⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
agent-native
Dispatch independent tasks to parallel workers or selected persistent roles. Use when: delegation is authorized with disjoint scopes; execution does not validate output.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
AgentOps
DevOps discipline for AI coding agents: shape the work, track it as a graph, and get each change judged by a fresh agent session that didn't write it.
Install · The loop · Goals · Try it · Skills
AgentOps provides optional skills and a CLI (ao). The same SKILL.md skills work
with coding agents (Claude Code, Codex, Cursor, OpenCode, Gemini CLI, Pi and
others) and personal assistants (OpenClaw, Grok Bot). You state intent as
behavior in your domain's words. The skills carry it through one change
(Plan → Implement → checks, with Validate where a mistake is costly: an RPI)
or, for bigger work, a goal made of
many RPIs tracked in
Beads, a dependency-aware issue tracker.
Why use AgentOps?
| When the agent… | AgentOps adds |
|---|---|
| Builds something different from what you meant | Given/When/Then examples shared by implementation and review |
| Uses three names for one concept | One domain term per concept, in intent, code and tests |
| Says “done” after a green test run on a change that matters | A fresh judge that didn't write the change |
| Loses the thread on work bigger than one session | A Beads graph holding intent, dependencies and verdicts |
| Runs off with a half-formed goal | An interview that settles the goal before agents go autonomous |
| Gives one model's answer to a hard call | A council: judges in fresh contexts, each with the model, effort and perspective you assign (one model family or several vendors), compare, duel (score each other's ideas) or debate to your majority, keep dissent, and can answer an interview for you; Idea Genie brainstorms options |
| Loses its plans, research and decisions when the session ends | Plans and decisions saved on the bead or issue (Plan, Interview, Navigate); research and idea reports under .agents/; council reports where you choose |
| Repeats the last session's investigation | Memory turns reviewed, disclosure-checked lessons into .context/ pages safe to commit |
Quickstart
Pick one method per agent: a plugin plus npx on the same agent gives you every skill twice.
claude plugin marketplace add boshu2/agentops
claude plugin install agentops@agentops-marketplace
claude plugin details agentops@agentops-marketplace
Check that agentops appears in the plugin inventory. The bundle includes
skills, four agents and tool-call guards.
codex plugin marketplace add boshu2/agentops
codex plugin add agentops@agentops-marketplace
codex plugin list --json
Check that agentops appears in the inventory. Skills use the agentops: prefix;
custom roles and read limits have separate setup.
With Node.js installed, run from your project directory, then pick your agents and skills:
npx skills@latest add boshu2/agentops
Add -g for a user-level install. In scripts, name the agents:
npx skills@latest add boshu2/agentops -g -a cursor opencode -y
(-y without -a can install into every agent the installer knows).
Installer targets include cursor, opencode, gemini-cli, antigravity,
pi, grok (Grok Build) and openclaw. Grok Bot has no installer target; add
the same SKILL.md folders through its skill settings.
Some skills need extra tools (install guide); what
each host has been tested for is in host coverage and limits.
Start a new session so the skills load. Most skills need only your coding
agent; Validate also needs the ao CLI. Invocation names
vary by agent: this README shows Claude Code's /agentops:<skill>; Codex uses
$agentops:<skill>.
The operational loop
Each change is shaped, built and judged. You (or Plan) write intent as behavior (BDD), using one word per concept (DDD's ubiquitous language). For a system that calls queued work a Job, in Gherkin:
Feature: Job redelivery is idempotent
A Job is one unit of queued work. Delivering it again never repeats its side effect.
Scenario: A completed Job is delivered again
Given Job "J-42" completed and charged the customer $20
When the worker receives Job "J-42" again
Then it returns the completed result of "J-42"
And the customer has been charged $20 exactly once
Scenario: A Job that failed before charging is delivered again
Given Job "J-43" failed before charging the customer $20
When the worker receives Job "J-43" again
Then Job "J-43" completes
And the customer has been charged $20 exactly once
The feature defines the domain term once; each scenario has concrete data, one
action and an observable result. Keep scenarios in the issue or conversation;
no .feature file is required.
| Step | Skill | What it does with the scenarios |
|---|---|---|
| Shape | plan | Turns the request into scenarios for one small change. Skip it when intent is clear. |
| Build | implement | Makes the change and tests both scenarios. |
| Judge | validate | A new session that didn't write it returns PASS, FAIL or NOT_PROVEN against the same scenarios. |
| Learn | memory | Optional: reviewed .context/ pages that later work can query. |
Enter at the step you need; an existing change goes straight to Validate. The author never approves its own work. Merging and releasing follow your repo's rules.
Goals
rpi runs Plan → Implement → checks, with Validate where a
mistake is costly, for one outcome
without check-ins (your agent's permission prompts still apply) and stops at
acceptance, a blocker or a spent limit. Bigger work becomes a goal (it
needs Beads: brew install beads, then bd init in your repo):
- **Interview.
// HOW IT'S BUILT
KEY FILES