Claude Skills by dwarvesf

github.com/dwarvesf

24 skillsA× 243 installs33 views

Implementation NotesADelta log only; the spec carries the design.developmentgoVotes: 0GitHub stars: 10
SpecsAGenerated: 2026-07-31 Status: APPROVED (operator pre-approved design; adversarial validate overridden in the gate ledger) Lane: full Phase B of the feature-registry program (Phase A: SPEC-219, merged as PR #323). The registry generator makes feature inventory drift mechanical to detect, but nothing yet closes the loop against the hand-derived `docs/workflow-paths.md` path index: a feature can be live in `docs/FEATURES.md` yet missing from the path map, or linger in the path map after removal....developmentgoshellVotes: 0GitHub stars: 10
VerificationABehavioral proof per `proof-gate.sh contract`'s bar for this task type (`class=behavioral`, no deploy/migration/schema keyword in the diff): the real primary flow (`tests/test-meta.sh`) run end to end, with a negative control on the one test-file assertion this branch touches.developmentgobashVotes: 0GitHub stars: 10
VerificationA| AC | Claim | Status | |---|---|---| | AC-1 | SKILL.md with frontmatter + four-slot table | MET | | AC-2 | Tier 1 mechanical: freshness refusal + both-directions cross-check | MET (live run below) | | AC-3 | Tier 2 delta-only subagent, no delta = no dispatch | MET (stated; live run had zero delta, zero dispatch) | | AC-4 | PR-gated apply | MET (this PR is the gate) | | AC-5 | README table + header count, audit-loop Known instances | MET | | AC-6 | BACKLOG: ID-458 shipped row + ID-407 registry-sdevelopmentbashVotes: 0GitHub stars: 10
GeneratedA> GENERATED by `lib/gate/proof-table-gen.sh` from the gate/run ledger (`~/.local/state/dwarves-kit/logs/runs/feature-map-skill.log`). Do NOT hand-edit -- regenerate instead. Companion run-table, not the canonical `proof-of-done.md` (SPEC-016: generators write under `docs/verification/generated/`, never the canonical). Lane: fulldevelopmentbashVotes: 0GitHub stars: 10
PromptsACLASS-LEVEL skills: each a rich SKILL.md (plus optional `references/` for session-specific detail), matched by a future agent on its `description`. One broad umbrella with labeled subsections beats five narrow one-session siblings. A library of hundreds of narrow one-bug skills is a FAILURE. - The user corrected your style / tone / format / verbosity / approach. Frustration ("stop doing X", "too verbose", "just give me the answer", "you always do Y") is a FIRST-CLASS signal. - The user correc...developmentrustdebuggingVotes: 0GitHub stars: 10
Skills DirectorySkills Directory 3 slots · $399/mo · one ad per page · sponsors can never buy grades.See placements
GoalsA**Merge policy:** auto **Time budget:** 3-4 hours. **Proof:** run-table: the skill fires on "show me the ledger state / my debt / telemetry / token cost" (trigger match) · it queries via the 02 `ledger` CLI (not a re-implementation) · it renders IN-TERMINAL using bot-reply-formatting (tables/bars) · it renders a web ARTIFACT (claude.ai) for share/review · negative control: BOTH surfaces render from the SAME 02 query output (no divergent second data path). Capture a terminal-render sample + an...developmentgobashVotes: 0GitHub stars: 10
SpecsAGenerated: 2026-07-04 Status: VALIDATED Lane: normal (lane-classify returned tiny; escalated per goal-file explicit /spec+/spec-validate mandate, see impl-notes) Depends-on: SPEC-127 (the `ledger` CLI, shipped, PR #673, merged to main as e6ff875b)developmentpythongoVotes: 0GitHub stars: 10
Render SkillA> Per-feature record. The canonical multi-feature index is > [`../../proof-of-done.md`](../../proof-of-done.md); this file is its `render-skill` > feature detail. | | | |---|---| | **Profile** | data/CLI tool addition (behavioral, read-only, pure-function render layer) | | **Proof class** | data-tool (recorded live run + negative control + reproducible) | | **Spec** | [`../../specs/SPEC-128-render-skill.md`](../../specs/SPEC-128-render-skill.md) |developmentpythongoVotes: 0GitHub stars: 10
Backlog ReconcileAUse to audit a repo's `_meta/BACKLOG.md` Active queue against reality, "audit the backlog", "reconcile the board", "is the board still true", "dọn backlog", "rà soát backlog", or a scheduled backlog-reconcile run. NOT for filing new items onto the board, NOT for a single known-stale row (just fix it), NOT for the kit's own FEATURES/workflow-paths pair (topology-drift).developmentrustgoVotes: 0GitHub stars: 10
Ci DriftAUse for the whole-estate CI audit, "audit the CI", "are the runners clean", "check the release pipeline", "ci drift", "stale workflows / secrets / runners", or a scheduled CI-audit cadence run. NOT for one failing run (/kit:debug), NOT for doc prose (doc-drift).developmentrustgoVotes: 0GitHub stars: 10
Doc DriftAUse for the whole-estate doc audit, "run the doc-drift loop", "audit the docs against the code", "are the docs still true", "doc drift sweep", "check every doc claim", or a scheduled doc-audit cadence run. NOT for diff-scoped doc sync inside a build cycle (/kit:docs), NOT for dated records like specs, research, retros, NOT for one known-wrong doc (just fix it).developmentgobashVotes: 0GitHub stars: 10
Gauntlet Proof AuditAUse to audit the gauntlet records, "are the ROUNDS.md records honest", "verify the proof corpus", "check each run record against its evidence", "audit the gauntlet corpus", "is the gauntlet proof trustworthy", or a scheduled run. NOT for re-running probes or rounds (`/kit:gauntlet` itself), NOT for the corpus-level stats projection (`lib/gauntlet/stats.sh`), NOT for non-gauntlet records.developmentrustgoVotes: 0GitHub stars: 10
Get Api DocsAFetch curated API documentation using Context Hub (chub) before coding against any external API. Use when the task involves calling a third-party API (Stripe, OpenAI, Airwallex, Notion, etc.) to prevent hallucinated parameters and deprecated endpoints.developmentgobashVotes: 0GitHub stars: 10
Loop EngineeringAUse to design or add a new bounded loop to the kit's SDLC orchestration ("design a new loop", "is this worth a loop"), or mentions the Karpathy loop / autoresearch / hill-climb / search-and-select prompt or parameter tuning. NOT for a one-off in-session Stop-hook goal (use goal-craft), NOT for the debug loop (already exists, use /kit:debug), NOT for building the loop's actual code.developmentgobashVotes: 0GitHub stars: 10
Memory TidyAUse when auditing, consolidating, or cleaning a repo's .claude/memory store, "dọn memory", "memory tidy", the biweekly memory audit, duplicate or stale memory notes, MEMORY.md index drift, or a scheduled memory-tidy audit. NOT for the built-in machine-local auto-memory under ~/.claude/projects, NOT for editing a single note (just edit it).developmentgogitVotes: 0GitHub stars: 10
ObserveAQuery and render the kit's control plane from an agent session. Use when asked about the fleet's runs, gate verdicts, conformance, spend/tokens/cache economics, the cognitive-debt score, replaying a recorded run, or building/refreshing the observability dashboard. Trigger phrases include "dashboard", "control plane", "how much did we spend", "token usage", "cognitive debt", "fleet stats".developmentpythonbashVotes: 0GitHub stars: 10
Repo HygieneAUse for the whole-repo decay audit, "run the repo-hygiene loop", "what has rotted in this repo", "is anything mis-shelved", "dọn repo", or a scheduled cadence run. NOT for the machine surface outside a git repo (disk-reclaim), NOT for doc claims drifting from code (doc-drift), NOT for board rows (backlog-reconcile), NOT for one file you already know is stale (just move it).developmentgobashVotes: 0GitHub stars: 10
Skill ReviewAReview and promote skill drafts that skill-curator staged from past sessions. Use when the user runs /skill-review, says "review my skill drafts", "promote a staged skill", or asks what skills the self-improvement loop proposed. Lists drafts under ~/.claude/skill-proposals/, runs the inline skill quality bar on each, then promotes the approved ones into ~/.claude/skills/ or rejects them.developmentbashVotes: 0GitHub stars: 10
StatsAQuery or render ledger state and propose backlog rows off anomalies. Use when asked to SEE it -- "show me the ledger state", "my debt", "understanding debt", "telemetry", "token cost", "kit runs", "render the ledger" -- or to check it -- "any ledger anomalies". NOT for editing/mutating any ledger. NOT for ad-hoc SQL exploration. NOT a persistent TUI/app.developmentrustgoVotes: 0GitHub stars: 10
Topology DriftAMaintainer-only. Use to audit THIS KIT's OWN feature estate against its path map, "run the topology-drift loop", "feature inventory drift". NOT for a consumer/adopter repo, NOT for a target project (/kit:feature-map), NOT for regenerating the registry, NOT for whole-doc prose drift (doc-drift), NOT for one known-missing feature.developmentgoshellVotes: 0GitHub stars: 10
Web DriftAUse for the live-website agent-readiness audit, "run the web-drift loop", "web drift sweep", "check the public sites", or a scheduled cadence run. NOT for docs/code in a checkout (doc-drift), NOT for CI/release state (ci-drift), NOT for the kit's feature registry (topology-drift), NOT for page-speed/Core Web Vitals, NOT for answer-engine citation, NOT for fixing a site (files rows only).developmentjavascriptpythonVotes: 0GitHub stars: 10
Kit BoardARead the state of the boards and explain the daily brief, using the dwarves-kit `board` command. Triggers: "how are the boards", "how many boards are over threshold", "what is waiting in triage", "what needs my decision", "explain the brief", "is board sync healthy", "what did the bots do". Read-only: it runs a dry run and never posts, never moves a card, never edits a board.developmentVotes: 0GitHub stars: 10
Kit PrecedentALook up what already exists before proposing a new tool, script, skill, cron, or memory note, using the dwarves-kit `precedent` command. Triggers: "should we build X", "do we already have something for X", "is there a script that does X", "have we done this before", or any plan that would add a new tool. Read-only: it searches and quotes the hit, it builds nothing.developmentVotes: 0GitHub stars: 10