跳到正文
cccskills
免费在 GitHub 公开

away-brief

Give the owner one page when they come back from sleep, a meeting or a long run: what got done, what is stuck, what waits for their answer, and what it cost in quota. Use when the owner asks what happened while they were away, wants a status page, or when you finish a long stretch of work and must report it.

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

实测评分 未实测

查看安装方法

包含的文件(4)

  • SKILL.md3.4 KB
  • scripts/away-brief12.3 KB
  • scripts/away-brief.t16.1 KB
  • scripts/selftest/run-selftest.sh1.3 KB

SKILL.md(原文)

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

away-brief

sno away-brief run reads what already exists and prints one page of at most 60 lines. It changes nothing except its own list of quota readings, and Reach, which may note that it has seen the cards that the inbox read listed (it never moves, accepts or finishes them).

## Done       new commits, charters delivered since the cutoff (with how many checks are proven),
              progress records that finished or are still going
## Stuck      charters not finished (with the numbers of the checks not yet proven), progress records
              with tasks left that nobody has touched for two hours
## Needs you  Reach cards of type question or decision waiting in the inbox
## Spend      your heartbeats, and each vendor's quota now with the change since the last reading

A source it cannot read prints not read: <what> -> <why> and the rest of the page still prints. Each section has its own share of the 60 lines; items beyond it are replaced by an and N more not shown line, so a long Done list never pushes out what waits for the owner or the quota.

Prerequisites: bash 4+, GNU coreutils, git and jq. It uses sno deliver-proof (the deliver skill) to count proofs, sno reach inbox, sno heartbeat --list and sno subscription-quota-check when they are installed.

Use

  1. Run sno away-brief run --since 12h in the project's git folder. Change --since to the time the owner left (8h, 2d, or a date). Add --repo DIR for each other repository and --charters DIR for folders that hold charters or progress records outside those repositories. Add --as <your seat> (or set SNO_REACH_ADDR) so the inbox is read.
  2. Read the page and tell the owner the three things that matter most, in plain words: what is finished, what is blocked and why, and what needs their answer. Keep the page's evidence paths so they can open the file. Do not add work that is not on the page.
  3. Quota: a reading shows usage now, not spend. When the owner is about to leave, run sno away-brief mark once; it stores a reading, so the next page can show what was spent since. Without an earlier reading the page says so instead of guessing.

What the page can and cannot say

  • "Done" is only what is in git, in a delivered charter, or in a finished progress record. Work that was never committed or recorded does not appear.
  • "Stuck" is a charter whose recorded proofs are missing or failing, or a progress record (written by sno handoff-checkpoint) with tasks left and no update for two hours. An agent that is busy but does not write records looks quiet.
  • "Needs you" is only the seat you name. Questions sent to other seats are not shown.
  • The change in quota compares two readings of the same window; if the window reset in between, the page says so instead of showing a negative number.

评价

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

评论

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

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

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

0 / 1000 字

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

同一仓库的技能

Answer how long agent work will take, how much longer active work needs, or what clock time applies. Estimate full AI-agent wall time, measure active progress first, and get owner-facing times from `sno report-time`. Never estimate human-developer time.

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

sno-ai/sno-station-skills7432026年10月24日 更新

Prove that a reported run caused its intended real effect. Walk the executor path from entry to effect, capture one observable per hop, and report a result a no-op could not produce.

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

sno-ai/sno-station-skills7432026年10月24日 更新

Report how many problems the two brains found: mutual review (the other model checks the work, from the peer-review records) and self-check (an agent finds its own error in its own conversation, judged by that agent's own model), side by side. Use when the owner asks whether the second agent or the reviews are worth it, or wants the week's review results.

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

sno-ai/sno-station-skills7432026年10月24日 更新

charter

免费

Write, revise or review a charter: the one document that tells an executor what to deliver, what is out of bounds, what the owner already decided, and how each success check will be proven. Use when work needs a written brief before someone else does it, or when asked to write, change or check a charter.

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

sno-ai/sno-station-skills7432026年10月24日 更新

Route production coding tasks from Claude Code to the user-level Codex Shell, TypeScript, Python, or Rust workflow through a direct `codex exec` run. Use for "codex-coder", "ask Codex to write code", "generate with Codex", language migrations, or mixed Shell/TypeScript/Python/Rust implementation.

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

sno-ai/sno-station-skills7432026年10月24日 更新

Route production coding tasks to the user-level Shell, TypeScript, Python, or Rust Codex workflow. Use for "codex-coder", "Codex write", "generate with Codex", language migrations, or mixed Shell/TypeScript/Python/Rust implementation when Codex should choose the correct language specialist automatically.

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

sno-ai/sno-station-skills7432026年10月24日 更新

查看 sno-ai 的全部技能

报告此技能的问题