Install a skill you understand.

Start with the source

Open the linked skill folder. Check that SKILL.md exists, read the license that applies to that folder, and inspect references, templates, scripts, and bundled archives. Our third-party pages link to maintainers rather than hosting their instruction files. For Five-Field Handoff, we host a versioned archive and publish its hash.

Choose where it is available

Many agents recognize a project-local folder such as .agents/skills/my-skill/SKILL.md. Some also support a user-level skills directory, but paths and discovery rules vary by product and version. Use the documentation for your own agent. Project scope is a good first choice when a skill should apply only to one repository; user scope gives broader access.

my-skill/
  SKILL.md
  LICENSE
  references/

Copy the complete folder

Keep any relative references beside SKILL.md. If you use a supported installer, inspect which repository, revision, and files it proposes before accepting. Manual copying is often clearer for a first trial. A skill from a public repository can change after our review date; compare its current files and license before updating.

Verify discovery and behavior

1. Restart or reload the agent if its documentation requires it.
2. Ask it to identify the skill by name and point to the loaded SKILL.md.
3. Try a small task with narrow permissions and inspect both output and tool calls.
4. Review any requested shell command, network call, file access, or external action before allowing it.

Update or remove

Record the revision you installed. Before replacing it, compare the new files and repeat the small trial. To remove a manually installed skill, delete its entire folder from the configured skills directory, then reload the agent. If duplicate skill names exist in project and user scope, check which copy your agent actually loaded.

Need a second look at a listed skill? Send the listing URL and concern to [email protected].