skill
Skill1 starsChanged 29 days agoMITView on GitHub
Save a procedure as a reusable PEKA skill, available in every project. Use when the user runs /peka:skill or asks to turn something they taught or just did (a deploy, a release, a fix) into a skill.
62 other projects use a version of this.
Adopted by
Most recently taken up by
- thenavidm/skill-buildertheir own version, first seen Nov 8, 2026
- HelloRuru/claude-teams-gotheir own version, first seen Nov 8, 2026
- TheAlejo160/orchestratheir own version, first seen Nov 8, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- nexoral/AxioDBtheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use ai-slop-cleaner, ralplan and 9 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.
Jurel89Skillai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Also in 5 projects that use this
ibahgatSkillralplan
Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.
Also in 5 projects that use this
- ibahgatSkill
hud
Control omi visual HUD profile and keep status output readable in normal, compact, or hidden mode.
Also in 5 projects that use this
- Jurel89Skill
ultraqa
QA cycling loop — build/lint/test, fix, retry up to 5 cycles
Also in 3 projects that use this
LucasCooperBeySkillvisual-verdict
Structured visual QA verdict for screenshot-to-reference comparisons. Returns JSON scores driving edit iterations. Use after any UI implementation to verify visual fidelity.
Also in 3 projects that use this
Yeachan-HeoSkillultragoal
Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.
Also in 3 projects that use this
Other versions62 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 62
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- tradecatlabs/vibe-coding-cn★ 18ksame name
- tukuaiai/vibe-coding-cn★ 18ksame name
- liyue-aigc/female-portrait-director★ 1.6ksame name
- sundial-org/skills★ 151same name
- build23w/fdv.lol★ 128same name
- builders-toronto/fdv.lol★ 128same name
- redf0x1/camofox-mcp★ 124same name
52 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.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
If that is empty, use the procedure the user just taught or the task you just finished together.
- Very specific: line 22
If it says PEKA is not set up, tell the user to run /peka:setup and stop.
- Very specific: line 23
Follow the instruction it prints: launch peka:learner with that prompt.
- Distinctive: line 26
When it finishes, tell the user in one line which skill was created or updated.
- Very specific: line 28
Do not write the skill yourself, and never into ~/.claude/skills.
“Common” is measured: kept by at least 6 in 10 of the 45 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
Save as a skill
What to turn into a skill: $ARGUMENTS
If that is empty, use the procedure the user just taught or the task you just finished together. If it is still unclear, ask one short question first.
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/peka.mjs" learn --session "${CLAUDE_SESSION_ID}" --mode skillIf it says PEKA is not set up, tell the user to run
/peka:setupand stop.- Follow the instruction it prints: launch
peka:learnerwith that prompt. In theRequest:line, put the user's words plus the concrete steps from this conversation: commands that worked, the order, what went wrong, and how you confirmed success. - When it finishes, tell the user in one line which skill was created or updated.
Do not write the skill yourself, and never into ~/.claude/skills; the learner puts it
in PEKA's store, where it is versioned, curated, and available everywhere.
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.