BF research-harness
Cognitive discipline for AI-native scientific experimentation. Trigger when setting up controlled experiments with LLM agents, designing reproducible evaluation pipelines, or structuring research workspaces for long-running agent collaboration. Provides guardrails, not recipes — teaches agents how to reason about experiments, not which commands to run.
As a process F 42/100 · Will not run — References files that are not bundled: scripts/validate_<module>.py, scripts/validate_repo_state.py
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 0
✓ No critical or high findings
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/validate_<module>.py - warning
missing-refreference to a missing file: scripts/validate_repo_state.py - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 42/100
- 0Tools and files. 2 referenced file(s) missing: scripts/validate_<module>.py, scripts/validate_repo_state.py
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (research-harness) differs from the folder (ai-research-harness)
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 58 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 3160 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +3Description length 354: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 58 items
- +4Reference files are cited in the instructions (6 of 6)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.