Dependency discovery toolkit: enumerate what a system depends on across six categories — packages, out-of-project services, configuration, secrets and permissions, OS and cloud resources, and network paths — each with the failure-relevant declarations (timeout, retry, fallback, health check) found for it. Static and read-only; emits a versioned JSON contract consumed by downstream analysis.
8 skills
Portable CATS API fuzzing toolkit: bootstrap per-repo config (init), run fuzz campaigns through config-declared shell hooks (run), query and render results from SQLite (report), triage true positives into a remediation plan (analyze), and manage declarative false-positive rules (fp). Repo-specific setup lives in .local/cats/config.yaml; false-positive rules live in a committed YAML file.
5 skills · 1 agent
Developer toolkit (sem-powered): annotate code with durable SEM@<sha> intent markers (sem-annotate), keep them maintained via a project convention (sem-auto), and find dead code + duplication and produce a ranked plan (dedupe). Uses the sem CLI entity graph. Supports Go, TypeScript/JavaScript, and Python.
3 skills · 3 agents
Logseq graph toolkit for a local classic (file-based) graph: capture notes/TODOs into journals or pages (capture), answer questions from the graph (query), find consistency problems (lint), merge/dedupe and restructure pages (organize), and import notes from an Obsidian vault (from-obsidian). Hybrid file/HTTP-API access with automatic graph discovery.
5 skills
Project discovery toolkit: identify what a codebase is built with (stack), what its requirements documents, PRDs, specs, and wiki pages say it must do (docs), how it deploys and what it depends on (topology), and what workflows its users actually perform (journeys). Read-only inference backed by a deterministic inventory script; emits versioned JSON contracts consumed by other plugins.
5 skills
Integration test design toolkit: discover a project's test conventions and how integration tests are separated (conventions), assess the quality of existing tests for over-mocking and misleading coverage (critique), find state-establishment and teardown affordances (state), and synthesize a prioritized scenario plan from confirmed customer journeys and documented requirements (design). Reports conflicts between what the documentation requires and what the code does. Read-only discovery; requires the profile plugin.
4 skills