Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
tradermonty avatar

Skill Integration Tester

  • 778 installs
  • 2.6k repo stars
  • Updated August 4, 2026
  • tradermonty/claude-trading-skills

skill-integration-tester is an agent skill that validates multi-skill CLAUDE.md workflows for correct handoffs, JSON schema contracts, and file naming for developers who maintain chained agent skill pipelines.

About

skill-integration-tester is a tradermonty/claude-trading-skills agent skill that automatically validates multi-skill workflows declared in CLAUDE.md before changes merge. It executes each pipeline step in sequence—covering workflows like Daily Market Monitoring, Weekly Strategy Review, and Earnings Momentum Trading—and verifies that step N outputs match step N+1 inputs via JSON schema compatibility checks. The skill also audits skill existence, inter-skill data contracts, file naming conventions, and handoff integrity across the full chain. Developers reach for skill-integration-tester when adding new workflows, modifying skill outputs, or confirming pipeline health ahead of release. It requires no API key and targets repositories where multiple Claude skills pass structured JSON between stages. Use it to catch broken references, schema mismatches, and naming drift that unit tests on individual skills would miss.

  • Validates multi-skill workflows defined in CLAUDE.md by executing each step in sequence
  • Checks inter-skill data contracts for JSON schema compatibility between consecutive steps
  • Verifies file naming conventions and reports broken handoffs
  • Supports dry-run mode with synthetic fixtures
  • Runs as a CI pre-check for pull requests touching skill scripts

Skill Integration Tester by the numbers

  • 778 all-time installs (skills.sh)
  • +90 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #1,345 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/tradermonty/claude-trading-skills --skill skill-integration-tester

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs778
repo stars2.6k
Last updatedAugust 4, 2026
Repositorytradermonty/claude-trading-skills

How do you test multi-skill CLAUDE.md workflows?

Automatically validate that multi-skill workflows defined in CLAUDE.md have correct handoffs, matching JSON schemas, and valid file conventions before merging changes.

Who is it for?

Developers maintaining multi-step Claude skill repositories who need automated contract checks across CLAUDE.md workflow definitions.

Skip if: Single-skill projects or codebases without CLAUDE.md-defined multi-skill handoff pipelines.

When should I use this skill?

User adds or modifies CLAUDE.md workflows, changes skill JSON outputs, or asks to verify pipeline health before release.

What you get

Validated skill pipeline report covering schema compatibility, handoff integrity, and file convention compliance.

  • Pipeline validation report
  • Schema compatibility audit

Files

SKILL.mdMarkdownGitHub ↗

Skill Integration Tester

Overview

Validate multi-skill workflows defined in CLAUDE.md (Daily Market Monitoring, Weekly Strategy Review, Earnings Momentum Trading, etc.) by executing each step in sequence. Check inter-skill data contracts for JSON schema compatibility between output of step N and input of step N+1, verify file naming conventions, and report broken handoffs. Supports dry-run mode with synthetic fixtures.

When to Use

  • After adding or modifying a multi-skill workflow in CLAUDE.md
  • After changing a skill's output format (JSON schema, file naming)
  • Before releasing new skills to verify pipeline compatibility
  • When debugging broken handoffs between consecutive workflow steps
  • As a CI pre-check for pull requests touching skill scripts

Prerequisites

  • Python 3.9+
  • No API keys required
  • No third-party Python packages required (uses only standard library)

Workflow

Step 1: Run Integration Validation

Execute the validation script against the project's CLAUDE.md:

python3 skills/skill-integration-tester/scripts/validate_workflows.py \
  --output-dir reports/

This parses all **Workflow Name:** blocks from the Multi-Skill Workflows section, resolves each step's display name to a skill directory, and validates existence, contracts, and naming.

Step 2: Validate a Specific Workflow

Target a single workflow by name substring:

python3 skills/skill-integration-tester/scripts/validate_workflows.py \
  --workflow "Earnings Momentum" \
  --output-dir reports/

Step 3: Dry-Run with Synthetic Fixtures

Create synthetic fixture JSON files for each skill's expected output and validate contract compatibility without real data:

python3 skills/skill-integration-tester/scripts/validate_workflows.py \
  --dry-run \
  --output-dir reports/

Fixture files are written to reports/fixtures/ with _fixture flag set.

Step 4: Review Results

Open the generated Markdown report for a human-readable summary, or parse the JSON report for programmatic consumption. Each workflow shows:

  • Step-by-step skill existence checks
  • Handoff contract validation (PASS / FAIL / N/A)
  • File naming convention violations
  • Overall workflow status (valid / broken / warning)

Step 5: Fix Broken Handoffs

For each FAIL handoff, verify that: 1. The producer skill's output contains all required fields 2. The consumer skill's input parameter accepts the producer's output format 3. File naming patterns are consistent between producer output and consumer input

Output Format

JSON Report

{
  "schema_version": "1.0",
  "generated_at": "2026-03-01T12:00:00+00:00",
  "dry_run": false,
  "summary": {
    "total_workflows": 8,
    "valid": 6,
    "broken": 1,
    "warnings": 1
  },
  "workflows": [
    {
      "workflow": "Daily Market Monitoring",
      "step_count": 4,
      "status": "valid",
      "steps": [...],
      "handoffs": [...],
      "naming_violations": []
    }
  ]
}

Markdown Report

Structured report with per-workflow sections showing step validation, handoff status, and naming violations.

Reports are saved to reports/ with filenames integration_test_YYYY-MM-DD_HHMMSS.{json,md}.

Resources

  • scripts/validate_workflows.py -- Main validation script
  • references/workflow_contracts.md -- Contract definitions and handoff patterns

Key Principles

1. No API keys required -- all validation is local and offline 2. Non-destructive -- reads SKILL.md and CLAUDE.md only, never modifies skills 3. Deterministic -- same inputs always produce same validation results

Related skills

How it compares

Pick skill-integration-tester over generic test skills when validating inter-skill JSON contracts in CLAUDE.md pipelines specifically.

FAQ

What does skill-integration-tester validate?

skill-integration-tester validates CLAUDE.md multi-skill workflows by checking skill existence, JSON schema compatibility between sequential steps, file naming conventions, and handoff integrity across the full pipeline.

Does skill-integration-tester need an API key?

skill-integration-tester sets requires_api_key to false and runs locally against CLAUDE.md workflow definitions, executing each step in sequence to verify contracts without external service calls.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.