install-skill
Skill16 starsChanged 10 months agoMITView on GitHub
This skill should be used when the user asks to "install a skill", "add a skill to the project", "unpack a skill", or "integrate a new skill". Automates the full workflow of unpacking .skill packages from dist/ and registering them in the marketplace.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- aornelas/claude-skillstheir own version, first seen Nov 1, 2026
- aaronjmars/miroshark-aeontheir own version, first seen Oct 21, 2026
- aeonfun/aeontheir own version, first seen Oct 20, 2026
- MiroShark/miroshark-aeontheir own version, first seen Oct 17, 2026
- Lilac-Labs/gini-agenttheir own version, first seen Oct 8, 2026
- Open-Curiosity/gini-agenttheir own version, first seen Oct 8, 2026
Used with
Projects with it also use aeon-update, auto-workflow and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
aaronjmarsSkillaeon-update
Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.
Also in 4 projects that use this
aaronjmarsSkillauto-workflow
Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.
Also in 4 projects that use this
- +10 more from aaronjmars
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- Lilac-Labs/gini-agent★ 1.9ksame name
- Open-Curiosity/gini-agent★ 1.9ksame name
- aaronjmars/aeon★ 789same name
- aeonfun/aeon★ 789same name
- roerohan/skills★ 29same name
- aaronjmars/miroshark-aeon★ 20same name
- MiroShark/miroshark-aeon★ 20same name
- Mineru98/skills-store★ 13same name
- xiangu152/my_claude_skills★ 2same name
- aornelas/claude-skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- geo-aeo-optimizationSkill
- linkedin-personal-brandingSkill
- linkedin-roastSkill
- seo-content-auditSkill
- seo-technical-auditSkill
- solidity-auditorSkill
- suno-music-creatorSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Identify target skill: If user specifies a skill name, use it.
- Distinctive: line 33
Verify package: Check the file exists and is a valid zip archive:
- Distinctive: line 40
Preview contents: before extracting:
- Distinctive: line 97
If file doesn't exist, create with template:
- Very specific: line 115
If file exists, add skill to plugins array.
- Distinctive: line 179
Invalid package: Check if file is valid zip archive
- Distinctive: line 182
Category conflict: Ask user to confirm category assignment
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Installer
Automates the installation of new skills into the skills marketplace project. Handles unpacking, marketplace registration, and documentation updates.
When to Use
- User has a
.skillfile indist/directory - User asks to "install", "add", "unpack", or "integrate" a skill
- User wants to add a new skill to the marketplace
Installation Workflow
Phase 1: Discovery
- List available skill packages:
ls -la dist/*.skill - Identify target skill: If user specifies a skill name, use it. Otherwise, list available packages and ask which to install.
- Verify package: Check the file exists and is a valid zip archive:
file dist/<skill-name>.skill
Phase 2: Extraction
- Preview contents before extracting:
unzip -l dist/<skill-name>.skill - Extract to project root:
unzip -o dist/<skill-name>.skill - Verify extraction:
ls -la <skill-name>/ ls -la <skill-name>/references/
Phase 3: Metadata Extraction
- Read SKILL.md frontmatter to extract:
name: Skill identifier (kebab-case)description: Full description for triggersmetadata.category: Category (seo, music, security, tooling, etc.)metadata.tags: Comma-separated tags
- Parse the frontmatter between
---markers at the top of SKILL.md - Generate short description for marketplace (one line, ~60 chars max)
Phase 4: Marketplace Registration
Update
.claude-plugin/marketplace.json:a. Update the top-level
descriptionif needed to include new categoryb. Add to
pluginsarray:{ "name": "<skill-name>", "type": "skill", "path": "<skill-name>", "description": "<short-description>", "category": "<category>", "tags": ["tag1", "tag2", ...] }c. Add category to
categoriesobject if new:"<category>": { "name": "<Category Display Name>", "description": "<Category description>", "marketplace": "marketplace-<category>.json" }Create/update category marketplace (
marketplace-<category>.json):If file doesn't exist, create with template:
{ "name": "skills-<category>", "version": "1.0.0", "description": "<Category> skills for Claude Code.", "author": "schwepps", "license": "MIT", "repository": { "type": "git", "url": "https://github.com/schwepps/skills.git" }, "plugins": [ { /* skill entry */ } ] }If file exists, add skill to
pluginsarray.
Phase 5: Documentation Update
Update README.md:
a. Update header description if new category added
b. Add to "What's Included" table:
| **[<skill-name>](<skill-name>/)** | <short-description> |c. Add usage examples section if new category:
### <Category>"Example prompt 1" "Example prompt 2"
d. Add to "Project Structure" tree:
├── <skill-name>/e. Add to "Browser Download" table:
| <Skill Display Name> | [Download ZIP](https://download-directory.github.io/?url=https://github.com/schwepps/skills/tree/main/<skill-name>) |
Phase 6: Verification
- Verify all files updated:
- Skill directory exists with SKILL.md and references/
- marketplace.json contains skill entry
- Category marketplace file exists and contains skill
- README.md updated with skill info
- Report summary:
Installed: <skill-name> Category: <category> Files: <count> reference files Updated: - .claude-plugin/marketplace.json - .claude-plugin/marketplace-<category>.json - README.md
Category Mappings
| Category | Display Name | Description |
| seo | SEO & AI Search | Search engine optimization and AI search visibility |
| music | Music Creation | AI-powered music and audio generation |
| security | Smart Contract Security | Blockchain and smart contract auditing |
| tooling | Developer Tools | Automation and development utilities |
Error Handling
- File not found: List available .skill files in dist/
- Invalid package: Check if file is valid zip archive
- Missing SKILL.md: Package is malformed, cannot install
- Missing frontmatter: Extract what's possible, ask user for missing metadata
- Category conflict: Ask user to confirm category assignment
Quick Install Command
For a straightforward installation with a known skill file:
/install-skill <skill-name>This will:
- Unpack
dist/<skill-name>.skill - Auto-detect metadata from SKILL.md
- Register in all marketplace files
- Update README.md
- Report completion status
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

