skillify
Skill0 starsChanged 3 months agoMITView on GitHub
Turn one previous Claude Code or Codex session into a focused reusable skill. Use when the user provides a transcript, session ID, or remembered task and asks to capture, extract, or skillify the repeatable workflow.
51 other projects use a version of this.
Adopted by
Most recently taken up by
- devjiwonchoi/skillstheir own version, first seen Nov 8, 2026
- kyle-chalmers/ticketwrighttheir own version, first seen Nov 8, 2026
- timurgaleev/vibestacktheir own version, first seen Nov 8, 2026
- fmind/dottheir own version, first seen Nov 8, 2026
- fmind/dotfilestheir 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 plan-tune, ios-clean 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.
ShreyRaviSkillplan-tune
Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.
Also in 9 projects that use this
Saqlain-811Skillios-clean
Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)
Also in 5 projects that use this
- Saqlain-811Skill
ios-fix
Autonomous iOS bug fixer. (gstack)
Also in 5 projects that use this
- ShreyRaviSkill
landing-report
Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)
Also in 8 projects that use this
timurgaleevSkilldocument-generate
Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.
Also in 7 projects that use this
bastosSkillios-design-review
Review iOS app UI/UX design quality using Apple's design principles and the Liquid Glass-era design language from WWDC25/26. Use when asked for a design review, UX critique, visual design assessment, or evaluation of an app's interface quality, design intent, alignment with the new Apple design system, or usability. Triggers: "design review", "UX review", "visual design critique", "review the UI", "does this design work", "evaluate this interface", "design feedback", "Liquid Glass review".
Also in 5 projects that use this
- +1 more from Saqlain-811
- +5 more from ShreyRavi
Other versions51 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 51
- garrytan/gstack★ 141ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- garrytan/gbrain★ 32ksame name
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- ZhangHanDong/harness-engineering-from-cc-to-ai-coding★ 1.5ksame name
- coreyhaines31/makerskills★ 893same name
- 0xMH/claude-skillify★ 45same name
- Surething-io/cockpit★ 44same name
41 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 repository4 other files it gives its agents.
- create-skillSkill
- prune-memorySkill
- share-memorySkill
- update-skillSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
4
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
- could be automatic: a setting could enforce it
- Distinctive: line 17
Read the selected transcript without resuming or modifying it.
- Distinctive: line 22
Remove secrets, ephemeral identifiers, local-only values, dated status, and incidental conversation.
- Distinctive: line 24
Stop if the session only records a one-off action.
- Very specific: line 30
After approval, route the artifact through create-skill, including its inventory check, script tests, and structural audit.
- Distinctive: line 35
Do not infer authority for publishing, messaging, deployment, production writes, or spending from the source session.
“Common” is measured: kept by at least 6 in 10 of the 44 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
Skillify
Produce an operating guide, not a transcript recap or a skill for a one-off result.
Workflow
- Require a concrete transcript path, session ID, or remembered description. Do not search or write when the reference is empty.
- Find one source session in the local Claude or Codex transcript store. Widen a text search only when needed. If multiple candidates remain plausible, show their source, ID, project, time, and matching evidence, then ask the user to choose.
- Read the selected transcript without resuming or modifying it. Never merge separate sessions into one source workflow.
- Extract the durable goal, inputs, decisions, ordered actions, outputs, validation, corrections, failure paths, tools, and human checkpoints. Treat later user corrections as authoritative over earlier behavior.
- Remove secrets, ephemeral identifiers, local-only values, dated status, and incidental conversation. Mark any unsupported inference as an assumption.
- Stop if the session only records a one-off action. Explain why it does not merit a skill.
- Infer a name, triggers, arguments, and destination only when unambiguous. Resolve material gaps with concise questions.
- Draft the complete proposed
SKILL.mdand any genuinely reusable resources. Show the exact artifact and destination before writing. - After approval, route the artifact through
create-skill, including its inventory check, script tests, and structural audit. - Report the source session ID, saved path, invocation examples, validation result, and transcript-unsupported assumptions.
Do not infer authority for publishing, messaging, deployment, production writes, or spending from the source session. Encode a fresh approval checkpoint instead.
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.