in-progress
Skill4 starsChanged 2 months agoMITView on GitHub
Manage draft skills that are not ready to ship yet. Use when the user asks to prototype, sketch, test, evaluate, or promote an experimental skill from in-progress into a stable skill bucket.
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/project-docs-prep/templates/AGENTS.mdAGENTS.md
- skills/project-docs-prep/templates/CLAUDE.mdCLAUDE.md
- deep-planningSkill
- deep-planningSkill
- deprecatedSkill
- architecture-reviewSkill
- code-reviewSkill
- diagnoseSkill
- tddSkill
- ui-design-engineeringSkill
- ux-ui-design-assessmentSkill
- mcp-tool-managementSkill
- skill-managementSkill
- obsidian-canvasSkill
- obsidian-markdownSkill
- obsidian-notion-bridgeSkill
- obsidian-vault-workflowSkill
- boomz-preferencesSkill
- personal-agent-workflowSkill
- personalSkill
- automation-designSkill
- grill-with-docsSkill
- handoffSkill
- inbox-meeting-triageSkill
- markdown-reportSkill
- prompt-improvementSkill
- project-docs-prepSkill
- claim-citation-checkSkill
- daily-news-reportSkill
- github-skill-researchSkill
- project-discoverySkill
- repo-tourSkill
- research-methodologySkill
- seo-website-evaluatorSkill
- thaiSkill
- thai-addressSkill
- thai-customer-serviceSkill
- thai-date-formatSkill
- thai-festival-cardSkill
- thai-government-formSkill
- thai-id-validateSkill
- thai-invoiceSkill
- thai-pdpaSkill
- thai-resumeSkill
- thai-social-captionSkill
- thai-text-processingSkill
- thai-translateSkill
- backtest-expertSkill
- dividend-value-screenerSkill
- drawdown-circuit-breakerSkill
- exposure-coachSkill
- market-breadth-analyzerSkill
- portfolio-managerSkill
- position-sizerSkill
- tradingSkill
- trader-memory-coreSkill
- uptrend-analyzerSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill for draft skills that need iteration before becoming public or team-ready.
- Distinctive: line 17
Keep experiments small enough to promote or retire quickly.
- Distinctive: line 18
Do not add large references until the core workflow works.
- Distinctive: line 19
Do not promote a skill without realistic trigger examples.
- Distinctive: line 30
Prefer workflow steps over broad advice.
- Distinctive: line 31
Add stop conditions when misuse is likely.
- Distinctive: line 33
Test with realistic prompts
- Distinctive: line 40
Keep in progress when examples still fail or scope is unclear.
- Distinctive: line 45
Update README references if the skill is public.
- Distinctive: line 46
Update workflows or registries only when the skill is part of a repeatable job.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
In Progress Skill Incubator
Use this skill for draft skills that need iteration before becoming public or team-ready.
Purpose
skills/in-progress/ is a staging area. A draft belongs here when the idea is useful but the trigger, workflow, scope, or validation is still uncertain.
Rules
- Draft skills should not be listed as stable skills in the root README.
- Keep experiments small enough to promote or retire quickly.
- Do not add large references until the core workflow works.
- Do not promote a skill without realistic trigger examples.
Workflow
- Define the experiment
- State the repeated task the draft skill should improve.
- Name the expected trigger phrases.
- Identify what the agent should do differently after loading it.
- Draft narrowly
- Give the skill one main job.
- Prefer workflow steps over broad advice.
- Add stop conditions when misuse is likely.
- Test with realistic prompts
- Try at least three prompts that should trigger the skill.
- Try one prompt that should not trigger it.
- Note where the instructions are too vague or too broad.
- Decide status
- Promote to a domain bucket when the workflow is stable and useful.
- Keep in progress when examples still fail or scope is unclear.
- Move to
deprecated/when the idea is no longer worth pursuing.
- Promote cleanly
- Move the skill folder into the right bucket.
- Update README references if the skill is public.
- Update workflows or registries only when the skill is part of a repeatable job.
Promotion Checklist
nameis lowercase and hyphenated.descriptionclearly says when to use the skill.- The body has a workflow, rules, and verification or output guidance.
- The skill has one main job.
- It does not duplicate another stable skill.
- Any long examples or references are moved into
references/.
Output Format
End with:
- Draft status
- What changed
- What still needs testing
- Promote, keep, or retire recommendation
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.

