Index of every page on this site: llms.txt
All skills
qoderai avatar

/harness-skill-creator

@c6240a8
by qoderaiqoderai/better-harness2.5k stars
208
Run it yourself

Use when bootstrapping or tightening the smallest harness-oriented skill from an existing repository, workflow, evaluation corpus, or harness-analysis chain. Trigger for meta skills, reusable harness workflows, Qoder/Codex plugin skill sets, skill blueprints, and harness-analysis-like skills that need evidence-backed references, validation gates, and qodercli forward-tests.

Use this Skill: https://skilld.dev/gh/qoderai/better-harness/harness-skill-creator

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈100 tokens for metadata: the name and description. ≈737 when used: this file. ≈902 more on demand in 1 file.

Description uses 5.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈400 characters, or 5.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Harness Skill Creator

Create the smallest skill that makes another agent repeat one harness job with evidence, validation, and clear ownership.

Workflow

  1. Resolve source, target, and host: canonical skills/<name>/, .agents/skills/ wrapper, or both.
  2. Inspect the source chain before designing: entry SKILL.md, first-hop references, scripts, validators, templates, specs, tests, plugin manifests, and any real smoke evidence.
  3. Load references/bootstrap-patterns.md after the first inventory. Use it to extract patterns, not product-specific rules.
  4. Draft the minimum viable skill map:
    • skill name and trigger sentence
    • one job the skill owns
    • files to create under skills/<skill-name>/, usually SKILL.md plus one reference
    • evidence boundary and validation commands
    • forward-test prompt and pass/fail gates
  5. Initialize new canonical skills with the system skill-creator helper when available. Add scripts/ only for stable repeated automation; keep ad-hoc evaluation prompts out of runtime scripts.
  6. Write the SKILL.md as a router. Put trigger conditions in frontmatter description, keep the body short, and route detailed rules to first-hop references.
  7. Validate locally, then forward-test. Treat qodercli output as model evidence; local validators and file inspection decide pass/fail.

Design Gates

  • Prefer one skill over a stage tree until the target process proves multiple reusable stages.
  • Copy ownership shape, not product names, branch policy, private commands, or source-specific team routing.
  • Keep .agents/skills/ as a wrapper or mirror when the workflow is shared by the plugin; canonical judgment belongs under root skills/.
  • Do not add install, network, server, migration, or dependency-changing commands unless the user requested them and source evidence supports them.
  • Prefer portable Node/Python validators or target-owned commands. Do not default generated validation gates to Unix-only grep/find checks.
  • In attachment-only or no-tools forward-tests, never emit tool-call markup, shell probes, or inspection plans; return the skill map with status: "insufficient-evidence" when needed.
  • Forward-test files is a string array of skills/<skill-name>/... paths, not objects.
  • If the generated skill cannot pass quick_validate.py <skill-dir>, do not describe it as usable.
  • After any forward-test, verify git status or file inventory for every repo the model was allowed to read or write.

Validation

Run the narrowest useful gates for the created skill:

python3 <skill-creator-root>/scripts/quick_validate.py <skill-dir>
qodercli --cwd <neutral-dir> --plugin-dir <harness-root> -p "<forward-test prompt>"
qodercli plugin validate <harness-root>

Reject missing frontmatter, stale placeholders, broken links, unsupported commands, source-only assumptions, pseudo tool calls, or broad reports.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    The skill is a meta-development tool designed to bootstrap and generate other AI agent skills by analyzing existing repositories. It executes local validation scripts and uses vendor-specific CLI tools (qodercli). While it functions as intended for a development workflow, it possesses an inherent attack surface for indirect prompt injection as it processes content from external repositories.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at c6240a8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 4 months ago

README badge

README badge for qoderai/better-harness/harness-skill-creator