Skill Registry Terms

These terms apply specifically to publishing a skill to the public Reelier registry (reelier push <skill> --publicor the dashboard’s “Submit to registry” toggle). They supplement, and do not replace, the general Terms of Service.

You grant distribution rights

When you publish a skill to the registry, you grant Reelier a non-exclusive, worldwide license to host, display, and distribute that content (the frozen skill file and its metadata) at its public URL and machine-readable twin, and to serve it via the registry API and the CLI’s get command, for as long as the listing remains public.

You warrant you may share it

By publishing, you represent and warrant that:

• You own the content or have the right to share it under the license you declare.
• The skill file does not contain malware, exploits, or anything designed to attack, scan, or otherwise harm a third-party system.
• The skill file does not contain secrets — API keys, bearer tokens, credentials embedded in URLs, or any other sensitive value. (The publish pipeline runs an automated secret scan and rejects likely matches, but that scan is a backstop, not a substitute for your own care.)
• The name and description do not impersonate Reelier, Anthropic, or any other person or project.

Effect grading is computed, not claimed

A skill’s public effect grade (read-only or writes) is computed from the file’s declared and classified tool effects — your own frontmatter/step annotations never override it. Understating a step’s effect is treated as a publish-time error, not something we take your word for.

Takedown & DMCA

To report a listing — copyright infringement, malware, impersonation, secrets, or any other policy violation — use the “Report” link on the skill’s page, or email max@seldonframe.com with:

• The URL of the listing (e.g. https://reelier.com/skills/<owner>/<skill>).
• A description of the issue and, for a copyright claim, the work being infringed.
• Your contact information.

On a valid report, we remove the listing: the page becomes a tombstone showing the removal reason (never the content), and the markdown twin, the fetch API, and the CLI’s getcommand all return an honest 410 with that reason. For a policy takedown, the content’s hash is blocklisted so it cannot be republished under a new name; an author who self-unpublishes their own work is not blocklisted and may republish their own bytes.

We aim to act on reports promptly. This is not a substitute for formal legal counsel on either side of a dispute.

No warranty on published content

Registry listings are published by their authors, not by Reelier. We run automated triage (parse validation, effect grading, a secret scan, and a name/description lint) before a skill can list, but we do not manually review every read-only listing before it goes live, and we make no warranty about the accuracy, safety, or fitness of any third-party skill.

Contact

Questions: max@seldonframe.com. See also our Terms of Service and Privacy Policy.