agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/skill-scientist/SKILL.md

skill-scientist

Skill1 starsChanged 3 months agoMITView on GitHub

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start with generate-hypothesis unless a hypothesis file already exists from a prior run.

    line 16
  2. Very specific:

    Follow each workflow next mapping in skill.yaml after reviewing generated outputs.

    line 17
  3. Very specific:

    If a fixture does not exist, create it manually or use the evaluation-harness skill before re-running run-experiment.

    line 18
  4. Very specific:

    Do NOT run promote-skill-update without reviewing the review report scores.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill Scientist

Overview

AI Scientist pattern adapted for bug bounty skill improvement. End-to-end automated pipeline: Hypothesize -> Design -> Run in lab -> Review -> Promote. Generates and validates improvements to existing fat skills by identifying coverage gaps, designing controlled experiments with positive/negative controls, executing against evaluation fixtures, scoring results, and producing promotion proposals. Never modifies production skills without explicit approval.

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

Quick Reference

  • Skill: skill-scientist
  • Severity range: info
  • Required tools: python3, jq, bash
  • Expected input files: .claude/skills/skill-scientist/payloads/coverage_matrix.yaml
  • Scope check: confirm authorization before running experiments or fixture creation.

Workflow Selection

  • Start with generate-hypothesis unless a hypothesis file already exists from a prior run.
  • Follow each workflow next mapping in skill.yaml after reviewing generated outputs.
  • If a fixture does not exist, create it manually or use the evaluation-harness skill before re-running run-experiment.
  • Do NOT run promote-skill-update without reviewing the review report scores.

Available Workflows

WorkflowPurposeScript pathsPrimary outputsEvidence
generate-hypothesisRead coverage matrix, find high-priority gaps, output hypotheses..claude/skills/skill-scientist/scripts/generate_hypothesis.py$OUTDIR/hypotheses.json$OUTDIR/evidence/
design-experimentDesign controlled experiments with positive/negative controls per hypothesis..claude/skills/skill-scientist/scripts/design_experiment.py$OUTDIR/design_manifest.json$OUTDIR/evidence/
run-experimentExecute experiments against evaluation fixtures, capture pass/fail results..claude/skills/skill-scientist/scripts/run_experiment.py$OUTDIR/results_manifest.json$OUTDIR/evidence/
review-experimentScore experiment results against success criteria, compute pass/fail threshold..claude/skills/skill-scientist/scripts/review_experiment.py$OUTDIR/review_report.json$OUTDIR/evidence/
promote-skill-updateGenerate promotion proposals for passed experiments, describe required diffs..claude/skills/skill-scientist/scripts/promote_skill_update.py$OUTDIR/promotion_report.json$OUTDIR/evidence/

Evidence Required

  • Save all generated JSON artifacts in the output directory.
  • Include timestamps, workflow name, and tool versions in every output manifest.
  • Store experiment logs (stdout/stderr captures) in the evidence directory.
  • Evidence templates from skill.yaml:
    • hypothesis_generated: hypotheses.json with gap IDs and priority levels
    • experiment_result: results_manifest.json with positive/negative control outcomes
    • review_passed: review_report.json with normalized score >= 7.0
    • promotion_ready: promotion_report.json with target skill and diff description

References

  • Source of truth: skill.yaml
  • Runbooks: runbooks/
  • Evaluation harness: .claude/skills/evaluation-harness/
  • Inspired by: SakanaAI AI Scientist pattern (arXiv:2408.06292)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.