技能综合测试员
- 作者仓库星标 1,568
- 作者仓库 claude-trading-skills
- 领域
- 数据
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tradermonty · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- Python >=3.9
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步:运行集成验证
针对项目的 CLAUDE.md 执行验证脚本:这会解析多技能工作流程部分中的所有`Workflow Name:`块,将每个步骤的显示名称解析为技能目录,并验证存在性、契约和命名。
第 2 步:验证特定工作流程
通过名称子字符串定位单个工作流程:
第 3 步:使用合成夹具进行试运行
为每个技能的预期输出创建合成夹具 JSON 文件,并在没有实际数据的情况下验证合约兼容性:夹具文件被写入带有 `_fixture` 标志集的 `reports/fixtures/`。
第 4 步:审核结果
打开生成的 Markdown 报告以获得人类可读的摘要,或解析 JSON 报告以进行编程使用。每个工作流程显示: 分步技能存在检查 移交合同验证(通过/失败/不适用) 文件命名约定违规
第 5 步:修复损坏的交接
对于每个`FAIL` 切换,验证: 生产者技能的输出包含所有必需字段 消费者技能的输入参数接受生产者的输出格式 文件命名模式在生产者输出和消费者输入之间保持一致
# 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:
```bash
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:
```bash
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:
```bash
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
```json
{
"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
章节与文件索引
按说明文件中的顺序排列。
概述
何时使用
先决条件
第 1 步:运行集成验证
第 2 步:验证特定工作流程
文件/命令 -> **Workflow Name:** · reports/fixtures/ · _fixture · FAIL · reports/ · integration_test_YYYY-MM-DD_HHMMSS.{json,md} · scripts/validate_workflows.py · references/workflow_contracts.md
内容校验值 -> b055ca45b738
当前原文的自动摘译,尚未人工审校。
概述
通过按顺序执行每个步骤来验证 CLAUDE.md 中定义的多技能工作流程(每日市场监控、每周策略回顾、收益动量交易等)。检查步骤 N 的输出和步骤 N+1 的输入之间的 JSON 模式兼容性的技能间数据契约,验证文件命名约定,并报告中断的切换。支持使用合成夹具的试运行模式。
何时使用
在 CLAUDE.md 中添加或修改多技能工作流程后 更改技能的输出格式(JSON 架构、文件命名)之后 在发布新技能以验证管道兼容性之前 调试连续工作流程步骤之间的中断切换时 作为 CI 预检查拉取请求是否涉及技能脚本
先决条件
Python 3.9+ 不需要 API 密钥 不需要第三方 Python 包(仅使用标准库)