Agent Stuff

Personal prompts, skills, and commands I use with Claude and Cursor. Some are highly specific to my own setup (like my Obsidian vault). Sharing publicly in case any of it's useful or interesting to others.

Agent skills format

This repo uses the Claude Agent Skills format. Skills are folders containing a SKILL.md with YAML frontmatter and instructions. The description field tells AI agents when to load and apply the skill.

skill-name/
├── SKILL.md              # Metadata + instructions
├── reference.md          # Optional: detailed docs
└── supporting-file.md    # Optional: additional context

Using these

Copy whatever looks useful into your own skills directory. Or use the skills CLI to quickly add items from this repo:

bunx skills add nweii/agent-stuff

# or
npx skills add nweii/agent-stuff

Install a specific skill:

bunx skills add nweii/agent-stuff --skill [skill-name]

Updating skills:

bunx skills update

To update a specific skill, run skills add again with the same skill.

Internal skills

Skills marked [Internal] in the catalog below have metadata.internal: true set — they're personal workflows tied to my own setup (vault paths, tools, naming conventions). You can still install them, but expect to tweak SKILL.md to fit your own folders, tool stack, and conventions before they're useful. The skills CLI treats them differently:

• bunx skills add nweii/agent-stuff (no --skill flag) skips internal skills. To install one, name it explicitly with --skill [skill-name].

• bunx skills update silently skips internal skills (you'll see "Failed to update" with no detail). To refresh an installed internal skill after a repo change, remove and re-add it:

  bunx skills remove --skill [skill-name]
  bunx skills add nweii/agent-stuff --skill [skill-name]

---

Catalog

Auto-generated by scripts/update-catalog.py

Skills

[Internal] = personal workflows or vault-specific, likely needs adaptation.

• archive-conversation — Create analytical archival summaries of AI conversations, capturing intellectual journeys, key insights, and technical logs. Use when archiving, saving, or documenting a chat session.
• archive-to-brain [Internal] — Save an archival summary of an AI conversation to Nathan's Obsidian vault, using the Thinking note template and vault folder conventions to capture intellectual journeys, key insights, and technical logs. Use when archiving a chat session to the vault.
• audit-transcription — Flag and propose corrections for likely mistranscriptions in auto-transcribed meeting notes or audio transcripts. Use when the user says 'audit this transcript', 'fix the transcription', 'find mistranscriptions', or shares a noisy Granola/Whisper output and asks for cleanup.
• code-to-pantry [Internal] — Extract a code pattern from the current codebase into Nathan's pantry repo as a reusable recipe. Use when Nathan says 'add to pantry', 'save this code pattern', or wants to preserve a technique for reuse.
• commit — Create well-formatted commits with conventional commit messages. Use when user asks to commit, wants to commit changes, or needs help with commit messages.
• create-topic-note [Internal] — Create a Commentary topic note grouping related notes under a common theme, with automatic backlinking to source notes. Triggers: 'group these under a topic', 'create topic note for [[A]], [[B]], [[C]]'.
• enrich-from-transcript — Enrich an existing meeting/interview note from its transcript, or scaffold one when only a transcript exists. Captures granular narrative, exact phrases, mechanics, casual context, and implicit signals. Run on thin auto-summary notes or transcripts that warrant close reading.
• extract-flow-scenario — Extracts a sequence of workflow events from conversation context into a structured markdown list. Surfaces actors, state changes, and pain points to serve as raw data for any later synthesis, design planning, or spec development. Use when asked to document an actual operational flow, user journey, or scenario from a conversation to capture exactly what happened.
• file-naming — Analyze file content and propose intelligent renames using context-aware naming conventions. Date-prefixed for transactional/periodic documents, content-first for creative works. Use for organizing files, cleaning up downloads, or standardizing filenames.
• nweii-skills [Internal] — Reference for Nathan's agent skills setup: the nweii/agent-stuff and nweii/agent-stuff-private repos, frontmatter conventions, changelog practices, privacy tiers, and migrating locally-developed skills into a repo. Use when creating, editing, migrating, or installing skills in Nathan's environment.
• obsidian-clis — Control Obsidian notes from the terminal via the obsidian app CLI, with notesmd-cli as a headless fallback. Covers CRUD, search, vault structure (orphans, backlinks, unresolved links), tasks, properties, Bases, and plugin dev. Use when the user mentions Obsidian CLI, notesmd-cli, or shell automation of vault notes.
• obsidian-granola [Internal] — Sync meetings from Granola to Obsidian — pulls notes and transcripts and imports them as formatted meeting/transcript notes. Use when the user says "sync my last granola meeting", "note for my last meeting", or asks to pull in a Granola transcript.
• obsidian-log-commits [Internal] — Fetches today's GitHub commits across personal and org repos, filters noise, and appends a summary as bullets into the ## Log section of today's daily note. Use when asked to log what was worked on today, check today's commits, or update the daily note with dev activity.
• obsidian-sync-people [Internal] — Creates or enriches entity notes for people in /04-Entities/ from available context — current conversation, Granola meetings, Gmail threads. Use when someone is mentioned and worth noting, or when explicitly asked to create or update a person note.
• obsidian-templater — Help with templates/snippets for the Obsidian Templater plugin. Use to help generate Obsidian templates from natural language, understand and debug existing tp.* snippets, and adapt vault notes and workflows to Templater when users mention Templater, tp.*, or <% %>.
• obsidian-web-clipper — Author and debug Obsidian Web Clipper extension templates: template JSON, variables, filters, schema.org/CSS selectors, AI interpreter prompts, URL/schema triggers. Use when generating, importing, or fixing a clipper template, or matching one to a target site. Not for general scraping.
• periodic-rollup [Internal] — Synthesize child periodic note descriptions into a parent weekly/quarterly/yearly note. For history rollup (compiling mentions of a project/topic into a Histories note), follow references/history-rollup.md.
• project-chronicles — Set up and maintain a two-track project documentation system: a working log (implementation decisions tied to code) and usage notes (durable product/process thinking). Detects existing structure and adapts rather than overwriting. Use when starting docs, writing a session log entry, or capturing project context for future sessions.
• project-teacher — Generates a detailed project explanation and retrospective (FOR_USER.md) to help the user learn from the project. Use this skill when the user asks to explain the project, asks "what did we just build?", or invokes the skill to generate a learning resource after a coding session.
• quantify-impact — Surface measurable metrics and outcomes from a description of work via structured conversation. Use when the user says 'help me quantify this', 'what numbers can I attach to X', or is drafting a resume bullet, case study, or impact statement that needs concrete scale.
• raycast-extensions — Build Raycast extensions — commands, List/Form/Grid views, hooks like useFetch, AI integration, manifest. Use when the user says 'raycast extension', 'add a raycast command', or is working in a project with @raycast/api and a Raycast manifest.
• react-useeffect — React useEffect best practices. Use when writing Effects, derived values, or data fetching. Teaches when NOT to use Effects and better alternatives like useMemo or key props.
• save-napkin-note [Internal] — Turn raw capture material into a properly structured Brain vault note (template, frontmatter, folder, links), or integrate a fragment into an existing note after confirmation. Use when filing a quick capture — triggers: 'save this as a note', 'file this', 'napkin note', 'process this dump'.
• save-term [Internal] — Save a term, phrase, or coined concept as a Term note in the Brain vault under 02-Evergreen/Terms/. Two modes: capturing a nice term encountered in reading (with source quote) or recording one coined during conversation (with brief gloss). Triggers: '/save-term ', 'save this term', 'add this to my terms'.
• set-note-description — Generate or update the description frontmatter property for a note. Selects Summary mode or Meta mode based on content type. Use when asked to create a description frontmatter summary for a note.
• spec-shaping — Shape product ideas into actionable specs and sprint plans. Use when interviewing about a product plan, breaking specs into sprints, or turning vague ideas into well-scoped work.
• suggest-lucide-icons — Pick Lucide icons for a concept, UI placement, or vault note. Searches lucide.dev for real icon names. Use when the user says 'what icon for X', 'suggest a Lucide icon', 'pick an icon', or needs an icon for note frontmatter, a button, or a section header.
• sync-things-tasks — Syncs tasks between Obsidian vault and Things 3. Adds tasks from notes, extracts action items from projects, reviews existing tasks. Use when managing todos from vault content.
• things-mac — Read, search, add, and update tasks/projects/areas in Things 3 via its CLI. Use when the user says 'what's in my Things inbox', 'add this to Things', 'show today in Things', 'find Things tasks tagged X', or asks about repeating templates.
• tirith-config [Internal] — Operate a tirith setup — the terminal command analyzer guarding against homograph URLs, ANSI injection, and pipe-to-shell exploits. Use when editing ~/.config/tirith/policy.yaml, debugging a blocked command, choosing between allowlist / tirith run / TIRITH=0 bypass, or verifying with tirith doctor.
• update-changelog — Add or revise entries in a Keep-a-Changelog-format changelog.md, including version bumps and change-type groupings. Use when the user says 'update the changelog', 'log this change', 'bump the changelog', or after a notable edit in a skill or project that has a changelog.md.
• use-tailwind-v4 — Tailwind CSS v4 syntax and v3→v4 migration reference. Use when the user mentions 'Tailwind v4', 'upgrade Tailwind', @theme, @utility, or @import 'tailwindcss', or is working in a project whose config indicates v4.
• using-heavy-mcps — Use mcporter and jq to reduce token bloat from heavy MCPs like Sanity or Brain vault. Filter and compact tool outputs outside chat to feed only essential data back to the model.
• validating-startup-ideas — Find and validate startup ideas by mining user complaints, crafting premises, and navigating the idea maze. Use when discovering product opportunities, validating ideas, shaping solutions, researching user pain points, or exploring what to build.
• visual-keywords — Generate keyword strings for images, screenshots, or visual references — optimized for fuzzy search, not alt text or prose. Use when the user says 'keywords for this image', 'tag this for search', 'visual keywords', or wants searchable labels on an Eagle asset.
• web-design-guidelines — Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

Commands

• cleanup-dictation — Process dictated or stream-of-consciousness input into clean formatted output. Used for Superwhisper presets and similar dictation workflows.
• create-command — Guide for creating new custom Claude commands with proper structure.