creator field guide / repository to discovery

publish agent skills.
get discovered.

To publish an Agent Skill, put its complete validated folder in a public Git repository, document the job, license, compatibility, permissions, examples, and install command, then verify the public source with npx skills add owner/repo. skills.sh has no separate submission form; successful installations provide anonymous ranking telemetry and can make the skill discoverable automatically.

Written and checked by skillZs. Updated July 15, 2026.

How do you publish an Agent Skill?

Finish and validate the skill. Use a folder with a valid uppercase SKILL.md, focused instructions, tested triggers, and every referenced script or resource.
Create a public Git repository. Commit the complete skill folder to a stable repository whose owner and history users can inspect.
Document trust and compatibility. Add a repository README, license, install command, supported clients, requirements, permissions, examples, tests, and security notes.
Test the public install path. Install from the repository with npx skills add owner/repo in a clean disposable project and verify the copied files and behavior.
Share the canonical repository. Link one stable source URL from documentation, examples, community posts, and relevant project pages instead of uploading conflicting copies.
Maintain the published revision. Review issues, document behavior changes, compare dependencies, keep examples working, and treat every update as a new security review.

my-agent-skills/
|-- README.md
|-- LICENSE
-- skills/
    -- pull-request-review/
        |-- SKILL.md
        |-- scripts/       # optional
        |-- references/    # optional
        -- assets/        # optional

Start with the Agent Skill creation guide if the folder is not finished. The publisher-facing README belongs at the repository level; SKILL.md remains the agent-facing source of truth inside each skill folder.

How does a skill become discoverable on skills.sh?

The official publishing flow has no registry upload or approval form. A user installs directly from the public repository, and the skills CLI sends anonymous telemetry containing the skill identity, files, and timestamp unless telemetry is disabled. Aggregated installs power the public leaderboard. A valid repository can therefore become discoverable through real installation activity.

npx skills add owner/repository

# When the repository contains several skills:
npx skills add owner/repository --skill pull-request-review

skillZs reads that live ecosystem through its API. It does not accept payment for placement or maintain a separate upload queue. See the catalog methodology and live install rankings for how discovery data is presented.

What should a public Agent Skill repository include?

A concise README naming each skill, the job it solves, supported clients, and exact installation examples.
A license that clearly permits the intended reuse and distribution.
Compatibility requirements such as runtimes, binaries, MCP servers, APIs, network access, or operating-system limits.
Permission and security notes for scripts, credentials, write access, destructive actions, and outbound services.
Positive and negative trigger examples plus one repeatable outcome test.
A maintainer identity, issue channel, version history, and responsible security-reporting path.

How do you help people trust and recommend your skill?

Make every claim inspectable. Link the canonical source instead of republishing unexplained copies, keep scripts readable, request only necessary permissions, document tested clients, and show what success looks like. Add the official skills.sh install-count badge to the repository README after the skill is indexed, but never present installs as a security certification.

Before sharing, run the security review checklist and repeat the installation process from a clean project. Users can then find the published result through the Agent Skills Directory or relevant agent and coding collections.

What do creators ask about publishing Agent Skills?

How do I submit an Agent Skill to skills.sh?

There is no separate submission form or publish command. Put the skill in a public Git repository, share it, and verify that people can install it with the skills CLI. Anonymous install telemetry can make it appear in the skills.sh ecosystem automatically.

How does a published skill appear on skillZs?

skillZs mirrors the live skills.sh ecosystem. Once the upstream API indexes a non-duplicate skill, skillZs can surface its source, manual, install count, and available audit information automatically.

Can one repository contain several Agent Skills?

Yes. Keep each skill in its own named folder with its own SKILL.md, document the available skills, and test selecting a specific skill during installation.

What makes people trust a published Agent Skill?

A clear maintainer, stable source, license, narrow permissions, readable scripts, realistic examples, outcome tests, compatibility notes, security disclosures, and a maintained change history all reduce uncertainty.

Do install counts prove that a skill is safe or high quality?

No. Install counts measure adoption. Users must still review the exact source, revision, permissions, dependencies, and behavior for their environment.

Which official sources explain Agent Skill publishing?

This guide was checked against the Vercel Agent Skills publishing guide, skills.sh documentation, skills CLI reference, and the Agent Skills specification.