This skill should be used when an audit-fleet lane is producing or validating report format and must enforce deterministic sections plus exact finding keys.
From audit-fleetnpx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin audit-fleetThis skill uses the workspace's default tool permissions.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Use one canonical structure so lane outputs can be merged without manual rework.
All audit-fleet outputs must preserve this exact section order:
All Findings entries must include these keys exactly:
Severity enum is strict: critical | warning | info.
Use a markdown table with this exact column order:
| finding_id | severity | dimension | evidence | impact | recommendation | effort | owner | dependencies | confidence | acceptance_criteria |
|---|