Protocol Templates Skill

Purpose

Provide structured, protocol-type-specific audit templates that enumerate the exact checks, invariants, and attack vectors relevant to each protocol category. These templates are loaded based on context detection.

Available Templates

Template Structure

Each template follows a consistent format:

1. Protocol Overview: What the protocol does
2. Architecture Checklist: Structural checks
3. Invariants: Mathematical properties that must hold
4. Attack Vectors: Known exploits for this protocol type
5. Critical Functions: Functions requiring deepest review
6. Integration Risks: External dependency risks
7. Economic Considerations: Game theory and incentive analysis

Usage

1. Context detection identifies protocol type
2. Appropriate template is loaded
3. Auditor follows template checklist systematically
4. Findings tagged with template category for standardized reporting

Prerequisites

Protocol templates require Context Detection for automatic loading. Manual template selection is also supported.

Validation

To verify template coverage, validate against known protocol types:

# Validate template completeness
required_sections = ["Overview", "Architecture Checklist", "Invariants", "Attack Vectors", "Critical Functions"]
for template in templates:
    for section in required_sections:
        assert section in template.sections, f"{template.name} missing {section}"

# Example template loading configuration
detected_type: amm-dex
confidence: 0.92
loaded_templates:
  - amm-dex-template.md
  - defi-patterns.md
checklist: dex-amm-checklist

# Test template file integrity
for f in *-template.md; do echo "Validating $f"; head -5 "$f"; done

Behavior Guidelines

• Template loading is required when context detection confidence exceeds 0.8
• Auditors MUST verify that all invariants in the template are tested
• Custom template sections may optionally be added for novel protocol designs

References

• Protocol Templates References - Template customization guides and architecture patterns