How do I install the Share Skills skill?

Run npx skillmds@latest add spinabot/share-skills in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Share Skills safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Share Skills?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Share Skills free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Share Skills?

spinabot (@spinabot) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Share Skills by spinabot — Agent Skill

Name: Share Skills
Author: spinabot

File contents

Sharing Skills

This skill explains how skills are structured and how to package one for sharing. It is a companion to skill authoring: where skill-creator helps you write a skill, this covers laying it out correctly and bundling it to hand off.

Where skills live

Each skill is a folder under the skills/ directory. The folder name is the skill's identity and must match the name field in its frontmatter (lowercase). At minimum a skill folder contains a SKILL.md; it may also include supporting files (scripts, reference docs, assets) the skill refers to.

skills/
  my-skill/
    SKILL.md
    reference.md        # optional supporting docs
    scripts/run.sh      # optional helper scripts

SKILL.md format

A SKILL.md is a Markdown file with a YAML frontmatter block followed by the skill body.

---
name: my-skill          # must equal the folder name, lowercase
description: Use when ...  # the "use when" trigger guidance, product-free
# optional eligibility keys (omit any that don't apply):
os: [darwin, linux]       # OS restriction
requires-bins: [foo]      # binaries that MUST be present
requires-any-bins: [a, b] # at least one of these binaries
requires-env: [MY_TOKEN]  # required environment variables
---

Body guidelines:

Open with a short overview of what the skill does and when to reach for it.
Keep instructions truthful: only describe actions the runtime can actually perform.
Reference any supporting files by relative path within the folder.
Keep it lean — the description and metadata are what get surfaced; the body is read on demand.

Versioning a shared skill

When you intend to share a skill, keep a changelog note and a version in mind so recipients can tell revisions apart. A simple convention is a ## Changelog section at the bottom of SKILL.md or a sibling CHANGELOG.md.

Packaging a folder to share

To share a skill, bundle its entire folder (so supporting files travel with it) and hand it off as an archive.

# from the skills/ directory, archive a single skill folder
tar -czf my-skill.tar.gz my-skill/

The recipient unpacks the archive into their own skills/ directory:

tar -xzf my-skill.tar.gz -C ./skills/

After unpacking, confirm the folder name still matches the name in frontmatter and that any requires-* eligibility keys are accurate for the new environment.

Checklist before sharing

name equals the folder name (lowercase).
description is present and free of product names.
Eligibility keys (os / requires-bins / requires-any-bins / requires-env) reflect real requirements — omit them when there are none.
Supporting files are inside the folder and referenced by relative path.
The body never instructs calling a tool the runtime does not have.

---name: share-skillsdescription: Use when you need to author, package, or share a skill folder — understanding the SKILL.md format, where skills live, and how to bundle a folder so it can be shared with others.---# Sharing SkillsThis skill explains how skills are structured and how to package one for sharing. It is a companion to skill authoring: where skill-creator helps you write a skill, this covers laying it out correctly and bundling it to hand off.## Where skills liveEach skill is a folder under the `skills/` directory. The folder name is the skill's identity and must match the `name` field in its frontmatter (lowercase). At minimum a skill folder contains a `SKILL.md`; it may also include supporting files (scripts, reference docs, assets) the skill refers to.```skills/ my-skill/ SKILL.md reference.md # optional supporting docs scripts/run.sh # optional helper scripts```## SKILL.md formatA `SKILL.md` is a Markdown file with a YAML frontmatter block followed by the skill body.```yaml---name: my-skill # must equal the folder name, lowercasedescription: Use when ... # the "use when" trigger guidance, product-free# optional eligibility keys (omit any that don't apply):os: [darwin, linux] # OS restrictionrequires-bins: [foo] # binaries that MUST be presentrequires-any-bins: [a, b] # at least one of these binariesrequires-env: [MY_TOKEN] # required environment variables---```Body guidelines:- Open with a short overview of what the skill does and when to reach for it.- Keep instructions truthful: only describe actions the runtime can actually perform.- Reference any supporting files by relative path within the folder.- Keep it lean — the description and metadata are what get surfaced; the body is read on demand.## Versioning a shared skillWhen you intend to share a skill, keep a changelog note and a version in mind so recipients can tell revisions apart. A simple convention is a `## Changelog` section at the bottom of `SKILL.md` or a sibling `CHANGELOG.md`.## Packaging a folder to shareTo share a skill, bundle its entire folder (so supporting files travel with it) and hand it off as an archive.```bash# from the skills/ directory, archive a single skill foldertar -czf my-skill.tar.gz my-skill/```The recipient unpacks the archive into their own `skills/` directory:```bashtar -xzf my-skill.tar.gz -C ./skills/```After unpacking, confirm the folder name still matches the `name` in frontmatter and that any `requires-*` eligibility keys are accurate for the new environment.## Checklist before sharing- `name` equals the folder name (lowercase).- `description` is present and free of product names.- Eligibility keys (`os` / `requires-bins` / `requires-any-bins` / `requires-env`) reflect real requirements — omit them when there are none.- Supporting files are inside the folder and referenced by relative path.- The body never instructs calling a tool the runtime does not have.

Frequently asked questions

Share Skills