skills.rest
docktermj
docktermjCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dry-run

Validate Senzing Bootcamp Claude plugin operations through MCP contract tests, filesystem hooks, and conversational audits.

Updated Jul 13, 2026
Search Tags:#automation#testing#validation#audit#mcp#senzing
One-click install
npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin --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/tree/main/.claude/skills/dry-run
Command: npx skills add https://github.com/docktermj/senzing-bootcamp-claude-plugin --skill dry-run-docktermj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the gap between static code analysis and real-world execution by verifying that the Senzing Bootcamp plugin functions correctly against live MCP schemas, actual filesystems, and human-in-the-loop interactions.

Core Features & Use Cases

  • MCP Contract Verification: Ensures all tool calls, parameters, and enums align with the live Senzing MCP server.
  • Hook and Script Testing: Executes plugin hooks and utility scripts against a realistic, scaffolded project environment to catch runtime defects.
  • Conversational Audit: Facilitates a structured walkthrough with a maintainer to validate the plugin's conversational flow and adherence to interaction invariants.

Quick Start

Execute the dry-run skill to initiate a full audit of the plugin against the live Senzing MCP server and local project environment.

Frequently Asked Questions about dry-run

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

FAQPage Schema
How do I validate Senzing plugin MCP contracts and filesystem hooks?▼

Validate Senzing plugin contracts by running an end-to-end audit that tests MCP call parameters, filesystem hooks, and conversational logic against a live Senzing MCP server to ensure operational reliability.

Do I need Python 3 and a live Senzing MCP server to test plugin integrity?▼

Yes, testing plugin integrity requires Python 3 and access to the Senzing MCP server to perform comprehensive end-to-end verification of tool calls, filesystem hooks, and conversational logic.

What is the best way to audit conversational logic in a Senzing Bootcamp plugin?▼

Audit conversational logic by facilitating a structured walkthrough with a maintainer to validate the Senzing plugin's conversational flow and verify adherence to interaction invariants during maintenance workflows.

How does plugin hook testing catch runtime defects in Senzing MCP environments?▼

Plugin hook testing executes utility scripts and hooks against a realistic scaffolded project environment, catching runtime defects that static code analysis misses in real-world Senzing MCP execution.

When should I use a dry-run validation instead of static code analysis for Senzing plugins?▼

Use dry-run validation when you need to verify Senzing plugin functionality against live MCP schemas, actual filesystems, and human-in-the-loop interactions, bridging the gap between static analysis and real-world execution.

Related Skills

Explore More Software Engineering Skills→
docktermjdocktermj

module-03b-truthset-visualization

Load the Senzing Truth Set and generate a D3-based entity resolution visualization.

Community
Advanced
docktermjdocktermj

implement-spec

Implement developer-defined specifications with live Senzing MCP server verification.

Community
Advanced
diegosouzapwdiegosouzapw
108

recce-mcp-e2e

Execute end-to-end verification of MCP server changes against a real dbt project.

Community
Advanced
adityaarsharmaadityaarsharma
2

orbit-wp-security

Detect security vulnerabilities in WordPress plugin PHP source code via static analysis.

Community
Advanced