跳到正文
cccskills
免费在 GitHub 公开

deliverable-intake

Turns dictated captures in a deliverable's inbox/ into a proposed planning-wiki diff, classifying and tracing each statement; decisions need the author's assent. Use to intake notes or process the inbox.

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

查看安装方法

包含的文件(2)

  • SKILL.md4.7 KB
  • agents/openai.yaml252 B

SKILL.md(原文)

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

Deliverable intake

The author thinks out loud; the wiki stays authoritative. This skill is the seam between the two. It reads captures verbatim, proposes where each statement belongs, and applies nothing the author has not seen.

Inputs

  • The nearest deliverable.yml upward from cwd (or the path given). Read it, then planning_dir/00-README.md and every file that index names. That is the current state of the wiki; the proposal is a diff against it.
  • inbox/*.md that do not end in .done.md, oldest first. A capture is read verbatim and never edited.
  • --from-log N: show the last N entries of ~/.config/macwhspr/cleanup_log.jsonl ({ts, raw, cleaned} pairs) as a numbered list with the first line of each, and ask which to import. An imported entry is written to inbox/YYYY-MM-DD-HHMM-log.md with the cleaned text (the raw text appended under a <!-- raw --> marker) before anything else happens. Nothing is imported without being named.

Classify, then trace

Walk the capture paragraph by paragraph. Each statement gets exactly one class:

ClassGoes toNeeds assent?
decisionthe wiki file that owns the topic (00-README.md "Decisions recorded here", or the numbered file)yes, always
evidence claimthe wiki file for the section it supports, marked with the capture referenceno, but a claim naming a source that is not in sources_of_truth or the bib is written as UNRESOLVED: <claim>; when the manifest names a knowledge_base, the report lists each such source as a process-source candidate (drop the PDF in sources/unprocessed/) so intake feeds the knowledge base rather than bypassing it
question08-open-questions.md, open listno
task08-open-questions.md under a Tasks heading; one due before the next session is also named in the report, so the closure step carries it into HANDOFFno
droppednowhere; listed in the report with the reason (duplicate, already resolved, off-topic)no

Every proposed line carries a trace: (inbox/2026-09-10-debrief.md ¶3). A capture paragraph that yields no proposal is listed as dropped with its reason, so the author can see the capture was read whole.

Names, dates, numbers, and citations that the capture states but the wiki cannot confirm stay as dictated and are tagged UNRESOLVED. Do not correct a dictated name against a guess; do not invent a citation to match a claim; do not resolve a number from memory.

Propose

Produce one unified diff across the wiki files (new files included) plus the dropped list. Show it. Then put the decisions to the author as a numbered list, each with the sentence that would be written and where; use AskUserQuestion when there are three or fewer, a numbered list otherwise.

Apply

Once the author has seen the diff, apply the non-decision hunks and each decision they approved, then rename the capture to *.done.md. Do not edit any existing HANDOFF.md entry, today's included; the intake is recorded by the closure step ($finished) as Intake: <capture> -> <n> decisions, <n> claims, <n> questions, <n> tasks, <n> dropped, and if the session ends without closure the renamed capture and the wiki diff are the record. Record which capture paragraphs were promoted (a <!-- promoted: ¶1,¶3 --> line at the end of the .done.md file) so a partially accepted capture is never promoted twice. On refusal of any decision, leave that line out and keep the capture unrenamed until the author says otherwise.

Report

Five lines: captures read; counts by class; UNRESOLVED items (each with what would resolve it); decisions applied; what to run next ($deliverable-lint if the wiki changed materially, otherwise nothing).

Notes

  • One worker, no subagents; a cheap model suffices.
  • A reaction to a lint report is a capture like any other: dictate it into inbox/, then intake it; findings the author accepts become tasks, findings they reject go under a Rejected findings heading in 08-open-questions.md (the authoritative wiki, not NOTES.md) with the finding id and one line of reason, so the next lint does not raise them again.
  • Register vocabulary as it appears: a proper noun the dictation mangled twice belongs in ~/.config/macwhspr/vocab.md (offer, never append silently).

Codex notes

Present the complete patch before applying anything; decision hunks go in only with explicit approval. Files and formats are identical to the Claude skill.

评价

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

评论

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

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

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

0 / 1000 字

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

同一仓库的技能

advisor

免费

Consults Fable as an independent, read-only reviewer at an effort the caller matches to the question. The calling session (usually Opus, or Haiku) holds the task and escalates one decision point. Use before committing to an interpretation or a substantial piece of writing or analysis, when stuck or not converging, when changing approach, or as a final check on a finished task. Fallback for when the native advisor tool is unavailable. Not for a session already running Fable.

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

scdenney/open-science-skills692026年10月20日 更新

advisor

免费

Consult an independent, read-only GPT-6 Astra advisor before committing to a substantive interpretation, approach, or final result. Not for routine work, implementation, or file edits. Uses gpt-6-astra at an effort matched to the question.

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

scdenney/open-science-skills692026年10月20日 更新

beamer

免费

House rules and craft for LaTeX Beamer decks (storyboarding, slide prose, frame budgets, layout, XeLaTeX and Korean fonts, color, figures, Overleaf hygiene, build QA). Use to write, edit, review, or build a Beamer deck.

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

scdenney/open-science-skills692026年10月20日 更新

beamer

免费

House rules and craft for LaTeX Beamer slide decks (lectures, seminars, talks), drawn from the author's own Overleaf edits and published slide-design guidance. Covers storyboarding, frame titles, slide prose, word and frame budgets, layout without overfull boxes, XeLaTeX fonts and Korean (xeCJK), color, figures and screenshots, Overleaf source hygiene, speaker notes, and a build-and-QA loop with a contact sheet. Use when writing, editing, reviewing, or building a Beamer deck, theme, or storyboard. A course skill supplies course facts and the frame skeleton; this skill supplies the craft. Not for HTML or PowerPoint decks, posters, or papers.

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

scdenney/open-science-skills692026年10月20日 更新

Audit a manuscript's citations for fabricated sources, DOIs that resolve to the wrong work, in-text and reference-list mismatches, style, and claim support, verified against Crossref and OpenAlex. Use to check citations, references, a .bib file, or DOIs.

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

scdenney/open-science-skills692026年10月20日 更新

Audits a manuscript's citations for fabricated or nonexistent sources, DOIs that resolve to a different work, mismatches between in-text citations and the reference list, APA 7 or journal style, and whether each source supports the claim it is attached to. Checks entries against Crossref, OpenAlex, and DataCite and labels anything it could not verify NOT CHECKED. Use to check citations, references, a .bib file, or DOIs, or when a source may be AI-invented. Figures and tables go to figure-table-audit.

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

scdenney/open-science-skills692026年10月20日 更新

查看 scdenney 的全部技能

报告此技能的问题