dry-run

Dry-run the Senzing Bootcamp plugin against live MCP schemas, real filesystems, and human walkthroughs.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill dry-run-docktermj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dry-run
Source: https://github.com/docktermj/senzing-bootcamp-claude-plugin-development/tree/main/.claude/skills/dry-run
Command: npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin-development --skill dry-run-docktermj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Pillow, numpy, and includes scripts (resource) components.

What problem does it solve? Static audits and offline test suites can only confirm a Claude Code plugin agrees with itself; they cannot detect where the plugin disagrees with the real world — live MCP server schemas, actual filesystem behavior, rendered artifacts, or human answers. This Skill finds that defect class by executing the Senzing Bootcamp plugin rather than reading it. ## Core Features & Use Cases - Phase 1 — MCP call contracts: Verifies every documented MCP call against the live Senzing MCP server's schemas, re-asks dated negative claims, and cross-checks the server's confabulation list. - Phase 2 — Hooks and scripts: Executes every hook entry and bundled script against a realistic scaffolded bootcamp project, asserting on artifacts and exit codes rather than exit status alone. - Phase 3 — Conversational layer: Walks the bootcamp with the maintainer answering as the Bootcamper, starting analysis at a chosen module to reach later modules before context runs out. - Coverage reports: Ships coverage_reports.py with invariants, affected, negatives, unmarked, and shipped reports that point audits at unguarded conformance gaps. - Use Case: A maintainer preparing a release runs all three phases to confirm the plugin actually works — catching defects like a mapping_workflow call missing its required workspace_dir parameter that three audits and 399 passing tests missed. ## Quick Start Ask the assistant to dry-run the Senzing Bootcamp plugin and specify which of the three phases to run.

Frequently Asked Questions about dry-run

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I dry-run a Claude Code plugin to find real defects?▼

Run the three phases in order: verify every MCP call against the live server schemas, execute all hooks and bundled scripts against a scaffolded project, then walk the conversation with a human answering. Each phase targets a defect class static analysis cannot see.

What does the dry-run skill test in the Senzing Bootcamp plugin?▼

It tests MCP call contracts against live server schemas, hook entries and bundled scripts against a realistic filesystem, and the conversational flow with a maintainer playing the Bootcamper. It also runs coverage reports listing uncited invariants and stale negative claims.

Can the conversational phase be self-played by the assistant?▼

No. The plugin forbids fabricating Bootcamper answers, and an assistant grading its own discipline proves nothing. If the maintainer is unavailable, phase 3 must be reported as untested rather than approximated.

Why does the dry-run forbid calling submit_feedback?▼

Calling submit_feedback would file junk upstream or transmit a real name and email to Senzing's servers. The skill verifies the tool's schema only and never invokes it, keeping all dry-run activity on the local machine.

What dependencies does the dry-run skill need?▼

Phase 1 needs access to the live Senzing MCP server. Phase 2 needs python3, and the label-occlusion helper additionally needs Pillow and numpy plus a headless browser. The coverage reports are stdlib-only and read-only.

Where should dry-run findings be recorded?▼

Each finding goes into a spec file under specs/ before any fix, following the issue template with problem, root cause, and acceptance criteria. Outcomes are then recorded in specs/IMPLEMENTED.md so findings survive the session.