[License-discuss] Licensing AI Agent Skills - A New Frontier?
Moming Duan
duanmoming at gmail.com
Mon Apr 6 14:39:32 UTC 2026
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>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20260406/566c2db8/attachment.htm>
More information about the License-discuss
mailing list