agentsclimarketplace

Implement

Skill boshu2/agentops/skills/implement

Execute one bounded RED to GREEN experiment from bead or caller intent; return derived subject identity and check facts. Triggers: "implement", "implement this bead", "run the experiment". Full plan-to-validation requests route to rpi.From its SKILL.md

Install
npx -y skills add boshu2/agentops --skill implement

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

4.0 KB, as published. Nobody here has run it

Implement

Execute exactly one bounded experiment described by the resolved bead or caller intent. Implement owns subject edits and factual evidence. It does not create a second planning record or a model-authored candidate packet.

Workflow

  1. Read the intent, acceptance, and scope from their existing source. A runtime may snapshot and hash that source automatically for drift detection.
  2. Run the declared first acceptance check before changing behavior. RED-first applies only when acceptance is behavioral: preserve evidence that the check fails for the expected missing behavior. Relocations, doc merges, and pure refactors need no failing-check ritual — record an honest green pre-change baseline instead.
  3. Make the smallest in-scope change that satisfies the active behavior.
  4. Run the targeted acceptance checks and capture factual results.
  5. Refactor only while those checks stay green. Refactoring does not change the acceptance test.
  6. Have the runtime derive actual changed paths and subject-manifest.v1 from the before/after subject. Do not make the model transcribe those facts.
  7. Return the manifest digest, author context ID, and exact check receipts in the response or runtime channel. Stop.

Specialists such as standards, domain, test, refactor, and security may provide advice. They are never hard dependencies and cannot add lifecycle authority.

Evidence proportionality

During edits, run the smallest deterministic checks that can falsify the active change. Reuse exact-input receipts when their subject and tool identity still match. Run an expensive full-suite check at the integration boundary, or earlier only when the intent explicitly makes it the first acceptance check. Repeatedly replaying the full suite after every focused edit adds latency, not proof.

Scope conflict rule

On discovering a live consumer of the change outside the declared write scope — a test asserting the old path, a generated twin, a gate reading the moved file — stop and report the exact file and line to the caller. Do not silently expand scope to absorb it or revise the intent from Implement. The caller may revise the source intent and start a separate invocation.

Before declaring GREEN, self-audit the diff for mocks, placeholders, TODO stubs, hardcoded fixture values, weakened assertions, regenerated goldens, widened tolerances, suppression directives, or specification edits standing in for real behavior. When the diff changes a test, gate, fixture, golden, or acceptance source, state why the original intent requires that change and confirm that green came from the implemented behavior rather than a weakened oracle. A check that passes against a substitute or weakened oracle is not evidence for the acceptance criterion; either finish the behavior or report it as not built.

Boundary

  • Do not commit, push, claim, close, release, land, reserve, retry, or invoke a semantic validator.
  • Do not silently expand acceptance. A different acceptance contract is a new intent for a caller to start separately.
  • A failed check is evidence for the caller, not permission to create a packet or validation loop.

What ships with it: 2 files

1.2 KB alongside SKILL.md, 1 of them executable

references/

scripts/

Gives 0 of the 12 instructions most quality gates skills give

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

  • Read full output and check exit codein 45 of 1524, across 40 files
  • Verify output confirms the claimin 44 of 1524, across 39 files
  • Identify the command that proves the claimin 43 of 1524, across 39 files
  • Execute the full verification commandin 36 of 1524, across 30 files
  • Produce a verification reportin 34 of 1524, across 18 files
  • Review git diff changesin 30 of 1524, across 16 files
  • Fix build failures immediatelyin 29 of 1524, across 9 files
  • Group findings by severityin 28 of 1524
  • State claim only with evidencein 27 of 1524, across 22 files
  • Verify regression tests with red-green cyclein 26 of 1524, across 22 files
  • Run the full test suitein 26 of 1524, across 25 files
  • Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

  • Read intent acceptance and scope
  • Run acceptance check before changing behavior
  • Make smallest in-scope change
  • Run targeted acceptance checks
  • Refactor only while checks stay green
  • Self-audit diff for mocks or stubs

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 613,297. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.