القائمة
Goal-pursuit loop: measure, diagnose, experiment, verify, compare, and iterate against a measurable target. Triggers: evolve, optimize, make this better, push to target.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | evolve |
| description | Goal-pursuit loop: measure, diagnose, experiment, verify, compare, and iterate against a measurable target. Triggers: evolve, optimize, make this better, push to target. |
Use this when there is a measurable target and repeated changes can move it. Do not use it for vague quality polish, red CI, or one-off analysis.
.evolve/ state if present./hypothesize first and pull the top-ranked bet from its portfolio..evolve/.Use references/full-reference.md for statistical details, structured-hypothesis mode, and state schemas.
Use references/deterministic-loop.md for the tamper-proof measure.sh harness, auto-revert discipline, the ≥2× noise-floor keep-check, and the resumable playbook — the loop that makes evolve safe to run unattended for hours.
hypothesize when "what to try next" is no longer obvious — build a researched, ranked portfolio instead of guessing one lever.meta-harness or pursue after repeated measured plateaus.autopsy for surprising or null results.polish when the metric is fine but quality still needs fixed-rubric cleanup.Raise the ceiling, don't climb toward it. When a target is nearly hit or a metric has plateaued, question the target itself: name the binding constraint, separate the physics floor from the assumed floor, design the regime change that makes 10x reachable, commit through the valley. Triggers: 'breakout', '10x this', 'raise the ceiling', 'why are we capped', 'think way bigger', 'this metric is a cage'.
Prove that a merged change is actually live and production behavior is measured against the deployed artifact. Use after merge, before claiming deployed/live/validated, for Cloudflare Pages/Workers deploys, cache claims, perf claims, and release closeout.
Diagnose and improve eval harnesses built on @tangle-network/agent-eval or similar trace-first systems. Use when success/failure rates, scorecard deltas, judge outputs, promotion gates, benchmark rows, or improvement campaigns may be contaminated by harness bugs, evaluator drift, routing/auth failures, missing traces, or invalid baselines.
Split one messy experiment branch into N clean, independent branches — one logical change each, built from the merge-base, disjoint change-sets, each an isolated reviewable PR. Triggers: 'finalize', 'split this branch', 'atomize this', 'make reviewable PRs', 'decompose this mess'.
Read repo/session state and choose the single next skill: exploit (evolve/polish), explore (pursue/meta-harness/breakout), bootstrap (eval-agent), diagnose (diagnose/eval-harness-diagnose), or step back (reflect). One dispatch, then exit.
Adopt @tangle-network/hub-sdk in any product that needs to talk to the Tangle hub (OAuth connections, tools/search/describe/invoke, capability tokens, policies). Use whenever a product imports @tangle-network/agent-integrations, maintains a local hub-client.ts, or hand-rolls fetch() to /v1/hub/*. Forces kill-and-replace, not additive code.