A static catalog of Homebrew tools, Neovim plugins,agent skills, and template repositories — generated from source repositories and synced on a schedule.
Command-line instruments, packaged for Homebrew — installed straight from the tap.
agit
AI-agent version control
crap
Change Risk Anti-Patterns (CRAP) scoring for TypeScript, Rust, Go and Lua
deadwood
Unused file and dependency analysis for TypeScript, Rust, Go and Lua
hopt
A TUI to interact with The Hoptimist store
mediacreator
Generate media via fal.ai and kie.ai from the CLI and save it to disk
newbrew
Browse and inspect new Homebrew formulae from your terminal
skill-eval
Automated CLI for evaluating AI agent skills
Small measures of UI and behaviour for Neovim, installable with lazy.nvim or vim.pack.
Portable instruction sets for coding agents — generated from the upstream SKILL.md sources.
acquire-codebase-knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like \"map this codebase\", \"document this architecture\", \"onboard me to this repo\", or \"create codebase docs\". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
agent-governance
Use this skill when building AI agents that call external tools, implementing policy-based access controls, adding semantic intent classification, creating trust scoring systems, building audit trails, or enforcing rate limits and content filters on agents.
agent-instructions
Use when creating or updating agent instruction files (AGENTS.md for Pi, copilot-instructions.md for Copilot, per-path guides, or AGENTS.md router) — especially when instruction files are too long, generic, or stale, or when agents repeatedly make the same avoidable mistakes.
agent-supply-chain
Use this skill when generating SHA-256 integrity manifests for agent plugins, verifying that installed plugins match their manifests, detecting tampered files, auditing dependency pinning, or building provenance chains for plugin promotion.
agentic-eval
Use when designing or implementing an evaluation loop for AI agent outputs — reflection loops, evaluator-optimizer pipelines, LLM-as-judge scoring, or rubric-based iteration. Not when running an existing test suite or reviewing a completed artifact without iterating.
api-smoke-validation
Use when running quick, repeatable API smoke tests after changes with hurl, including auth, status-code, response-shape, endpoint sanity, and pre-integration health checks.
ast-grep
Use when you need ast-grep structural search, linting, or safe codemod rewrites, especially for requests that mention ast-grep, sg, codemod, rule files, or syntax-aware edits instead of plain-text search.
astro-seo
Audit and improve SEO for Astro sites, including metadata, structured data, sitemaps, indexing, Open Graph images, schema endpoints, and related search visibility setup.
autoresearch
Use when running autonomous iterative experiments to optimize a measurable metric on an existing codebase — not for writing tests or diagnosing a specific failure.
aws-lambda-go-deployment
Use when deploying or debugging Go-based AWS Lambda packaging, bootstrap, runtime, or handler issues — not when the main failure is SAM stack wiring, IAM OIDC auth, or a generic GitHub Actions run failure.
ci-images
Validate CI checks locally and manage Docker image publishing workflows. Use when changing build inputs (generated code, formatting, tests), preparing a release, or verifying that image tags are correct.
cloudflare-d1-query-tuning
Tune slow Cloudflare D1 queries and D1-backed repository access without schema or migration changes. Use for N+1 access, over-fetching, pagination, or runtime D1 query-shape issues.
code-generation
Run and troubleshoot repository code generation after detecting the generator contract. Use when schema, query, spec, or template inputs changed, or generated output may be stale.
code-intelligence
Use when navigating or refactoring code — choosing between LSP, rg, or semantic search tools; an LSP call returns empty and you need to know if it failed; or a tool substitution needs disclosure.
code-tour
Use when asked to create a .tour walkthrough — onboarding, PR review, RCA, architecture, or any persona-targeted step-by-step code narrative. Not for codebase exploration without a .tour file output.
configuration-env
Configure applications safely through environment variables, .env files, and repo-owned runtime config such as Wrangler bindings. Use for startup failures, environment drift, or deployment bootstrap.
context-map
Use when the user explicitly wants a pre-edit scoping pass — mapping candidate files, tests, and reference patterns before implementation. Not for general multi-file tasks unless the user asks "what files are involved" or requests a context map.
database-migrations
Create, apply, inspect, and recover database schema migrations after detecting the repository's migration contract, including Cloudflare D1 via Wrangler across local, preview, and remote. Use when changing persistent schema, adding indexes/constraints, or troubleshooting migration state or schema drift.
docker-compose-dev
Run a service stack locally using Docker Compose for prod-like development (e.g. PostgreSQL + app). Use when you need a real DB backend, multi-service integration, or want to reproduce production-like behavior locally.
fallow
Use when auditing JS/TS code health with Fallow - dead code, duplication, boundaries, or cleanup; not for debugging failures.
finishing-a-development-branch
Use when implementation work is complete and you need to decide how to integrate the branch — merging locally, creating a PR, keeping the branch, or discarding the work.
git-signing-troubleshoot
Use when commits, tags, or pushes are blocked by GPG or SSH signing failures — including 1Password op-ssh-sign errors, failed to fill whole buffer, or misleading op whoami output, not when the main task is branch integration, PR handling, or secret-scan triage.
git-worktrees
Set up and manage isolated git worktrees for parallel tasks and agent lanes, and configure or operate Worktrunk (wt) for worktree lifecycle, hooks, LLM commits, and parallel agent workflows. Use when worktree setup, recovery, or wt configuration is the real need, not generic planning or implementation guidance.
github-actions-failure-triage
Diagnose and minimally fix failing GitHub Actions runs in repositories already using GitHub Actions. Use when a workflow, job, or check fails after a workflow edit, action bump, runner, cache, or matrix change and the goal is a targeted fix or precise explanation.
github-actions-local-repro
Use when a GitHub Actions failure needs local reproduction with act before pushing, especially for workflow logic or step-level regressions, but not when the failure depends on org-managed runner or secret policy.
github-cli-pr-workflow
Use when a branch needs GitHub CLI PR lifecycle work, like creating or updating a PR, watching checks for a pushed head SHA, or preparing PR handoff before review.
github-presence
Audit and improve GitHub profile, organization, and repository presentation. Use for profile READMEs, pinned repositories, README quality, community health files, templates, and repo metadata.
go-cli-development
Develop, structure, and release Go CLI tools. Use when building a new Go CLI, adding subcommands or flags, wiring config, formatting output, setting up goreleaser + Homebrew distribution, or debugging CLI-specific behavior — not for build failures or test debugging.
go-docker-builds
Containerize Go services with production-ready multi-stage Docker builds. Use when writing or debugging a Dockerfile for a Go service, setting up static compilation for scratch/distroless images, adding health checks, or wiring image builds into CI — not for Docker Compose local dev stacks or non-Go Dockerfiles.
go-error-patterns
Use when Go error-handling design or function-type mismatches surface — including `func(string) error` vs concrete constructors, package-local type aliases, or concrete-vs-interface error choices, but not when the immediate task is a build or test failure.
goreleaser-release-pipeline
Use when setting up, debugging, or fixing a GoReleaser v2 release pipeline — especially Release Please tag issues, missing release assets, or publish jobs that fail after a release is created, not when the main task is generic CI triage or PR handling.
graphify
Build and query persistent Graphify knowledge graphs from code, documents, papers, images, or video. Use when the user asks to graphify a corpus, needs graph-based mapping, path, or community analysis, invokes Graphify commands, or asks a corpus question when graphify-out/ already exists.
grill-me
Use when the user wants to be interviewed or stress-tested about a plan, design, or decision, including explicit requests to 'grill me'. If they also mention CONTEXT.md, ADRs, or a domain glossary, use the documentation mode; otherwise keep the session pure interrogation and do not create docs.
http-api
Keep HTTP APIs honest: sync OpenAPI contracts with handler behavior, and write or debug end-to-end HTTP integration tests for handlers, middleware, auth, and endpoint contracts. Use when endpoints, schemas, auth, or error shapes change, or HTTP integration tests need adding or fixing.
implementation-review
Review completed code changes, diffs, and implementation revisions for merge readiness, or draft and harden an implementation plan before work starts (plan mode). Use for code review, plan review, named reviewer approval, validation gaps, regressions, security risk, or scope drift.
knip
Use when a JavaScript or TypeScript project needs Knip to find unused dependencies, exports, files, or unresolved imports; not for runtime failures or dormant-task recovery.
make-interfaces-feel-better
Polish existing interfaces when the UI feels off through better radius, shadows, typography, motion, and micro-interactions. Use when asked to make an existing UI feel more refined, or to tighten hover, press, and enter/exit details.
modern-web-guidance
Modern web platform API guidance for avoiding legacy HTML, CSS, and JavaScript patterns. Use when implementing web interfaces, forms, accessibility, performance, browser APIs, or animations.
neovim
Edit, debug, and validate Neovim Lua configurations, and develop, test, and release Neovim Lua plugins. Use for init.lua and plugin-manager work (vim.pack, lazy.nvim), LSP/completion wiring, treesitter, startup behavior, or for building plugins with plenary tests, GitHub Actions CI, vimdoc, and release automation.
observability-metrics
Validate and operate application /health, /metrics, and logging behavior. Use when adding metrics, changing observability endpoint auth, or verifying deployment telemetry — not for general production debugging where telemetry health is not the question.
repository-adapters
Implement or modify database repository adapters. Use when adding adapter methods, changing queries, or mapping database errors while preserving domain boundaries.
resolve-open-loops
Use when the stabilisation-guard blocks the session because of active open_loop or assistant_goal memories, or when the user explicitly asks to review and close out pending items in Lore.
reverse-prompt
Rewrite a rough request into a repository-grounded execution brief before research, planning, or implementation. Use when the user asks for a sharper prompt, better request, or contract-shaped brief.
review-comment-resolution
Apply pull request review feedback by assessing comments, fixing valid concerns, pushing the branch, and waiting for checks. Use when reviewer feedback must be carried through to completion, not just reviewed.
rpi-workflow
Apply a Research → Plan → Implement → Validate workflow for multi-phase work that benefits from explicit phase boundaries. Use when the task is complex, spans many files, or needs durable progress artifacts — not for small fixes, single-file edits, or narrow specialist workflows.
sam-cloudformation
Use when AWS SAM templates, CloudFormation stacks, or SAM deploys fail on YAML, transforms, resource wiring, or rollback state, or when the deploy caller gets AWS sts:AssumeRole or sts:AssumeRoleWithWebIdentity AccessDenied — not when the Lambda binary itself or Terraform-owned infrastructure is the primary blocker.
schema-boundary-typing
Introduce or refine runtime schema validation at untrusted boundaries so static TypeScript types stay truthful. Use when API, storage, or parsing input flows into typed code without runtime validation.
secret-scan-triage
Use when secret scanning with gitleaks reports findings that need fast triage, containment, and false-positive adjudication before code changes or merges continue.
security-basics
Apply security and privacy guardrails to application code. Use when touching authentication, secrets, sensitive endpoint exposure, or logging of credentials/PII — not for general request-handling changes without a security dimension.
session-store-history
Search and summarize past work from the `session_store` database when the user asks what they worked on before, how a similar problem was handled, or which session, PR, issue, branch, or file changed something.
skill-creator
Build, upgrade, or standardise a specific skill package in the current catalog. Use when adding a skill directory, reconciling its authoring contract, improving metadata/examples/evals, or tightening trigger boundaries — not for one-off prompt advice.
systematic-debugging
Use when encountering any bug, test failure, unexpected behavior, or persistent error before proposing fixes — especially under time pressure, after multiple failed attempts, or when the root cause is unclear.
templ-templates
Edit and troubleshoot server-side HTML templates (.templ files for Go's templ framework), including regeneration and handler wiring. Use when changing UI components, layouts, or page templates.
terraform-skill
Use when writing, reviewing, or debugging Terraform/OpenTofu — modules, tests, CI/CD, security scans, or state operations.
test-driven-development
Use when the user explicitly asks for test-driven development (TDD), a red-green-refactor cycle, or test-first implementation — not for general feature work, bug fixes, or refactoring unless TDD discipline is specifically requested.
testing-workflows
Write, run, and debug Go tests, unit and integration, and diagnose Go build, toolchain, and CI-parity failures (GOROOT/GOTOOLDIR overrides, govulncheck stdlib findings, TempDir race flakes, local-green CI-red). Use when adding test coverage, debugging test failures, or when go build or CI fails for environmental reasons.
to-issues
Use when the user wants to turn a plan, spec, PRD, or approved idea into independently grabbable issue-tracker slices, or first needs a PRD synthesized from repository and conversation context for that handoff. Not when repository discovery or a generic handoff artifact is the real need.
tsc-error-triage
Diagnose and resolve TypeScript compiler errors by finding the smallest root-cause fix before editing call sites. Use when tsc failures burst after a refactor, upgrade, or config change and leaf-by-leaf patching would be wasteful.
tsconfig-hardening
Tighten and rationalize TypeScript configuration safely, especially when enabling stricter compiler checks incrementally. Use when enabling strict flags, untangling a tsconfig chain, or fixing module-resolution or emit config drift.
type-test-authoring
Write compile-time type tests that protect public TypeScript APIs, inference behavior, and negative cases. Use when locking down generic helpers, utility types, or an inference regression with tsd, expectTypeOf, or @ts-expect-error fixtures.
typescript-any-eliminator
Use when TypeScript source contains explicit `any` in application code, shared helpers, DTOs, or API layers that should be narrowed without changing runtime behavior — or when a reviewer or lint rule flags unsafe `any` usage.
verification-before-completion
Use when about to claim work is complete, tests pass, a bug is fixed, or a build succeeds.
workflow-contracts
Use when a task needs a durable handoff artifact for planning, review, or execution in agent-driven workflows — not just a chat summary.
writing-and-editing
Draft, co-author, and edit documents, audit prose readability, and review short audience-facing metadata strings. Use when the primary task is writing quality: a new or restructured doc, iterative co-authoring with reader feedback, a readability pass, or copy review.
Public GitHub repositories marked as templates — scaffolding for your next project.
astro-site-template
Astro starter template for building and deploying sites to Cloudflare Pages.
elysia-crud-template
Starter CRUD API template with Elysia, Drizzle ORM, Postgres, and Bun.
go-api-template
Minimal Go API template with Chi, Docker, CI, and GHCR publishing.
nvim-plugin-template
Template repository for building and releasing Neovim plugins with tests and CI.
ts-package-template
TypeScript package template with dual CJS/ESM builds, testing, linting, and CI.