Minimizing Ty Ecosystem Changes
astral-sh/ruff
A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…
Draft or lint a bounded long-running goal prompt with a finish line and hard limits.
$ npx skills add boshu2/agentops --skill craft-goal -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install boshu2/agentops craft-goal --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/craft-goal .claude/skills/craft-goal && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "craft-goal" agent skill from https://github.com/boshu2/agentops/tree/main/skills/craft-goal into .claude/skills/craft-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "craft-goal", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/boshu2/agentops/tree/main/skills/craft-goalType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add boshu2/agentops --skill craft-goal -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install boshu2/agentops craft-goal --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/craft-goal .agents/skills/craft-goal && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "craft-goal" agent skill from https://github.com/boshu2/agentops/tree/main/skills/craft-goal into .agents/skills/craft-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "craft-goal", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boshu2/agentops --skill craft-goal -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install boshu2/agentops craft-goal --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/craft-goal .cursor/skills/craft-goal && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "craft-goal" agent skill from https://github.com/boshu2/agentops/tree/main/skills/craft-goal into .cursor/skills/craft-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "craft-goal", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/boshu2/agentops.git --path skills/craft-goal--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add boshu2/agentops --skill craft-goal -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install boshu2/agentops craft-goal --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/craft-goal .gemini/skills/craft-goal && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "craft-goal" agent skill from https://github.com/boshu2/agentops/tree/main/skills/craft-goal into .gemini/skills/craft-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "craft-goal", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install boshu2/agentops craft-goalInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add boshu2/agentops --skill craft-goal -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/craft-goal .github/skills/craft-goal && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "craft-goal" agent skill from https://github.com/boshu2/agentops/tree/main/skills/craft-goal into .github/skills/craft-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "craft-goal", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add boshu2/agentops --skill craft-goal -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install boshu2/agentops craft-goal --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/craft-goal .opencode/skills/craft-goal && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "craft-goal" agent skill from https://github.com/boshu2/agentops/tree/main/skills/craft-goal into .opencode/skills/craft-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "craft-goal", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
craft-goalDraft or lint a bounded long-running goal prompt with a finish line and hard limits.
Craft Goal is an agent skill from boshu2/agentops. Draft or lint a bounded long-running goal prompt with a finish line and hard limits. Use when: selected by name; one change goes to Plan.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/goal-prompt.md` and `scripts/validate.sh`).
It sits in Development, covering Linting and formatting. The repository describes itself as: DevOps discipline for AI coding agents: shape the work, track it as a graph, and get each change judged by a context that didn't write it. The licence is Apache-2.0.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 06165d9. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Craft Goal loads about 2.7k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 37 tokens; SKILL.md has 1,369 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from boshu2/agentops at commit 06165d9, republished under its Apache-2.0 licence (© boshu2). 1,369 words, ~2,692 tokens.
.claude/skills/craft-goal/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Craft or lint the autonomy contract above AgentOps RPI. A goal is a persistent controller (the Goal / Mayor role) over a bead-shaped experiment graph: each RPI is one scientific trial, and the goal picks the next useful trial, preserves what was learned and ratchets toward a larger outcome.
Goal / Mayor: observe graph → choose bounded wave → consume results → ratchet
└─ Bead: durable experiment intent, context, scratch, evidence, and links
└─ RPI: plan → implement → checks → one fresh validate where a mistake is costly → report
└─ Implementation: one RED → GREEN → refactor experimentThe number of RPIs need not be known in advance. A goal is safe when success is decidable, every experiment is bounded, evidence keeps its provenance, and the authorization envelope cannot silently renew itself. Beliefs are revisable: new evidence may retract an earlier claim. More stored knowledge is neither progress nor proof that knowledge is correct.
Authority boundary. The emitted prompt and safety report are inert caller-owned text. Crafting creates no goal, starts no runtime, mutates no bead and confers no standing authorization. The prompt drives RPI dispatch only when a caller pastes it into their own goal runtime, under their own authority and within the non-renewing envelope they set. Craft Goal reads tracker state when present but needs no tracker installed to compile a prompt.
| Caller wording | Mode | Result |
|---|---|---|
| "craft a goal", "turn this into a goal" | craft | Decision, then the filled goal prompt and settings when safe. |
| "lint/review this goal", "is this safe" | lint | Decision and findings, plus a rewrite when supplied facts permit one. |
Fuzzy route is acceptable; fuzzy success is not. Before goal creation the caller must know the outcome, what evidence would prove it, non-goals, and authority; the exact experiment graph may still be unknown. Write each terminal criterion as a Given/When/Then with an observable result and name each domain term once; the caller can settle these with Interview first.
USE_RPI: one shaped experiment with no verdict-driven follow-on.SAFE_TO_CREATE: a terminal outcome that may need several related
experiments, with those decisions and the budgets below supplied. A shaped
goal with no beads may begin with 1 bounded discovery wave that creates the
root and initial experiment beads.UNSAFE_GOAL: no falsifiable first question or terminal evidence can be
named (route that intent to idea or plan work), or the request is indefinite
monitoring or event reaction, which is an automation, not a terminal goal.Goals come in different sizes: size the wave and hard envelopes to the
outcome, never to one universal budget. Do not invent acceptance, authority,
graph semantics or campaign size; return UNSAFE_GOAL with the missing
decisions. The caller owns revision and goal creation.
The two failure modes this prevents: the completion treadmill, where discoveries keep becoming requirements and activity continues without new information, and first-red abandonment, where one falsified hypothesis ends a viable campaign.
Declare both envelopes with numbers before any work is selected, helper and validation costs included:
Name the native control that enforces each claimed hard limit and how the remaining allowance is observed. Objective text is an instruction, not enforcement: never report an unmeasured aggregate as a remaining balance, and never claim the goal is paused from prose alone. No helper, retry, new subject, compaction or wave renews the goal allowance.
Enter HOLD on any declared trigger: repeated blocker, no ratchet for the configured number of RPIs, oscillation between prior approaches, introduced regression, unknown new-defect cause, recurrence, requested acceptance change, or operator-reserved decision. HOLD stops implementation for causal examination. While the remaining allowance admits it, consult exactly 1 bounded fresh-context helper per HOLD incident, supplying acceptance, observations, failed approaches, exact evidence and remaining allowance. Rewording the blocker or an automatic continuation is not a new incident.
UNSTUCK must name a materially different experiment, its discriminating
check, and why it fits unchanged acceptance, authority and remaining bounds;
only the selected outer goal may resume, and it never revives a spent RPI
bound.ESCALATE, an unhelpful helper or no admissible experiment emits
NEEDS_OPERATOR; no more implementation or helper dispatch follows.NOT_ACHIEVED with the exact gaps. A retry threshold
alone is not proof of a spent hard budget.When operator action is required, report it truthfully and keep work stopped.
A controller's threshold for recording blocked is status bookkeeping, never
permission for extra experiments or helpers.
| Dimension | Passes when the prompt |
|---|---|
| outcome | names one larger caller-visible result. |
| evidence | gives each terminal criterion as a Given/When/Then with its authoritative proof. |
| admission | fits a goal: several related experiments, a falsifiable first question, a terminal finish. |
| bead graph | names the root epic or its bounded bootstrap rule and ties each experiment to an unmet criterion or named blocking uncertainty. |
| RPI boundary | makes one bead one RPI, takes checks and CI as an ordinary bead's result, limits fresh validation to the costly cases and consumes verdicts unchanged. |
| ratchet | counts progress only as evidence tied to an unmet criterion or blocking uncertainty, never activity, counts or digests. |
| discovery | keeps all three classes (necessary-now, linked-follow-up, HOLD/rescope) and never downgrades a necessary finding. |
| wave budget | sets numeric RPI, concurrency, time or token and live-attempt limits per wave, with a checkpoint. |
| hard budget | sets numeric campaign totals that nothing resets, naming the enforcing control or the unmeasured aggregate. |
| breaker | sets the numeric no-ratchet threshold and the HOLD triggers. |
| operator andon | allows one helper per HOLD incident, maps UNSTUCK and ESCALATE, and stops implementation on NEEDS_OPERATOR. |
| scope | states non-goals and exact read, write, external and Git authority. |
| self-hosting | repairs an unstable factory from outside it and runs the factory only as a declared bounded canary. |
| terminal reports | defines ACHIEVED, NOT_ACHIEVED and NEEDS_OPERATOR. |
Fill the copy-paste-only goal prompt: keep its headings and terminal semantics and replace every angle-bracket field. Return, in order:
SAFE_TO_CREATE,
USE_RPI or UNSAFE_GOAL. SAFE_TO_CREATE judges prompt content; it does
not certify native enforcement or create a goal.UNSAFE_GOAL, each missing decision; the caller can settle them with
Interview.This skill makes one pass, craft or lint, then returns. It never creates or
runs a goal and never mutates beads. The goal it writes stops at its first
terminal report: ACHIEVED, NOT_ACHIEVED or NEEDS_OPERATOR.
© boshu2, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts, references) in skills/craft-goal of boshu2/agentops.
Open the folder on GitHubat commit 06165d9
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in boshu2/agentops, which our catalogue first saw on October 7, 2026.
Craft Goal next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Craft Goal this skillboshu2/agentops | 448 | 1 repos | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Minimizing Ty Ecosystem Changesastral-sh/ruff | 50k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.4k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Babysit PR To Pass CIsgl-project/sglang | 37k | 2 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Summarise Ecosystem Resultsastral-sh/ruff | 50k | — | ~2.2k | Automated safety check: Pass | MIT |
astral-sh/ruff
A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
sgl-project/sglang
Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
astral-sh/ruff
A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
boshu2/agentops
Dispatch independent tasks to parallel workers or subagents without write collisions.
boshu2/agentops
Compare independent opinions from several models or contexts without inflating agreement.
boshu2/agentops
Write or update READMEs, docs, repo instructions and handoff notes, checked against source.
boshu2/agentops
Brainstorm evidence-backed options for what to build, or stress-test an idea.
boshu2/agentops
Change or repair code, config or services without weakening tests; report what ran and what did not.
boshu2/agentops
Write, find or curate lessons and agent rules with stated evidence and limits.
Categories
Draft or lint a bounded long-running goal prompt with a finish line and hard limits. Craft Goal is an agent skill from boshu2/agentops. Draft or lint a bounded long-running goal prompt with a finish line and hard limits.
Craft Goal fits situations like: : selected by name; one change goes to Plan.
Run `npx skills add boshu2/agentops --skill craft-goal -a claude-code`. Or copy the skill folder (skills/craft-goal in boshu2/agentops) into .claude/skills/craft-goal in your project. Claude Code loads it when a task matches its description.
Run `npx skills add boshu2/agentops --skill craft-goal -a codex`. Or copy the skill folder (skills/craft-goal in boshu2/agentops) into .agents/skills/craft-goal in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add boshu2/agentops --skill craft-goal -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/craft-goal, .gemini/skills/craft-goal, .github/skills/craft-goal and .opencode/skills/craft-goal in your project.
Going by SKILL.md and its folder, Craft Goal needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Craft Goal is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 828 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Craft Goal: Minimizing Ty Ecosystem Changes (astral-sh/ruff, 50k stars), Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.4k stars), Babysit PR To Pass CI (sgl-project/sglang, 37k stars) and Rust Best Practices (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
boshu2 (a GitHub user) maintains it in boshu2/agentops, which has 448 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 11, 2026.
Source: boshu2/agentops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.