Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

wawoodwa

@wawoodwa source repo

6 published skills

  1. ▌
    Context Kit Check · wawoodwa bundle
    Read-only integrity, wiring, and hygiene audit of a project context kit -- a CLAUDE.md entry point plus its docs/ tree (runbooks, changelog, history, status, sessions). Verifies the CLAUDE.md Version matches the changelog, changelog rows stay in reverse-chronological order, every runbook/doc is registered and exists, all relative Markdown links resolve, no orphaned docs, no committed secrets or leaked mount paths, dates are never in the future, session folders follow the dated notes.md convention, and status/history docs stay coherent; plus concurrency-safe rules for editing shared index files when multiple sessions or agents share a context. Use whenever the user wants to audit, validate, verify, lint, or health-check their CLAUDE.md or docs context kit -- before or after an end-of-session capture, a docs reorg, or adding a runbook, when inheriting a kit, or on asks like "are my docs consistent", "any broken links", or "did I commit a secret". Trigger even on terse asks like "check my CLAUDE.md".
    0
    installs
  2. ▌
    Context Kit Split · wawoodwa bundle
    Reorganize a project's markdown docs to cut per-session context load: move accumulated history (changelogs, completed-work logs, per-version lessons, module breakdowns) out of session-loaded entry-point docs (CLAUDE.md, README.md, status.md, large runbooks) into companion files, leaving a pointer plus a "where to add new content" rule behind. Substance is preserved verbatim; only its location changes. Trigger explicitly via "my docs have grown too large", "shrink CLAUDE.md", "split my docs", "extract the changelog", "reduce context for agents", or similar; an explicit request targets whatever file or section the user names, regardless of size. May also be offered proactively as a one-time soft by-the-way if you happen to notice an entry-point doc has grown large and history-dominated -- don't hunt for candidates, and drop it if declined. Skip when the doc is substantive current reference (its size is purposeful) or each shipped change already self-extracts.
    0
    installs
  3. ▌
    Context Kit Ingest · wawoodwa bundle
    Repeatably ingest a pre-context-system session into a project context kit -- an old chat export or share link, prior engagement notes, a ticket export, or another engineer's handover/transcript -- by pulling the material, distilling it to signal (never storing verbatim transcripts), saving assets to dated docs/sessions/ directories, interleaving a docs/history.md entry, updating the affected entity's file (customer, client, stakeholder, or tenant -- whichever the kit uses), capturing reusable lessons, and verifying with a read-only sub-agent plus the context-kit-check. Use whenever the engineer wants to import, ingest, backfill, fold in, or capture work done BEFORE this kit existed -- including phrases like "ingest this old session", "import this chat into the kit", "we did this work outside the kit", "fold this handover into history", or onboarding a new customer/client/stakeholder whose earlier work lives outside the kit. Trigger even on terse asks like "ingest this session" or "add this old chat".
    0
    installs
  4. ▌
    Context Kit Capture · wawoodwa
    Capture a finished workflow or troubleshooting session as a self-contained task .md file and update CLAUDE.md. Use when wrapping up a multi-step technical session or asked to document/save the work.
    0
    installs
  5. ▌
    Context Kit Steward · wawoodwa bundle
    Design-before-run meta-skill that keeps the Context Kit skill family coherent and evolving. It owns the shared conventions charter (references/CONVENTIONS.md) that every kit skill must honor -- work-start dating, newest-first ordering, multi-session concurrency, entity vocabulary, reference-don't-embed, hygiene, and skill-authoring limits -- audits each kit skill for drift from the charter, and harvests recurring lessons from real operating context kits to propose updates. Always produces an approval-gated proposal first and emits drop-in skill edits; it never auto-edits skills. Use whenever the operator wants to align, sync, audit, or evolve the context-kit skills, reconcile conventions across them, propagate one lesson into the whole suite, or asks 'keep my kit skills consistent', 'update the charter', 'do my context skills still agree', or 'propagate this across the kit skills'. Run it after changing any one kit skill, or after operating several kits, to catch cross-skill drift before it spreads.
    0
    installs
  6. ▌
    Context Kit Scaffold · wawoodwa bundle
    Scaffold a portable, name-agnostic starter kit for the next project -- any stack (Node.js, Python, PowerShell, ops/admin) -- by mining this project's accumulated docs, conventions, runbooks, agent-testing harness, and engineering strategies into a generic template tree under docs/genericcontext/. Produces a generic CLAUDE.md, stack-appropriate standards, five canonical runbook templates with empty lessons stubs, a sandboxed agent-smoke harness (restricted tester plus independent judge), an unattended-testing permission allowlist, a PORTING cheat-sheet, and a lessons-from-source-project.md that anonymizes and merges the portable strategies. Use whenever the operator wants to carry a project's hard-won patterns into a new one, or says 'generate generic context', 'scaffold next project from this one', 'extract docs as a starter kit', 'create a project template', or 'produce a generic CLAUDE.md'. Skip if the project has fewer than ~5 shipped changes, or back up first if docs/genericcontext/ already exists.
    0
    installs