Licensing AI Agent Skills - A New Frontier?
Moming Duan <[email protected]> Mon, 6 Apr 2026 22:39:32 +0800
| Newsgroups | gmane.comp.licenses.open-source.general |
|---|---|
| Message-ID | <CAE=aCWVSN5hy_MQ=zGaFy0_rtFMZtGvD6iqj=CkyQahU3BaKEQ@mail.gmail.com> |
--===============7601713403835816354== Content-Type: multipart/alternative; boundary="00000000000036f2fb064ecba38c" Content-Transfer-Encoding: 7bit --00000000000036f2fb064ecba38c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Hi OSI license community, Following previous discussions on model licensing and distillation, I wanted to raise another emerging question: how should we think about licensing AI agent "skills"? Skills are instruction sets for AI coding assistants (Claude Code, Cursor, etc.), they're essentially structured prompts with metadata, code snippets, and workflows that tell the AI how to perform specific tasks. They're distributed like software packages but aren't executed code. A few questions I'm curious about: 1. Do skills need explicit licenses? Anthropic's official skills use a restrictive proprietary license prohibiting extraction, derivatives, and distribution [1], while community skills like Tavily's often use MIT [2]. But are skills even copyrightable works, or just instructions? 2. Are these licenses enforceable? The US Copyright Office has concluded that "prompts alone do not provide sufficient human control" to qualify for copyright protection [3]. If the underlying prompts aren't copyrightable, what legal basis do skill licenses actually rest on? 3. Are traditional OSS licenses appropriate? Skills aren't software that gets compiled and executed - they're instructions that guide AI behavior. Do concepts like "derivative works" and "distribution" even apply in the same way? This matters beyond just skills. As AI agents become more autonomous and instruction-based, we're seeing a shift from licensing executed code to licensing the instructions that generate code. The legal frameworks we've built for software might not map cleanly. Curious to hear thoughts from the community. Best, Moming Duan --- Refs *[1] Anthropic skill LICENSE example: https://github.com/anthropics/skills/blob/main/skills/docx/LICENSE.txt <https://github.com/anthropics/skills/blob/main/skills/docx/LICENSE.txt>[2] Tavily skills (MIT): https://github.com/tavily-ai/skills <https://github.com/tavily-ai/skills>[3] US Copyright Office on prompt copyrightability: https://www.congress.gov/crs-product/LSB10922 <https://www.congress.gov/crs-product/LSB10922>* --00000000000036f2fb064ecba38c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi OSI license community,<br><br>Following previous discus= sions on model licensing and distillation, I wanted to raise another emergi= ng question: how should we think about licensing AI agent "skills"= ;?<br><br>Skills are instruction sets for AI coding assistants (Claude Code= , Cursor, etc.), they're essentially structured prompts with metadata, = code snippets, and workflows that tell the AI how to perform specific tasks= . They're distributed like software packages but aren't executed co= de.<br><br>A few questions I'm curious about:<br><br>1. Do skills need = explicit licenses?=C2=A0<div><br></div><div>Anthropic's official skills= use a restrictive proprietary license prohibiting extraction, derivatives,= and distribution [1], while community skills like Tavily's often use M= IT [2]. But are skills even copyrightable works, or just instructions?<br><= br>2. Are these licenses enforceable?=C2=A0</div><div><br></div><div>The US= Copyright Office has concluded that "prompts alone do not provide suf= ficient human control" to qualify for copyright protection [3]. If the= underlying prompts aren't copyrightable, what legal basis do skill lic= enses actually rest on?<br><br>3. Are traditional OSS licenses appropriate?= =C2=A0</div><div><br></div><div>Skills aren't software that gets compil= ed and executed - they're instructions that guide AI behavior. Do conce= pts like "derivative works" and "distribution" even app= ly in the same way?<br><br>This matters beyond just skills. As AI agents be= come more autonomous and instruction-based, we're seeing a shift from l= icensing executed code to licensing the instructions that generate code. Th= e legal frameworks we've built for software might not map cleanly.<br><= br>Curious to hear thoughts from the community.<br><br>Best,<br>Moming Duan= <br><br>--- Refs<br><i>[1] Anthropic skill LICENSE example: <a href=3D"http= s://github.com/anthropics/skills/blob/main/skills/docx/LICENSE.txt">https:/= /github.com/anthropics/skills/blob/main/skills/docx/LICENSE.txt</a><br>[2] = Tavily skills (MIT): <a href=3D"https://github.com/tavily-ai/skills">https:= //github.com/tavily-ai/skills</a><br>[3] US Copyright Office on prompt copy= rightability: <a href=3D"https://www.congress.gov/crs-product/LSB10922">htt= ps://www.congress.gov/crs-product/LSB10922</a><br></i></div></div> --00000000000036f2fb064ecba38c-- --===============7601713403835816354== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVGhlIG9waW5p b25zIGV4cHJlc3NlZCBpbiB0aGlzIGVtYWlsIGFyZSB0aG9zZSBvZiB0aGUgc2VuZGVyIGFuZCBu b3QgbmVjZXNzYXJpbHkgdGhvc2Ugb2YgdGhlIE9wZW4gU291cmNlIEluaXRpYXRpdmUuIE9mZmlj aWFsIHN0YXRlbWVudHMgYnkgdGhlIE9wZW4gU291cmNlIEluaXRpYXRpdmUgd2lsbCBiZSBzZW50 IGZyb20gYW4gb3BlbnNvdXJjZS5vcmcgZW1haWwgYWRkcmVzcy4KCkxpY2Vuc2UtZGlzY3VzcyBt YWlsaW5nIGxpc3QKTGljZW5zZS1kaXNjdXNzQGxpc3RzLm9wZW5zb3VyY2Uub3JnCmh0dHA6Ly9s aXN0cy5vcGVuc291cmNlLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2xpY2Vuc2UtZGlzY3Vzc19saXN0 cy5vcGVuc291cmNlLm9yZwo= --===============7601713403835816354==--