goal-check
Give the human a compact reminder of the thread's longer-term goal, recent work, and the input needed next. Use when the user asks for a goal check, context reset, or quick orientation before continuing a task.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- goal-check
- description
- Give the human a compact reminder of the thread's longer-term goal, recent work, and the input needed next. Use when the user asks for a goal check, context reset, or quick orientation before continuing a task.
02 资源文件 1
- 参考文档agents/openai.yaml199 B
03 SKILL.md 正文
Goal Check
Summarize the current thread for the human. Infer the longer-term goal from the whole thread (or half-dozen of turns or so, if a lot has happened) and the near-term work from the most recent one or two tasks.
Return exactly this structure:
## Goal Check!
Here's my understanding of this <thread or project>:
| Type | Summary |
| --- | --- |
| Long | <one-sentence summary of the longer-term goal> |
| Near | <one-sentence summary of the most recent one or two tasks> |
| Next | <what the agent needs from the human to progress> |
Keep the entire response succinct. Apply these rules:
- If the longer-term goal is uncertain, give the best useful guess and append
(unclear)or a more precise short qualifier. - In
NEXT, bold each short, distinct response keyword in uppercase. If a choice is required then put each choice option in uppercase so that a single word can kick it in motion. If no human input is needed, mention that. - Keep each table value on one line. Escape/replace literal pipe characters in values so the Markdown table remains valid.
- Include no preamble, explanation, bullets, code fence, closing, or other commentary outside the heading and table.
- Assume that if this skill is given, the human or agent is not quite sure where things stand and it is your job to make sure their next turn is with clear context in plain language.
04 同仓库更多 Skills
write-simplified-technical-english
Write, rewrite, or review technical content with ASD-STE100 Simplified Technical English (STE), Issue 9. Use only when the user explicitly invokes $write-simplified-technical-english. Common requests mention ASD-STE100, STE, or "write STE"; do not use for general requests for clear, simple, concise, or technical writing.
write-plainly
Write, rewrite, or review prose in plain language for its intended reader while preserving technical meaning, constraints, uncertainty, and protected literals. Use when the user asks for plain language or plain English, audience-appropriate clarity, an easier-to-understand explanation, or a meaning-preserving simplification of technical prose. When one of those triggers applies, use for public information, documentation, instructions, explanations, notices, and interface text. Do not invoke solely for proofreading, shortening, generic copyediting, humanizing prose, removing AI tells, marketing voice, or creative rewriting. When the user explicitly requests ASD-STE100, STE, or invokes $write-simplified-technical-english, use that skill instead.
write-humanly
Draft, rewrite, or review prose so it sounds like a particular human had a reason to write it. Use when the user asks for human-sounding or less AI-ish writing, dislikes the wording or tone, wants anti-AI prose review or voice matching from supplied human text, needs an existing document's voice preserved, or wants familiar LLM habits removed, such as corrective antithesis, triplets, stock metaphors, prestige filler, needless em dashes, generic assistant language, and performative confidence. Do not invoke solely for plain language, proofreading, shortening, generic copyediting, or a change in formality. Use only when the request concerns human voice, authorial character, or generated-prose texture.
what-what
The user is asking: What is this thread (or main thread) asking for here? Give it to me and $write-humanly. What is even the context? What changes?
what-huh
Make final responses understandable to a reader who cannot see the agent's working text, especially when reporting progress, explaining findings, or asking for a decision.
verifier-system
Establish and keep a project's verification practice useful through Surface, Answer Key, and Comparison. Use for setup verifier-system, choosing how to verify agentic changes, or updating a project's verification guidance as its components evolve.