new
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.
pinned to #8f8a6eeupdated 2 weeks ago
Ask your AI client: “install skills/new”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/newmetahub onboarded this repo on the author's behalf.
If you own github.com/bradautomates/second-brain on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
173
Last commit
2 weeks ago
Latest release
published
About this skill
Pulled from SKILL.md at publish time.
Create items from natural language: `/new <input>`
Allowed tools
- Read
- Glob
- Write
- Edit
- AskUserQuestion
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.8f8a6ee· 2 weeks ago
Documentation
41Description quality
26 words · 167 chars — "Quick capture - classify and file natural language input into the vault. Part of…"
README is present and substantial
10,031 chars · 11 sections · 9 code blocks
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
README has usage / example sections
found: Installation
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrent8f8a6eewarn2 weeks ago
Contents
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]]
## Notes
Person:
---
type: person
last-contact: YYYY-MM-DD
tags: []
---
## Context
Who they are, relationship.
## Follow-ups
- [ ] Pending items
Idea:
---
type: idea
tags: []
---
Description of the idea.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/new