skill integration tester

Data Community

Skill notes

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)

Step 1: Run Integration Validation

Execute the validation script against the project's CLAUDE.md: 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:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tradermonty · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python >=3.9
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview skill-integration-tester.preview
# Step 4: Review Results

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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.