localmin
Community@localmin · Kawasaki, Japan
Master of hai-furi. icon: https://x.com/kawara_pigeon_
Agent Skills by localmin
Showing 10 vetted skills indexed across 1 GitHub repositories.
localminplanning-workflow
Persists plan mode decisions and work-in-progress state in .claude/plans/ markdown documents.
localmininbox-capture
Captures Chrome tab URLs, summarizes articles, and appends them to a daily Inkdrop inbox note.
localminskill-curation
Evaluates, vets, and adopts agent skills via catalog lookup, rubric scoring, and vendor pinning.
localminweekly-review
Extracts read-later articles from Inkdrop inbox notes and organizes them into themed notebooks.
localminparallelization
Guides parallel subagent dispatch and task isolation decisions for agent workflows.
localminplan-doc
Generates structured plan documents under .claude/plans and registers them in a per-project INDEX.md.
localminmonthly-summary
Aggregates promoted Inkdrop notes into a monthly summary note via MCP.
localmincommit-pr-workflow
Executes commit, push, and pull request workflows following repository conventions.
localminnotebooklm-judge
Aggregates Inkdrop notes by tag and judges whether topics merit promotion to NotebookLM.
localmindevelopment-style
Enforces TDD cycles, test discipline, and code design principles when writing production code.
Frequently Asked Questions About localmin
FAQPage SchemaWhat tasks can I automate using localmin's skills?▼
You can persist planning discussions into .claude/plans/ documents, capture Chrome tabs into daily Inkdrop inbox notes, triage read-later articles weekly, build monthly note summaries, judge NotebookLM topic promotion, run TDD-disciplined coding, and execute convention-based commit, push, and PR creation.
Who are these skills designed for?▼
They target a single developer maintaining a personal dotfiles environment who uses Claude Code with plan mode, Inkdrop for note-taking, and NotebookLM for topic synthesis. They suit engineers wanting strict conventions for planning persistence, knowledge curation, and git operations.
How do the planning and resume workflows operate at runtime?▼
The planning-workflow and plan-doc skills write agreed plan-mode decisions into structured documents under .claude/plans/, registered in a per-project INDEX.md with WIP.md tracking. This lets work resume across sessions and after context compaction without losing design rationale.
What prerequisites and dependencies do these skills require?▼
They assume a Claude Code environment with plan mode, the Inkdrop note app with inbox and themed notebooks, Chrome for tab capture, NotebookLM for topic promotion, git hosting for PRs, and the dotfiles vendor mechanism with manifest.tsv pinning rather than APM.
How are new skills evaluated and adopted in this registry?▼
The skill-curation meta-skill reads references/catalog.md first, then runs staged cross-source search, a seven-axis rubric, and a mandatory waxa eval gate. Accepted skills are pinned into coding-agents/vendor/manifest.tsv through the vendor mechanism before adoption.