鱼皮AI导航
鱼皮AI导航
  • 主页
  • 社区
  • AI工具
  • AI知识库
  • AI提示词
  • MCP
  • Skills
  • AI学习资源
  • AI资讯
  • GitHub开源
登录/注册

testing-handbook-generator

基于测试手册内容自动生成安全测试相关的技术能力,通过分析静态分析、模糊测试等领域的工具与方法,批量创建可复用的技能模块,并建立跨技能关联关系,实现知识体系的系统化构建与持续更新。

效率工具文档处理数据与分析
访问 GitHub
文档Skills.MD
name
testing-handbook-generator
description
Meta-skill that analyzes the Trail of Bits Testing Handbook (appsec.guide) and generates Claude Code skills for security testing tools and techniques. Use when creating new skills based on handbook content.

Testing Handbook Skill Generator

Generate and maintain Claude Code skills from the Trail of Bits Testing Handbook.

When to Use

Invoke this skill when:

  • Creating new security testing skills from handbook content
  • User mentions "testing handbook", "appsec.guide", or asks about generating skills
  • Bulk skill generation or refresh is needed

Do NOT use for:

  • General security testing questions (use the generated skills)
  • Non-handbook skill creation

Handbook Location

The skill needs the Testing Handbook repository. See discovery.md for full details.

Quick reference: Check ./testing-handbook, ../testing-handbook, ~/testing-handbook → ask user → clone as last resort.

Repository: https://github.com/trailofbits/testing-handbook

Workflow Overview

▼
text
复制代码
Phase 0: Setup Phase 1: Discovery ┌─────────────────┐ ┌─────────────────┐ │ Locate handbook │ → │ Analyze handbook│ │ - Find or clone │ │ - Scan sections │ │ - Confirm path │ │ - Classify types│ └─────────────────┘ └─────────────────┘ ↓ ↓ Phase 3: Generation Phase 2: Planning ┌─────────────────┐ ┌─────────────────┐ │ TWO-PASS GEN │ ← │ Generate plan │ │ Pass 1: Content │ │ - New skills │ │ Pass 2: X-refs │ │ - Updates │ │ - Write to gen/ │ │ - Present user │ └─────────────────┘ └─────────────────┘ ↓ Phase 4: Testing Phase 5: Finalize ┌─────────────────┐ ┌─────────────────┐ │ Validate skills │ → │ Post-generation │ │ - Run validator │ │ - Update README │ │ - Test activation│ │ - Update X-refs │ │ - Fix issues │ │ - Self-improve │ └─────────────────┘ └─────────────────┘

Scope Restrictions

ONLY modify these locations:

  • plugins/testing-handbook-skills/skills/[skill-name]/* - Generated skills (as siblings to testing-handbook-generator)
  • plugins/testing-handbook-skills/skills/testing-handbook-generator/* - Self-improvement
  • Repository root README.md - Add generated skills to table

NEVER modify or analyze:

  • Other plugins (plugins/property-based-testing/, plugins/static-analysis/, etc.)
  • Other skills outside this plugin

Do not scan or pull into context any skills outside of testing-handbook-skills/. Generate skills based solely on handbook content and resources referenced from it.

Quick Reference

Section → Skill Type Mapping

Handbook SectionSkill TypeTemplate
/static-analysis/[tool]/Tool Skilltool-skill.md
/fuzzing/[lang]/[fuzzer]/Fuzzer Skillfuzzer-skill.md
/fuzzing/techniques/Technique Skilltechnique-skill.md
/crypto/[tool]/Domain Skilldomain-skill.md
/web/[tool]/Tool Skilltool-skill.md

Skill Candidate Signals

SignalIndicates
_index.md with bookCollapseSection: trueMajor tool/topic
Numbered files (00-, 10-, 20-)Structured content
techniques/ subsectionMethodology content
99-resources.md or 91-resources.mdHas external links

Exclusion Signals

SignalAction
draft: true in frontmatterSkip section
Empty directorySkip section
Template/placeholder fileSkip section
GUI-only tool (e.g., web/burp/)Skip section (Claude cannot operate GUI tools)

Decision Tree

Starting skill generation?

▼
text
复制代码
├─ Need to analyze handbook and build plan? │ └─ Read: discovery.md │ (Handbook analysis methodology, plan format) │ ├─ Spawning skill generation agents? │ └─ Read: agent-prompt.md │ (Full prompt template, variable reference, validation checklist) │ ├─ Generating a specific skill type? │ └─ Read appropriate template: │ ├─ Tool (Semgrep, CodeQL) → templates/tool-skill.md │ ├─ Fuzzer (libFuzzer, AFL++) → templates/fuzzer-skill.md │ ├─ Technique (harness, coverage) → templates/technique-skill.md │ └─ Domain (crypto, web) → templates/domain-skill.md │ ├─ Validating generated skills? │ └─ Run: scripts/validate-skills.py │ Then read: testing.md for activation testing │ ├─ Finalizing after generation? │ └─ See: Post-Generation Tasks below │ (Update main README, update Skills Cross-Reference, self-improvement) │ └─ Quick generation from specific section? └─ Use Quick Reference above, apply template directly

Two-Pass Generation (Phase 3)

Generation uses a two-pass approach to solve forward reference problems (skills referencing other skills that don't exist yet).

Pass 1: Content Generation (Parallel)

Generate all skills in parallel without the Related Skills section:

▼
text
复制代码
Pass 1 - Generating 5 skills in parallel: ├─ Agent 1: libfuzzer (fuzzer) → skills/libfuzzer/SKILL.md ├─ Agent 2: aflpp (fuzzer) → skills/aflpp/SKILL.md ├─ Agent 3: semgrep (tool) → skills/semgrep/SKILL.md ├─ Agent 4: harness-writing (technique) → skills/harness-writing/SKILL.md └─ Agent 5: wycheproof (domain) → skills/wycheproof/SKILL.md Each agent uses: pass=1 (content only, Related Skills left empty)

Pass 1 agents:

  • Generate all sections EXCEPT Related Skills
  • Leave a placeholder: ## Related Skills\n\n<!-- PASS2: populate after all skills exist -->
  • Output report includes references: DEFERRED

Pass 2: Cross-Reference Population (Sequential)

After all Pass 1 agents complete, run Pass 2 to populate Related Skills:

▼
text
复制代码
Pass 2 - Populating cross-references: ├─ Read all generated skill names from skills/*/SKILL.md ├─ For each skill, determine related skills based on: │ ├─ related_sections from discovery (handbook structure) │ ├─ Skill type relationships (fuzzers → techniques) │ └─ Explicit mentions in content └─ Update each SKILL.md's Related Skills section

Pass 2 process:

  1. Collect all generated skill names: ls -d skills/*/SKILL.md
  2. For each skill, identify related skills using the mapping from discovery
  3. Edit each SKILL.md to replace the placeholder with actual links
  4. Validate cross-references exist (no broken links)

Agent Prompt Template

See agent-prompt.md for the full prompt template with:

  • Variable substitution reference (including pass variable)
  • Pre-write validation checklist
  • Hugo shortcode conversion rules
  • Line count splitting rules
  • Error handling guidance
  • Output report format

Collecting Results

After Pass 1: Aggregate output reports, verify all skills generated. After Pass 2: Run validator to check cross-references.

Handling Agent Failures

If an agent fails or produces invalid output:

Failure TypeDetectionRecovery Action
Agent crashedNo output reportRe-run single agent with same inputs
Validation failedOutput report shows errorsCheck gaps/warnings, manually patch or re-run
Wrong skill typeContent doesn't match templateRe-run with corrected type parameter
Missing contentOutput report lists gapsAccept if minor, or provide additional related_sections
Pass 2 broken refValidator shows missing skillCheck if skill was skipped, update reference

Important: Do NOT re-run the entire parallel batch for a single agent failure. Fix individual failures independently.

Single-Skill Regeneration

To regenerate a single skill without re-running the entire batch:

▼
text
复制代码
# Regenerate single skill (Pass 1 - content only) "Use testing-handbook-generator to regenerate the {skill-name} skill from section {section_path}" # Example: "Use testing-handbook-generator to regenerate the libfuzzer skill from section fuzzing/c-cpp/10-libfuzzer"

Regeneration workflow:

  1. Re-read the handbook section for fresh content
  2. Apply the appropriate template
  3. Write to skills/{skill-name}/SKILL.md (overwrites existing)
  4. Re-run Pass 2 for that skill only to update cross-references
  5. Run validator on the single skill: uv run scripts/validate-skills.py --skill {skill-name}

Output Location

Generated skills are written to:

▼
text
复制代码
skills/[skill-name]/SKILL.md

Each skill gets its own directory for potential supporting files (as siblings to testing-handbook-generator).

Quality Checklist

Before delivering generated skills:

  • All handbook sections analyzed (Phase 1)
  • Plan presented to user before generation (Phase 2)
  • Parallel agents launched - one per skill (Phase 3)
  • Templates applied correctly per skill type
  • Validator passes: uv run scripts/validate-skills.py
  • Activation testing passed - see testing.md
  • Main README.md updated with generated skills table
  • README.md Skills Cross-Reference graph updated
  • Self-improvement notes captured
  • User notified with summary

Post-Generation Tasks

1. Update Main README

After generating skills, update the repository's main README.md to list them.

Format: Add generated skills to the same "Available Plugins" table, directly after testing-handbook-skills. Use plain text testing-handbook-generator as the author (no link).

Example:

▼
markdown
复制代码
| Plugin | Description | Author | |--------|-------------|--------| | ... other plugins ... | | [testing-handbook-skills](plugins/testing-handbook-skills/) | Meta-skill that generates skills from the Testing Handbook | Paweł Płatek | | [libfuzzer](plugins/testing-handbook-skills/skills/libfuzzer/) | Coverage-guided fuzzing with libFuzzer for C/C++ | testing-handbook-generator | | [aflpp](plugins/testing-handbook-skills/skills/aflpp/) | Multi-core fuzzing with AFL++ | testing-handbook-generator | | [semgrep](plugins/testing-handbook-skills/skills/semgrep/) | Fast static analysis for finding bugs | testing-handbook-generator |

2. Update Skills Cross-Reference

After generating skills, update the README.md's Skills Cross-Reference section with the mermaid graph showing skill relationships.

Process:

  1. Read each generated skill's SKILL.md and extract its ## Related Skills section
  2. Build the mermaid graph with nodes grouped by skill type (Fuzzers, Techniques, Tools, Domain)
  3. Add edges based on the Related Skills relationships:
    • Solid arrows (-->) for primary technique dependencies
    • Dashed arrows (-.->) for alternative tool suggestions
  4. Replace the existing mermaid code block in README.md

Edge classification:

RelationshipArrow StyleExample
Fuzzer → Technique-->libfuzzer --> harness-writing
Tool → Tool (alternative)-.->semgrep -.-> codeql
Fuzzer → Fuzzer (alternative)-.->libfuzzer -.-> aflpp
Technique → Technique-->harness-writing --> coverage-analysis

Validation: After updating, run validate-skills.py to verify all referenced skills exist.

3. Self-Improvement

After each generation run, reflect on what could improve future runs.

Capture improvements to:

  • Templates (missing sections, better structure)
  • Discovery logic (missed patterns, false positives)
  • Content extraction (shortcodes not handled, formatting issues)

Update process:

  1. Note issues encountered during generation
  2. Identify patterns that caused problems
  3. Update relevant files:
    • SKILL.md - Workflow, decision tree, quick reference updates
    • templates/*.md - Template improvements
    • discovery.md - Detection logic updates
    • testing.md - New validation checks
  4. Document the improvement in commit message

Example self-improvement:

▼
text
复制代码
Issue: libFuzzer skill missing sanitizer flags table Fix: Updated templates/fuzzer-skill.md to include ## Compiler Flags section

Example Usage

Full Discovery and Generation

▼
text
复制代码
User: "Generate skills from the testing handbook" 1. Locate handbook (check common locations, ask user, or clone) 2. Read discovery.md for methodology 3. Scan handbook at {handbook_path}/content/docs/ 4. Build candidate list with types 5. Present plan to user 6. On approval, generate each skill using appropriate template 7. Validate generated skills 8. Update main README.md with generated skills table 9. Update README.md Skills Cross-Reference graph from Related Skills sections 10. Self-improve: note any template/discovery issues for future runs 11. Report results

Single Section Generation

▼
text
复制代码
User: "Create a skill for the libFuzzer section" 1. Read /testing-handbook/content/docs/fuzzing/c-cpp/10-libfuzzer/ 2. Identify type: Fuzzer Skill 3. Read templates/fuzzer-skill.md 4. Extract content, apply template 5. Write to skills/libfuzzer/SKILL.md 6. Validate and report

Tips

Do:

  • Always present plan before generating
  • Use appropriate template for skill type
  • Preserve code blocks exactly
  • Validate after generation

Don't:

  • Generate without user approval
  • Skip fetching non-video external resources (use WebFetch)
  • Fetch video URLs (YouTube, Vimeo - titles only)
  • Include handbook images directly
  • Skip validation step
  • Exceed 500 lines per SKILL.md

For first-time use: Start with discovery.md to understand the handbook analysis process.

For template reference: See templates/ directory for skill type templates.

For validation: See testing.md for quality assurance methodology.

效率工具
文档处理
数据与分析

快捷安装

复制到终端去安装 Skill

npxskillsaddtrailofbits/skills--skill"testing-handbook-generator"
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
🔥热门工具
朱雀AI检测朱雀AI检测
朱雀AI检测助手朱雀AI检测助手
LovartLovart
老鱼简历老鱼简历
WritePass官网WritePass官网
面多多面多多
CursorCursor
星月写作星月写作
朱雀AI检测助手朱雀AI检测助手
零感AI零感AI
Skills 推荐
webapp-testing
提供本地 Web 应用的端到端测试能力,支持页面导航、元素交互、表单填写、动态等待、断言验证、截图捕获、浏览器日志收集及网络请求拦截,适用于前端功能验证与 UI 行为调试。
definition-of-done-generator
自动生成项目完成标准的规范定义与配置文件,提供符合企业级工作流要求的最佳实践指导,输出可直接投入生产环境的代码和验证结果,适用于需要标准化流程审批、合规审查及跨系统集成的复杂项目管理场景。
implement
实现 Linus Dashboard 的功能开发与集成,基于 TypeScript 和 Python 构建前后端组件,遵循严格的代码规范与架构模式,完成视图、卡片、服务及传感器等模块的创建与验证,确保高质量交付并兼容 Home Assistant 生态。
cloud-scheduler-job-creator
自动处理 Google Cloud Platform 中的云调度任务创建,提供符合最佳实践的配置方案与生产级代码生成,支持计算、存储、大数据及机器学习服务的集成部署。
planning-with-files
通过创建任务计划、笔记与交付文件三个持久化文档,实现对复杂任务的结构化管理。在多阶段工作中保持目标清晰,动态更新进度并沉淀研究过程,适用于需长期跟踪的规划、研究及创作场景。