BB ecl-harness-engineer
Create or audit ECL Agent Harness infrastructure: AGENTS.md, change tracking, repository guidance, lint checks, CI gates, and agent handoff docs.
Create or audit ECL Agent Harness infrastructure: AGENTS.md, change tracking, repository guidance, lint checks, CI gates, and agent handoff docs.
As a process B 67/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 9
✓ No critical or high findings
Medium and low: 9
-
low Dangerous commands
cmd-execpolicy-bypassreferences/ecl-harness.md:1418Runs PowerShell with execution policy bypassed (documentation of a security skill)powershell -NoProfile -ExecutionPolicy Bypass -File scripts/harn…ps1 reindex
security skill -
low Dangerous commands
cmd-execpolicy-bypassreferences/ecl-harness.md:1419Runs PowerShell with execution policy bypassed (documentation of a security skill)powershell -NoProfile -ExecutionPolicy Bypass -File scripts/harn…ps1 check
security skill -
low Exfiltration
read-dotenvreferences/environment-config-guide.md:246Reads a .env file (documentation of a security skill)cat .env.example
security skill -
low Exfiltration
read-dotenvreferences/environment-config-guide.md:248Reads a .env file (documentation of a security skill)cat .env.sample
security skill
A further 5 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 29. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 145 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_repo" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "license_source"
Process rating: all ten parameters 67/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 483 tokens
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
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 145: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 7 items
- +4Reference files are cited in the instructions (1 of 15)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.