Skill Share
Spin up a properly structured SKILL.md package and notify your team on Slack when you publish internal agent skills.
Overview
Skill-share is an agent skill most often used in Build (also Operate, Grow) that scaffolds, validates, and packages Claude skills and can announce them on Slack via Rube.
Install
npx skills add https://github.com/composiohq/awesome-claude-skills --skill skill-shareWhat is this skill?
- Scaffolds hyphen-case skill dirs with scripts/, references/, and assets/
- Validates SKILL.md YAML frontmatter and required metadata before zip
- Packages distributable archives after automated structure checks
- Posts created skills to Slack via Rube for team discovery
- Triggers when you explicitly want to create or share a skill
- 3 standard asset directories: scripts, references, assets
Adoption & trust: 2.2k installs on skills.sh; 63.7k GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You wrote a useful agent skill but lack a repeatable folder layout, validation step, zip artifact, and a way for teammates to notice it shipped.
Who is it for?
Indie or small teams building a library of internal Claude skills with Slack as the source of truth for what is available.
Skip if: Solo builders with no Slack/Rube setup who only need a one-off SKILL.md edit without packaging or team broadcast.
When should I use this skill?
You need to create new Claude skills, validate structure, package for distribution, or automatically share skills on Slack—including when the user says they want to create or share their skill.
What do I get? / Deliverables
You get a validated skill package ready to install plus optional Slack visibility so the team can adopt the skill without manual copy-paste.
- Validated SKILL.md skill directory
- Distributable skill zip
- Optional Slack team notification
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Skill authoring and packaging are core build-phase agent-tooling work before those capabilities ship to the team. Canonical shelf is agent-tooling because the skill generates directories, frontmatter, and distributable skill bundles—not general app code.
Where it fits
Author a payments integration skill, validate frontmatter, zip it, and post the bundle link in #agents.
Revise an internal lint skill, re-package after validation, and Slack the team that v2 is installable.
Onboard a contractor by creating a starter skill from template and broadcasting it on Slack.
How it compares
Skill scaffolding and team notification—not a marketplace listing tool or a skill quality benchmark suite.
Common Questions / FAQ
Who is skill-share for?
Solo builders and small teams who author Claude skills regularly and want consistent structure plus optional Slack announcements for discovery.
When should I use skill-share?
Use it in Build when packaging agent-tooling, in Operate when rolling out internal skill libraries, or in Grow when onboarding teammates to new capabilities—especially when you say you want to create or share a skill.
Is skill-share safe to install?
It may touch the filesystem, create archives, and call Slack through Rube; review the Security Audits panel on this page and scope Slack tokens before enabling auto-share.
SKILL.md
READMESKILL.md - Skill Share
## When to use this skill Use this skill when you need to: - **Create new Claude skills** with proper structure and metadata - **Generate skill packages** ready for distribution - **Automatically share created skills** on Slack channels for team visibility - **Validate skill structure** before sharing - **Package and distribute** skills to your team Also use this skill when: - **User says he wants to create/share his skill** This skill is ideal for: - Creating skills as part of team workflows - Building internal tools that need skill creation + team notification - Automating the skill development pipeline - Collaborative skill creation with team notifications ## Key Features ### 1. Skill Creation - Creates properly structured skill directories with SKILL.md - Generates standardized scripts/, references/, and assets/ directories - Auto-generates YAML frontmatter with required metadata - Enforces naming conventions (hyphen-case) ### 2. Skill Validation - Validates SKILL.md format and required fields - Checks naming conventions - Ensures metadata completeness before packaging ### 3. Skill Packaging - Creates distributable zip files - Includes all skill assets and documentation - Runs validation automatically before packaging ### 4. Slack Integration via Rube - Automatically sends created skill information to designated Slack channels - Shares skill metadata (name, description, link) - Posts skill summary for team discovery - Provides direct links to skill files ## How It Works 1. **Initialization**: Provide skill name and description 2. **Creation**: Skill directory is created with proper structure 3. **Validation**: Skill metadata is validated for correctness 4. **Packaging**: Skill is packaged into a distributable format 5. **Slack Notification**: Skill details are posted to your team's Slack channel ## Example Usage ``` When you ask Claude to create a skill called "pdf-analyzer": 1. Creates /skill-pdf-analyzer/ with SKILL.md template 2. Generates structured directories (scripts/, references/, assets/) 3. Validates the skill structure 4. Packages the skill as a zip file 5. Posts to Slack: "New Skill Created: pdf-analyzer - Advanced PDF analysis and extraction capabilities" ``` ## Integration with Rube This skill leverages Rube for: - **SLACK_SEND_MESSAGE**: Posts skill information to team channels - **SLACK_POST_MESSAGE_WITH_BLOCKS**: Shares rich formatted skill metadata - **SLACK_FIND_CHANNELS**: Discovers target channels for skill announcements ## Requirements - Slack workspace connection via Rube - Write access to skill creation directory - Python 3.7+ for skill creation scripts - Target Slack channel for skill notifications