skill-integration-tester

Validate CLAUDE.md multi-skill workflows for skill existence, JSON contracts, and handoffs.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/MileniumTick/skills --skill skill-integration-tester-mileniumtick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-integration-tester
Source: https://github.com/MileniumTick/skills/tree/main/skills/skill-integration-tester
Command: npx skills add https://github.com/MileniumTick/skills --skill skill-integration-tester-mileniumtick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Validates multi-skill workflows defined in CLAUDE.md by ensuring all referenced skills exist, that inter-skill data contracts (JSON schema) are compatible between steps, and that file naming conventions and handoffs are correct. It helps prevent pipeline breakages before release and during CI.

Core Features & Use Cases

  • Validate that each step's skill is present and correctly named
  • Check producer → consumer handoffs against defined contracts
  • Generate JSON and Markdown reports, plus synthetic fixtures for dry-run validation
  • Run as a CI pre-check to catch breaking changes to skill interfaces

Quick Start

Run the integration tester against CLAUDE.md to validate all defined workflows.

Frequently Asked Questions about skill-integration-tester

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

FAQPage Schema
How do I validate multi-skill workflows defined in CLAUDE.md?

Validate multi-skill workflows by running an offline Python tool that checks CLAUDE.md for skill existence, inter-skill JSON schema contracts, and handoff integrity to ensure pipeline health.

Can I check inter-skill JSON schema contracts before a CI release?

Yes, you can check inter-skill JSON schema contracts as a CI pre-release check. The tool validates producer to consumer handoffs against defined contracts to catch breaking changes to skill interfaces.

How do I generate dry-run fixtures and reports for integration testing?

Generate dry-run fixtures and reports by running the integration tester against your workflow definitions. It outputs synthetic JSON fixtures, JSON data, and human-readable Markdown reports for validation.

Do I need API keys or external dependencies to run contract validation on skill handoffs?

No API keys or external dependencies are needed for contract validation on skill handoffs. The tool is implemented in Python using only the standard library for fully offline validation.

What is the best way to detect naming violations in multi-skill pipelines?

The best way to detect naming violations in multi-skill pipelines is offline validation. The tool checks that each step's skill is present and correctly named against your defined workflows.

Why does my skill workflow fail during handoffs even when skills exist?

Skill workflows fail during handoffs when inter-skill data contracts are incompatible between steps. Validating producer to consumer JSON schema compatibility catches these breaking changes before release.