skill-integration-tester

Validate multi-skill workflows defined in CLAUDE.md by checking skill existence, inter-skill data contracts (JSON schema compatibility), file naming conventions, and handoff integrity. Use when adding new workflows, modifying skill outputs, or verifying pipeline health before release.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with concrete commands, a clear multi-step workflow, and correctly signaled references to real bundle files. Its only weakness is mild redundancy between the Overview, Prerequisites, and Key Principles sections plus a hardcoded example date.

Suggestions

Remove the redundant 'No API keys required' from Key Principles (already stated in Prerequisites) or fold Key Principles into Prerequisites to avoid repetition.

Tighten the Overview so it does not restate the frontmatter description verbatim; keep it as a brief orienting summary.

Replace the hardcoded '2026-03-01T12:00:00+00:00' in the JSON example with a placeholder like '<ISO timestamp>' to avoid implying stale time-sensitive data.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and a concrete JSON schema, but the Overview restates the description, the Key Principles section repeats 'No API keys required' already in Prerequisites, and the JSON example hardcodes a date ('2026-03-01T12:00:00+00:00'), so it could be tightened.	2 / 3
Actionability	It provides copy-paste-ready bash commands with real flags (--workflow, --dry-run, --output-dir) and a concrete JSON output schema, fully meeting the executable-guidance anchor.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced with the validation script as an explicit checkpoint, a review step, and a dedicated 'Fix Broken Handoffs' recovery step; the skill is explicitly non-destructive, so the destructive-cap does not apply.	3 / 3
Progressive Disclosure	The body is an overview that signals one-level-deep references to real, verified bundle files (scripts/validate_workflows.py and references/workflow_contracts.md) in its Resources section, with content appropriately split rather than nested.	3 / 3
	Total	11 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that names concrete capabilities and gives explicit 'Use when' triggers, giving it a clear and distinguishable niche. It is held back only slightly by trigger terms that are a touch more project-internal than naturally user-spoken.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions: 'checking skill existence, inter-skill data contracts (JSON schema compatibility), file naming conventions, and handoff integrity', matching the anchor for listing several specific concrete actions rather than a single domain mention.	3 / 3
Completeness	It explicitly states what the skill does (validate multi-skill workflows by checking existence, contracts, naming, handoffs) and provides an explicit 'Use when...' trigger clause, satisfying both the 'what' and 'when' requirements.	3 / 3
Trigger Term Quality	The 'Use when adding new workflows, modifying skill outputs, or verifying pipeline health before release' clause provides relevant triggers but leans toward project-internal jargon and misses common user-facing variations, so it sits at 'some relevant keywords but missing common variations' rather than full natural-term coverage.	2 / 3
Distinctiveness Conflict Risk	The niche is clearly defined as multi-skill workflow integration testing tied to CLAUDE.md, with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: tradermonty/claude-trading-skills
Path: skills/skill-integration-tester/SKILL.md
Commit: 62a1635

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.