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.
Plugin dependency-model from marketplace efitz-skills in ericfitz/skills. Commands read from the repo's manifest — 8 days ago.
configEnumerate the configuration a system must be supplied with to run — environment variables, config files, flags, and remote config — with what reads each key, whether it is required, and what default it declares. Read-only. Use when documenting deployment requirements or planning test environments. E
networkEnumerate the names, hosts, and ports a system must resolve and connect to — inbound listeners, outbound endpoints, DNS, proxies, and ingress. Nothing is resolved or probed. Read-only. Use when mapping a system's network surface or planning egress policy. Emits the dependency-model:discovery contrac
packageInventory the libraries a project ships with and at what versions — every ecosystem syft catalogues, with declared/locked/installed resolution and the dependency edges between them. Read-only. Use when auditing dependencies, planning an upgrade, or building a dependency graph. Emits the dependency-m
platformEnumerate the OS and cloud resources a system declares a need for — CPU, memory, disk, GPU, architecture, runtime versions, and managed cloud services. Every figure is a declared one; nothing is measured. Read-only. Use when sizing an environment or planning capacity review. Emits the dependency-mod
reportRender the dependency-model synthesis contract into a human-readable document — an inventory summary by category, the health definitions, the Mermaid dependency graph, cycles, and assumptions. Read-only. Use when a system's dependency and health picture needs to be handed to a reader rather than a d
securityEnumerate the secrets and permissions a system requires — what each credential is named, where it is read, and which policies grant what. Records names and locations only, never values. Read-only. Use when auditing a system's credential surface or planning least-privilege review. Emits the dependenc
serviceIdentify the out-of-project services a system needs — databases, caches, queues, object stores, search engines, and APIs — with the timeout, retry, fallback, and health-check declarations that bear on how each one fails. Read-only. Use when mapping a system's runtime dependencies or planning failure
synthesizeGather the six dependency-model discovery contracts for a repository, merge them into one graph, and derive which dependencies carry a failure-relevant health condition. Read-only. Use when a system's dependency inventory and health picture need to be assembled from the six discovery skills' output.
Localization/i18n toolkit: analyze missing keys, measure coverage, detect non-localizable strings, translate, validate translations, update JSON locale files, and backfill every locale. Use for i18n auditing, translation, and locale-file maintenance.
7 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
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.
5 commands
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Use Alibaba Open Code Review from local Codex.
2 skills
Claude Code skill for creating and presenting Slidev slidedecks
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.