← ClaudeAtlas

plumb-line-adoptlisted

Use when a builder wonders what plumb-line would do for their codebase or which part to adopt, or when, mid-task, they are building with a stand-in: stubbing a service that is not built yet, falling back to cached or last-known values when a source fails, filling a field with generated or sample data, mixing fixture, cached or LLM-produced data with real data. It answers yes, and: add it, and here is how to keep track of it (a label or marker, or plumb-line's provenance primitive where it fits). Inspects the repo and routes to the right skills and primitive integration. Read-only: recommends and hands off, never edits or installs.
slopstopper/plumb-line · ★ 4 · Code & Development · score 70
Install: claude install-skill slopstopper/plumb-line
# Adopt plumb-line — which part, on what REQUIRED READING FIRST: `reference/fit-map.md` (plugin root). If this file cannot be read, stop immediately and report: "Cannot route: `reference/fit-map.md` is missing or unreadable. Do not recommend from memory — the fit map is the source of truth for what the primitives are for." Read `reference/portable-principles.md` only if the conversation needs the principles named; the fit map is sufficient for routing. This skill is a concierge for the whole toolkit — the four sibling skills AND the run-time primitives. Its job is the question the docs cannot answer for a specific repo: *"what would I use this on, here?"* It recommends only. It never edits files, installs anything, or scaffolds code; every action belongs to the skill it hands off to, or, for a stand-in met mid-task, to the agent or builder doing the task. ## 1. Look — a lightweight, read-only scan Scan the repository for **routing signals only** (this is not an audit — do not read whole files; filenames, imports, and greps suffice): - HTTP ingestion: `requests` / `httpx` / `fetch` / `axios` whose results feed computation; caching or retry-with-cache logic. - Dataframes: `pandas` / `numpy` imports; `fixtures/`, `sample_data/`, or demo CSVs loadable by production-adjacent code. - LLM or agent surface: LLM SDK calls; fallback/canned-response branches; agent-generated artifacts consumed downstream. - Fakery near production paths: mock flags, `USE_MOCK`-style toggles,