BD harness-engineering
Design, build, diagnose, and evolve agent harnesses: instructions, tools, execution environments, durable state, context management, verification, recovery, bounded autonomous loops, and software factories that repeatedly turn incoming work into accepted deliverables. Use for director/worker production systems, factory steering, unreliable coding agents, cross-session drift, premature completion, harness audits, or changes to the runtime around a model, including bounded typed-decision routing. Do not use for prompt rewriting alone, model training, general application architecture, or operating an already evaluated agent in production; route those concerns to their specialist skills.
Design, build, diagnose, and evolve agent harnesses: instructions, tools, execution environments, durable state, context management, verification, recovery…
As a process D 47/100 · Unfinished process — References files that are not bundled: ../multi-agent-coordination/SKILL.md, templates/harness-contract.md, ../systematic-debugging/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 60. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../multi-agent-coordination/SKILL.md - warning
missing-refreference to a missing file: templates/harness-contract.md - warning
missing-refreference to a missing file: ../systematic-debugging/SKILL.md - warning
missing-refreference to a missing file: templates/lesson-candidate.md - warning
missing-refreference to a missing file: templates/session-protocol.md - warning
missing-refreference to a missing file: templates/guardrail-promotion.md - warning
missing-refreference to a missing file: templates/state.json - warning
missing-refreference to a missing file: templates/recovery-drill.md - warning
missing-refreference to a missing file: templates/runtime-design.md - warning
missing-refreference to a missing file: templates/tool-contract.json - warning
missing-refreference to a missing file: templates/observability-plan.md - warning
missing-refreference to a missing file: templates/run-record.json - warning
missing-refreference to a missing file: templates/loop-contract.md - warning
missing-refreference to a missing file: templates/graph.json - warning
missing-refreference to a missing file: templates/factory-charter.md - warning
missing-refreference to a missing file: templates/factory-role.md - warning
missing-refreference to a missing file: templates/factory-change.md - warning
missing-refreference to a missing file: templates/factory-snapshot.json - warning
missing-refreference to a missing file: templates/factory-batch-record.md - warning
missing-refreference to a missing file: templates/handoff.md - warning
missing-refreference to a missing file: ../langgraph/SKILL.md - warning
missing-refreference to a missing file: ../pydanticai/SKILL.md - warning
missing-refreference to a missing file: ../autogen/SKILL.md - warning
missing-refreference to a missing file: ../agent-evals-and-observability/SKILL.md - warning
missing-refreference to a missing file: ../agent-production-operations/SKILL.md - warning
missing-refreference to a missing file: ../agent-skills/SKILL.md - warning
missing-refreference to a missing file: ../secure-software-engineering/SKILL.md - warning
missing-refreference to a missing file: ../ai-governance/SKILL.md - warning
missing-refreference to a missing file: ../spec-driven-development/references/executable-business-policy.md - warning
missing-refreference to a missing file: ../spec-driven-development/templates/BUSINESS-POLICY.md
Process rating: all ten parameters 47/100
- 0Tools and files. 30 referenced file(s) missing: ../multi-agent-coordination/SKILL.md, templates/harness-contract.md, ../systematic-debugging/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 3 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 4801 tokens
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 12 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- -36 of 10 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 692: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (37 of 38)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.