跳到正文
cccskills
免费在 GitHub 公开

gaia-steward-full

Run Gaia Steward end to end: observe every routine's detectors, triage debt by authority, land Class A repairs on the integration branch, drive one bounded Class B dispatch through an independent verifier, re-observe, and leave a quiet founder desk or a precise list of decisions. Use for "/gaia-steward-full", "run the steward", "full maintenance pass", "what does the repo need", "resume the steward run", or a scheduled maintenance wake. Thin entrypoint: each phase is an atomic gaia-steward-* skill.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md5.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

gaia-steward-full

The root of Gaia Steward Full. It owns no logic of its own: the deterministic runner (gaia steward full) decides every state transition, and the atomic skills below each do one job. This file maps a mode to a command and an action to a skill, and states the rules that hold across all of them.

Modes

InvocationCommandSkill
/gaia-steward-fullgaia steward full run --jsonthis loop
--observegaia steward full run --observe --jsongaia-steward-observe
--triagegaia steward full run --triage --jsongaia-steward-triage
--routine Ngaia steward full run --triage --routine N --jsongaia-steward-triage
--debt IDgaia steward full run --triage --debt ID --jsongaia-steward-triage
--verifygaia steward full run --verify --jsongaia-steward-verify
--retrogaia steward full run --retro --jsongaia-steward-retro
--statusgaia steward full status --jsongaia-steward-desk
--resume RUNgaia steward full run --resume RUN --jsonthis loop
--afkadd --afk to any runthis loop

The runner itself never prompts in any mode; --afk is recorded on the run for audit and tells the driver to queue founder decisions instead of asking. An awaiting-action run keeps the run lease until its TTL, so a second invocation meanwhile exits 4 (observing-existing).

Scheduled runs add --trigger scheduled. Class A landing additionally needs --integration-branch dev/<name> --push (or GAIA_STEWARD_INTEGRATION_BRANCH); the runner refuses main, master and the remote default branch.

The driver loop

The runner makes zero model calls. Whatever needs a model or a forge comes back as a pending action. Drive it like this, and nothing else:

  1. Run the mode's command. Read status, nextAction and actions.

  2. For each pending action, hand it to exactly one owner:

    Action typeOwner
    agent.builda fresh builder agent following gaia-steward-lane, given only params.promptPath
    agent.verifya different, fresh agent following gaia-steward-verify
    forge.open_prgaia-steward-land (draft PR to the integration branch)
    lead.integratethe orchestrator, merging into the integration branch only
  3. Record each outcome: gaia steward full record RUN STEP --input outcome.json.

  4. Resume: gaia steward full run --resume RUN --json. Repeat until the run is completed or blocked.

  5. Render the desk (gaia-steward-desk) and stop.

The runner tracks every step in a durable ledger (refs/heads/steward/ledger, or a local file when no remote answers). Resuming never repeats a recorded step, and a second concurrent invocation loses the lease and refuses cleanly.

Agents, models and effort

  • Builders: params.allowedModels (Haiku or Sonnet). Verifier: Sonnet only, and never an agent listed in params.forbiddenAgentIds.
  • Every agent invocation names an explicit thinking effort. default and inherit are refused by record.
  • Subagents do not fan out without the orchestrator's approval.
  • No other models are authorized.

Hard limits (enforced in code, repeated here)

  • Never merge into main, push to main, force-push, tag, release or publish.
  • Class B: maxInFlight 1, maxAttempts 2, cooldown 3600 s, one dispatch per run. Need more throughput? File a founder-reviewable amendment (founder/steward/decisions/); never loop the CLI to get around the cap.
  • Unknown coverage blocks Class A for the run. A not-evaluated sensor is never healthy.
  • Class C goes to the desk. Founder availability is not permission, and --afk only queues decisions while A/B work continues.
  • The builder never verifies its own work; the machine can reject or escalate but never accept.

Reused skills

Steward finds and bounds the work; existing skills do the specialised parts.

Debt or situationSkill
any Class B dispatchgaia-steward-lane (the builder's contract)
trust_calibration_drift, trust_stamp_stalegaia-tm-inspect first: verify the effective-evidence context before any calibration
timeline_causality_driftgaia-trace-timeline to reconstruct the order; the fix stays human-gated
generated_projection_driftgaia-docs-sync
ci_failure, CI churnci-churn
escalated work too large for one dispatchgaia-triage, then gaia-issue-resolver or feature-pipeline on its own PR

Stop conditions

Stop and report when the run is completed or blocked, a step is refused twice, a lease is lost, or an action asks for anything outside the table above.

Where the rest lives

  • Architecture contract: founder/handovers/2026-10-20-steward-full-architecture.md
  • Coverage catalog and checker: founder/steward/routine-coverage.json, scripts/check_steward_coverage.py
  • Policy: founder/steward/POLICY.yaml; decisions: founder/steward/decisions/

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

ci-churn

免费

Measure CI churn cost for a pull request: how many commits and how many CI-compute seconds were burned on avoidable "fix the CI" push rounds. Use when you want to understand the efficiency cost of a PR's iteration cycle, get actionable pre-push check suggestions, or include a churn summary in a pipeline report. Triggers: "ci churn", "how much CI did we burn", "avoidable commits", "ci efficiency", "wasted CI time", "churn report", "/ci-churn". Called automatically by /fp-drift at pipeline close.

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月24日 更新

Produce the rendered evidence a human-gated frontend PR owes its reviewer: capture each changed surface (plus the before state for anything modified, plus mobile width), then generate one self-contained local HTML page the founder can open and review without checking anything out. Use when a PR is gated by the "Frontend changes are HUMAN-GATED" section of CLAUDE.md, or when the user says "/design-gate", "screenshot evidence for this PR", "prep this for founder review", "build the design evidence page", "what does this look like before and after". The page comes from a template script, not hand-written markup. Output is session-local and never committed. Do NOT use for non-gated changes: typo/grammar/factual fixes in an unchanged block, dead link targets, alt/ARIA fixes with no visual change, cache-bust bumps, or refactors with no rendered diff.

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月24日 更新

One-fix-at-a-time, approval-gated design fix recovery. Given a checklist of fixes (handover doc, CHECKLIST.md, or inline list), applies each individually, presents a diff, and waits for an explicit APPROVE / REJECT / NO CHANGES decision before committing. Trigger phrases: /design-iteration, "go through the checklist one by one", "fix these one at a time", "bucket recovery", "design fix pass".

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月24日 更新

Playbook for correcting a named skill's star level to match its computed Trust Magnitude grade, with an independent post-calibration verification pass and a CLI-logged timeline event (never hand-written). Use when: recalibrating a skill's level, fixing a stale or drifted star rating, running a batch of `gaia dev calibrate` corrections, or confirming a past calibration actually landed. Triggers: "calibrate <skill>", "recalibrate the trust magnitude backlog", "promote/demote <skill> to N stars", "why is <skill> still N stars", "verify a calibration actually landed", "Hall of Heroes ranking is wrong".

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月24日 更新

Close out a completed EPIC / sprint end-to-end: author a fact-verified meta-post announcing what shipped, archive the EPIC's handovers, snapshot orchestrator memory, gate the integration→main merge on CI-green + explicit human go, drive the version bump (merge-commit conventions that auto-sync classifies), and verify the release reached the registry/PyPI. Use when the user says "close out EPIC <n>", "wrap up the sprint", "ship the meta shift", "/epic-close", or asks to finalize an integration branch that is ready to merge to main. Generalizes the EPIC 1002 (Yggdrasil II) close-out. This skill orchestrates — it authors founder docs directly (superadmin) and delegates code/regen to workers; it NEVER merges to main without the human gate.

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月24日 更新

Run this skill for Phase 3 of the evidence verification pipeline — the adversarial audit step. Use when you need to check the evidence data lake for bad data before ingestion: dead links, wrong URL formats (tree/ vs blob/), subjective wording ("elite", "high-quality"), stale migration notes, benchmark catalog misuse/vendor-claim leakage, or skills whose star evidence conflicts with classified evidence level. Triggers on phrases like: "audit the data lake", "adversarial check", "ev-adversarial-audit", "check for noise in evidence", "flag bad evidence", "run the audit phase", "quality check the by-type files", or any reference to Phase 3 of the pipeline.

中文简介正在准备中。当前显示原文说明。

gaia-research/gaia-skill-tree232026年10月24日 更新

查看 gaia-research 的全部技能

报告此技能的问题