- name
SKILL.md
File skill tetap berada di repositori penerbit.
Tempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add boshu2/agentops --skill craft-goal -a cursor -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add boshu2/agentops --skill craft-goal -a claude-code -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add boshu2/agentops --skill craft-goal -a codex -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add boshu2/agentops --skill craft-goal -a grok -yKirim pesan yang disalin di chat Grok Bot. Bot mengambil SKILL.md ini dari GitHub dan menambahkannya ke skill yang dipakai bersama oleh semua Bot Anda.
Install this skill: https://github.com/boshu2/agentops/tree/HEAD/plugin/skills/craft-goalDari penerbit
Craft or lint a goal prompt: the contract a long-running goal runtime follows over a bead graph, picking each next experiment (one build bead) until a frozen finish line is proven or a limit stops it. The number of experiments 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.
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 work 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 and needs no tracker installed to compile a prompt; the goal it writes runs on one.
Asked to craft ("craft a goal", "turn this into a goal"), return the decision, then the filled prompt and settings when safe. Asked to lint ("lint/review this goal", "is this safe"), return the 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, authority, and the tracker the goal runs on (any with status, dependencies and notes; BD is one); 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_PLAN: one shaped change with no verdict-driven follow-on; hand it to
Plan or native execution (RPI only if the caller selects it).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, tracker or campaign size; return UNSAFE_GOAL with the
missing decisions. The caller owns revision and goal creation.
The template's experiment policy and breaker carry these into the runtime. They prevent 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.
The template's Breaker and helper section is the one list of HOLD triggers (implementation stops for causal review) and helper rules; fill its threshold and keep every line.
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_PLAN 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.SAFE_TO_CREATE.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.
Draft or lint a bounded long-running goal prompt with a finish line and hard limits. Use when: asked to craft or lint a goal (a /goal prompt); one change goes to Plan.
---name: craft-goaldescription: Draft or lint a bounded long-running goal prompt with a finish line and hard limits. Use when: asked to craft…---# plugin/skills/craft-goal/SKILL.mdFAQ
Unduh plugin/skills/craft-goal/SKILL.md dari penerbit, atau salin path-nya dan buka repositori. PlugMCP hanya mendaftar skill ini dan tidak meng-host filenya.
Penerbit menyimpannya di https://github.com/boshu2/agentops.
Claude, Cursor, Codex, dan Grok Build bisa membaca SKILL.md yang Anda tambahkan dari repositori penerbit. Grok Bot memasangnya saat Anda mengirim tautan folder GitHub skill tersebut di chat.
NEEDS_OPERATOR