Agent Skills › TomWhitwell/Workshop_Computer › choose-card-license

choose-card-license

GitHub

协助卡片作者通过问答选择符合规范的开源许可证。区分法律许可与社区偏好，基于代码来源、衍生作品要求及商业意图推荐MIT、GPL或CC0等标准许可证，并输出YAML配置及注意事项。

.github/skills/choose-card-license/SKILL.md TomWhitwell/Workshop_Computer

触发场景

为项目选择开源许可证讨论许可证对商业复用和衍生作品的限制确定info.yaml中的License字段值

安装

npx skills add TomWhitwell/Workshop_Computer --skill choose-card-license -g -y

更多选项

非标准路径

npx skills add https://github.com/TomWhitwell/Workshop_Computer/tree/main/.github/skills/choose-card-license -g -y

不安装直接使用

npx skills use TomWhitwell/Workshop_Computer@choose-card-license

指定 Agent (Claude Code)

npx skills add TomWhitwell/Workshop_Computer --skill choose-card-license -a claude-code -g -y

安装 repo 全部 skill

npx skills add TomWhitwell/Workshop_Computer --all -g -y

预览 repo 内 skill

npx skills add TomWhitwell/Workshop_Computer --list

SKILL.md

Frontmatter

{
    "name": "choose-card-license",
    "description": "Interview a Workshop Computer card author to choose a legal License value for info.yaml. Use when: selecting a license, discussing commercial reuse, ports, derivatives, modified Workshop System cards, VCV Rack, plugins, or hardware adaptations.",
    "argument-hint": "Describe the card, its source dependencies, and reuse preferences"
}

Choose a Workshop Computer Card License

Help a card author select the License value required by documentation/info.yaml.md.

Boundaries

State that this is general guidance, not legal advice.
Clearly separate the legal license from the author's community preferences.
Explain that courtesy requests cannot override permissions granted by a legal license.
Do not imply that commercial software/hardware permissions restrict selling or releasing music made with the card.
Link to Choose a License for further guidance.

Interview

Ask these questions one at a time, using plain language:

After each answer, briefly update the provisional recommendation or explain which remaining legal answer is needed. Do not present a provisional result as final.

Does the card include or derive from third-party code, libraries, samples, documentation, or hardware designs? If yes, identify their licenses before recommending anything.
May others distribute closed-source versions of the card software?
Must distributed derivatives remain open under the same terms?
Does the author want a broad public-domain-style dedication?
May others sell or commercially distribute modified software, plugin ports, hardware versions, or other derivatives? Clarify that this does not concern music created with the card.
Ask separately for non-legal author preferences for:
- a derivative or modified Workshop System card;
- a VCV Rack port;
- a plugin port, including a sold plugin;
- a hardware version, including a sold hardware version.

For each preference, offer:

OK without asking, with credit
OK without asking
Please contact me first
I am not comfortable with this

Recommendation Rules

Recommend MIT for permissive reuse, including commercial and closed-source derivatives, with notice retention.
Recommend GPL-3.0-or-later when distributed derivatives must remain open under compatible GPL terms.
Recommend CC0-1.0 only for a requested broad public-domain-style dedication, with a warning to review its suitability for software and patent concerns.
If commercial reuse is prohibited or permission is required, explain that standard open-source licenses are not a match and ask the project maintainers for a source-available/custom policy.
If inherited or third-party licensing is unresolved, do not make a final recommendation.

Output

Return:

Recommended legal license and short rationale.
Permissions and obligations in plain language.
Compatibility or dependency warnings.
A clear note that author preferences are separate from legal conditions.
A link to the authoritative full license text and instructions to add it as LICENSE beside info.yaml, including any copyright placeholders or source notices that must be completed.
The exact YAML line:

License: <SPDX identifier or approved short name>

Do not serialize community preferences into notes, readme, or another unrelated field. Do not invent or paraphrase the legal text; direct the author to copy the complete authoritative text and preserve third-party notices.