Menu
Turn a task or research note into a living spec plus a goal envelope — a ready-to-run work order for a condition-based agent loop.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Read, search, create, and edit notes in the user's personal Obsidian vault, located at "$HOME/Documents/Remote vault primary". Use this skill WHENEVER the user refers to "my notes", "my vault", "my Obsidian", a "daily note", or asks to find / look up / write down / jot / capture / file something into their notes — even if they don't say the word "Obsidian". Also use it when the user asks to summarize, link, or reorganize existing notes, or to add to today's daily note. If a request plausibly concerns the user's own knowledge base rather than the wider web, reach for this skill before falling back to generic file tools, so that Obsidian conventions (wikilinks, tags, frontmatter, daily notes) are respected.
Compact reference of best practices for authoring Agent Skills (SKILL.md files), distilled from Anthropic's official skill-authoring guide. Use whenever writing a new skill, reviewing or improving an existing SKILL.md, deciding how to structure a skill's files, or when the user asks about skill conventions, descriptions, progressive disclosure, or skill quality — even if they don't say "best practices".
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Complete reference for Neovim's vim.lsp API — all functions, arguments, and submodules. Use this skill whenever the user asks about vim.lsp functions, LSP keybindings, LSP configuration, or needs help with any Neovim LSP command. Also use when the user mentions lsp.buf, codelens, inlay hints, semantic tokens, or LSP-related Neovim setup, even if they don't say "vim.lsp" explicitly.
Complete reference for Neovim's vim.treesitter API — all functions, arguments, and submodules. Use this skill whenever the user asks about treesitter functions, treesitter queries, syntax highlighting, TSNode manipulation, or tree-sitter configuration in Neovim, even if they don't say "vim.treesitter" explicitly.
| name | to-goal |
| description | Turn a task or research note into a living spec plus a goal envelope — a ready-to-run work order for a condition-based agent loop. |
One pass, two artifacts: a contract (the living spec — abstract, permanent, user-observable) and its work order (the goal envelope — concrete, ephemeral, file paths and commands). Concreteness lives only in the work order; the contract must survive it.
Judge the blast radius of the request:
Either way the reasoning lands in ## Design Notes in the work order.
Done when one route is chosen — and, if extreme, the decline is delivered and the skill stops.
Read the input in full. Search the repo for existing specs, docs, or notes on the topic and carry forward any decisions they have already settled, naming where each came from. Walk the code.
Done when every Scope path and Verification command you are about to write traces to a file:line you have read.
Present both drafts and iterate until the user accepts.
Save the contract under specs/ and the work order under goals/ (create
either lazily), the work order linking the contract. Print the ready-to-paste
goal condition in the session and stop: the loop is the user's to start. Suggest re-checking
the implementation against the contract's user stories once the goal clears.
