new
Skill217 starsChanged 8 months agoMITView on GitHub
Quick capture - classify and file natural language input into the vault. Part of chief-of-staff system. Use for capturing tasks, ideas, project notes, or people notes.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- per-simmons/claude-game-studiotheir own version, first seen Nov 8, 2026
- vvs1off/fabric-skillstheir own version, first seen Nov 8, 2026
- timpulver/openai-image-gentheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- AlexCiortan/setlisttheir own version, first seen Oct 29, 2026
- rust-off-rails/rustoffrailstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use upgrade, gate and 3 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.
agenticnotetakingSkillupgrade
Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".
Also in 4 projects that use this
synaptiaiSkillgate
Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.
Also in 3 projects that use this
kt057Skillcheck
lint, typecheck, test を一括実行して結果をサマリーする
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 5 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- H-mmer/pentest-agents★ 815same name
- with-pebbly/aseprite-ai-artist★ 473same name
- alamenai/terrae★ 245same name
- crisandrews/ClawCode★ 64same name
- rust-off-rails/rustoffrails★ 49same name
- howells/fiction★ 23same name
- The-Utopia-Studio/skills★ 6same name
- codebycorey/delta-spec★ 4same name
- per-simmons/claude-game-studio★ 4same name
- vvs1off/fabric-skills★ 4same name
10 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
- create-farmerSkill
- daily-reviewSkill
- delegate-taskSkill
- farmSkill
- historySkill
- start-second-brainSkill
- todaySkill
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 20 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
- Very specific: line 10
Create items from natural language: /new <input>
- Distinctive: line 51
When creating a task without a due date, use AskUserQuestion:
- Very specific: line 67
Use Obsidian wiki-style links [[slug]] in the markdown body to connect entities.
- Very specific: line 69
When creating a task linked to a project, update the project file to include [[task-slug]].
- Distinctive: line 71
Check if person/project already exists before creating (use Glob).
“Common” is measured: kept by at least 6 in 10 of the 20 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
/new - Quick Capture
Create items from natural language: /new <input>
Input is in $ARGUMENTS.
Do NOT commit manually unless explicitly asked. A PostToolUse hook auto-commits after Write operations.
Steps
- Decompose - Extract ALL entities from input (may be multiple)
- Classify each entity: task | project | person | idea
- Extract structured data (due dates, tags, names)
- Link entities via frontmatter fields
- Write files for each entity (hook handles git commit)
- Respond with summary of what was created
Decomposition
Parse input for multiple entities. Example:
"new project with John Smith for marketing outbound, need landing page and brainstorm names"
Entities:
- Person: John Smith
- Project: marketing-outbound (linked to John Smith)
- Task: create landing page (linked to project)
- Task: brainstorm names for workshop (linked to project)
Classification
- Named person with context → person
- Ongoing work, multiple steps → project
- Specific actionable item → task
- Speculative, "what if" → idea
- Confidence < 0.5 → Ask for clarification
Edge case: "start/begin/create X" → task (the action of initiating), not project.
- "I need to start a content plan" → task: start content plan
- "Working on the content plan" → project: content plan (if ongoing)
Missing Information
When creating a task without a due date, use AskUserQuestion:
Question: "When is this due?"
Header: "Due date"
Options:
- "Today" → use today's date
- "End of week" → use Friday of current week
- "Next week" → use Monday of next week
- (Other allows custom entry)Apply similar pattern for other ambiguous fields when classification confidence is high but key data is missing.
Linking
Use Obsidian wiki-style links [[slug]] in the markdown body to connect entities.
When creating a task linked to a project, update the project file to include [[task-slug]]. Same for project → person links.
Check if person/project already exists before creating (use Glob). Use Read before editing existing files.
File Formats
Task:
---
type: task
status: pending
due: YYYY-MM-DD # optional
tags: []
---
Description here.Project:
---
type: project
status: active
tags: []
---
## Next Action
- First task to do
[[linked-task-slug]]
## NotesPerson:
---
type: person
last-contact: YYYY-MM-DD
tags: []
---
## Context
Who they are, relationship.
## Follow-ups
- [ ] Pending itemsIdea:
---
type: idea
tags: []
---
Description of the idea.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.

