メニュー
Default reviewer criteria for the with_review tool. Generic quality bar — accuracy, intent-match, no hallucinations, clarity. Use as the criteria.skill argument when calling with_review without a domain-specific reviewer skill.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/jezweb/vite-flare-starter --skill review-outputコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Evaluate multiple choices side-by-side based on relevant criteria, then present a comparison the user can act on. Use when the user asks to compare options, choose between alternatives, or weigh up X vs Y.
Day-of-week rotating proactive sweep — Mon=connections / Tue=routines / Wed=skills / Thu=memories / Fri=findings / Sat=cross-cutting / Sun=weekly summary. Forces outward scan instead of inward thrash. Routine-only; load this skill into a daily routine that fires AssistantAgent. Adapted from goanna's caretaker.
Use when an agent has had N consecutive quiet runs with nothing to do. Pivots to bounded inward consolidation (promote findings, refresh memory, audit asks) anchored in own data — NOT generic news summarisation. Adapted from goanna's reverie cycle. Routine-only; loaded by the routine that detects the quiet condition.
SOC 職業分類に基づく
SKILL.md を表示中
| name | review-output |
| description | Default reviewer criteria for the with_review tool. Generic quality bar — accuracy, intent-match, no hallucinations, clarity. Use as the criteria.skill argument when calling with_review without a domain-specific reviewer skill. |
Use these criteria when reviewing the worker's draft. Issue exactly one verdict per iteration:
Accuracy — every factual claim is grounded in the provided context or independently verifiable. No invented stats, dates, names, URLs, or quotes. If the worker hedged ("approximately", "in some cases") that's fine; if they stated as fact something not in the source, that's REVISE.
Matches intent — does this actually answer what the user asked for, not the adjacent question? An email asking for a refund should request a refund, not apologise. A code review should flag bugs, not document the code.
Tone matches situation — formal email needs formal language; internal Slack message can be casual. Look for tone mismatches that would jar the recipient.
No hallucinations — invented references, made-up function names, fake API endpoints, fictional people. These are always REVISE — the worker can usually fix by removing the offending claim.
Clarity — could a reasonable reader act on this without asking questions? Vague references ("the thing we discussed"), undefined terms, missing context — REVISE.
Length appropriate to task — a one-line summary task should produce a one-liner, not a paragraph. A detailed report should not be three sentences. Both directions are REVISE.
Respond with ONE LINE in this exact shape:
VERDICT: APPROVE — passes all checks
VERDICT: REVISE — second paragraph claims 23% growth but source says 18%
VERDICT: REJECT — answered "what's our pricing" instead of "draft a thank-you email"
The em-dash (—) or hyphen (-) is the parser delimiter — use either.