Skip to content

Skill catalogue

23 skills ship in skills/. wfx install --skills copies every one into ~/.claude and ~/.agents.

Skill What it does
approval-desk See what wfnexus runs are waiting on a human and resolve them — approve, reject, or answer a question. Trigger: what is waiting on me, approve that run, answer the agent’s question.
change-reviewer Adversarially review a diff you did not write: correctness, regressions, scope creep and missing tests. Trigger on: review this change, review the diff, check this PR.
cleanup-pr-writer Write a detailed, verifiable pull request for a dead-code removal: every removal with its location, evidence and risk, what was kept and why, bugs found, build/test counts before and after, and how to revert each commit — with every claim checked against the evidence by a calibrated classifier before it is published. Trigger on: write the cleanup PR, PR description for removals, describe this refactor PR.
dead-code-finder Inventory code that looks unused — unreachable functions, unused exports, unused dependencies, unused files — with tool output as evidence for every candidate. Finds; never deletes. Trigger on: find dead code, what is unused, cleanup candidates, inventory unused code.
dep-upgrader Upgrade a dependency and repair the breakage it causes, with the suite as the judge. Trigger on: bump a dependency, upgrade a package, fix breakage after an upgrade.
doc-syncer Make docs true to the code again with the smallest possible edit: for each doc statement a machine flagged (a path, symbol, flag or behaviour the code no longer has), prove from the code whether it is really stale, and if so rewrite only that statement, citing the code line that makes the new text true. Never touches history (ADRs, changelogs, proposals). Trigger on: fix stale docs, docs drift, the README is out of date, sync docs with code.
fix-author Implement the minimal correct fix for a reproduced bug on a feature branch, with tests, ready for review.
leader-brief Draft a leader’s cited brief (daily brief, meeting brief, meeting actions, weekly digest, decision log, 1:1 prep) from a collected evidence file — every line cites refs, nothing invented, draft only. Trigger: draft the brief, write draft.json from evidence, leadership brief.
pr-publisher Push an approved branch and open the pull request with gh, returning the PR URL.
pr-reviewer Adversarial review of a proposed fix — verify claims by running tests, hunt regressions and edge cases, approve or block.
prod-signal-triage Explain production signals (error logs, failing probes, stuck jobs, broken cron, exporter gaps) against the code: cause with file:line, impact, the smallest fix, and whether it is even this product’s. Evidence only, ‘unknown’ over a guess. Trigger on: triage these alerts, why is prod failing, explain this error spike, is this a real incident.
product-cartographer Map a product repository the way a new engineer and a new ops lead both need it: what the products are, the user journeys, where production signals live, and — most of all — the RECURRING MANUAL WORK people do around it (from runbooks, task files, issues, retros, specs). Evidence with file:line only. Trigger on: understand this product, map this repo, what does this codebase do, what work could we automate here.
repo-navigator Fast orientation inside an unfamiliar repository — build/test commands, layout, and locating the code behind a symptom.
reproduce-bug Turn a validated bug into a deterministic reproduction, preferably a failing automated test committed in the repo.
safe-remover Delete only the code an approved removal plan names, one commit per removal citing its evidence, cleaning up what the removal orphans (its tests, its docs), and proving the build and tests stay green after each one. Trigger on: remove the dead code, apply the removal plan, delete these unused functions.
test-author Write tests that would have caught a real defect, for code that currently has none. Trigger on: backfill tests, add missing tests, improve coverage where it matters.
usage-prover Adversarially prove each dead-code candidate IS used before anything is deleted — literal search across code, docs, skills, templates and config, indirect use, build tags, entry points — then have a calibrated classifier (wfx judge) score each one. Sorts candidates into remove / keep / bug / needs-a-human. Trigger on: verify dead code, is this really unused, prove before removing.
validate-bug Decide whether a bug report is actionable — plausible against the code, severity, affected component, and what is missing.
wfnexus-deploy Take a wfnexus workflow that works locally to the team server, git-natively: propose, approve, publish a version, schedule it, verify it is installed and scheduled there, then dry-run it. Trigger: deploy this workflow, ship it to the team server, publish and schedule it, run it every Friday.
wfnexus-setup Take a machine from nothing to a working wfnexus install on Docker, on free models, ending in READY or a named blocker. Trigger: install wfnexus, set up wfnexus, get wfnexus running, is my wfnexus ready.
workflow-author Turn work someone keeps doing by hand into a wfnexus workflow they can trust to run without them. Interviews them about the work — not about YAML — then drafts, dry runs its own draft, and hands over with the assumptions attached. Trigger on: write a workflow, author a workflow, automate this, edit this workflow, add a step, my workflow is failing, turn this into a workflow, convert my script/Actions file.
workflow-recipes Build a working wfnexus workflow by ANSWERING QUESTIONS, not writing YAML. Asks what work the person wants off their plate, matches it to a proven recipe (production watch, alert triage, CI failure doctor, dead-code remover, docs drift, dependency upgrade, verified PR review, issue triage, ticket triage and reply drafts, weekly KPI narrative, invoice/expense exceptions, NDA triage), asks only that recipe’s questions one at a time with a default for each, refuses answers that would make it a toy, then assembles, validates and dry-runs the workflow and installs it only on a yes. Trigger on: I want to know when X starts failing, take this off my plate, build me a workflow, automate this for me, workflow from a recipe, set up a watch/triage/review.
workflow-scout Turn a product’s recurring manual work into wfnexus workflow candidates that are WORKABLE, not toys — each checked against the 7-point bar (real trigger, system of record, typed output, verification, human gate, no silent failure, a success number), matched to a proven pattern from the top-6-per-category catalogue, and ranked by value. Trigger on: what workflows should we build, propose automations for this repo, workflow ideas for this product.