collect-skills
Skill0 starsChanged 5 months agoNo licenceView on GitHub
Discover and ingest skills from sibling GitHub repos owned by the same user or org as the well-worn-tools checkout. Use when the user says "collect skills", "harvest skills from my other repos", "import skills from <repo>", "find skills across my repos", or "pull in skills I made elsewhere". Walks every non-archived repo for the owner, finds .claude/skills/* on the default branch, downloads each skill into a staging directory, and runs an adaptation pass that flags repo-specific paths, broken cross-references, frontmatter drift, and naming collisions before anything moves into .claude/skills/. Uses Python helpers in scripts/ for owner detection, repo and skill listing, content fetching, and adaptation reporting; the agent makes the final calls. Carries metadata.distribute false and must not itself be sent outward. Do NOT use for sending skills outward (use distribute-skills skill), authoring new skills from scratch (use skill-craft skill), or general issue and PR workflow (use git-workflow skill).
In this repository36 other files it gives its agents.
- address-feedbackSkill
- apple-to-android-port-specSkill
- architectural-decisionsSkill
- await-claude-reviewSkill
- backlog-groomingSkill
- bug-squashing-methodologySkill
- ci-debuggingSkill
- comprehensive-pr-reviewSkill
- concurrencySkill
- continue-epicSkill
- cve-remediationSkill
- de-slopifySkill
- discord-ralph-recapSkill
- distribute-skillsSkill
- documentationSkill
- error-handlingSkill
- file-naming-conventionsSkill
- frontend-aestheticsSkill
- git-workflowSkill
- max-quality-no-shortcutsSkill
- mutation-testingSkill
- preflightSkill
- prompt-engineeringSkill
- quick-testSkill
- review-diffSkill
- scan-issue-writerSkill
- securitySkill
- skill-craftSkill
- spec-decompositionSkill
- statusSkill
- stay-greenSkill
- testingSkill
- tracer-codeSkill
- triage-and-planSkill
- user-facing-error-messagesSkill
- vibeSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

