跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

judge

Use when editing a draft, checking for AI voice patterns, reviewing prose quality, running readability analysis, auditing consistency, or validating SEO requirements on finished content.

https://github.com/Jeffallan · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Jeffallan/writing-with-agents --skill judge

技能说明


name: judge description: Use when editing a draft, checking for AI voice patterns, reviewing prose quality, running readability analysis, auditing consistency, or validating SEO requirements on finished content. license: MIT metadata: author: https://github.com/Jeffallan company: https://synergetic.solutions version: "1.0.0" domain: quality triggers: edit, review draft, judge, check quality, AI voice detection, readability, consistency check, proofread, polish, Strunk and White, editing pass role: specialist scope: analysis output-format: report related-skills: carpenter, quality-rubric, seo-writer

Role Definition

The Judge is the detection and reporting specialist. AI runs 5 detection passes and presents findings. Human decides which findings to act on. AI then implements the approved changes.

Lead: AI detects patterns, measures metrics, and reports findings. Support: Human reviews findings and decides which changes to approve.

The Judge inspects. All details that result in a polished piece become important ONLY in this last stage. During earlier phases, fussing over word choice or sentence rhythm would have been premature. Now it is the entire job.

The Judge does not rewrite. If a detection pass reveals structural problems -- a missing argument, a broken throughline, a section that contradicts the thesis -- the piece goes back to the Architect or Carpenter. The Judge handles line-level and pattern-level quality, not architectural repair.

When to Use This Skill

  • After the Carpenter phase has delivered a complete draft and the human has spot-checked it
  • When you need to detect AI-generated voice patterns in a draft
  • When you need to apply Strunk & White composition principles systematically
  • When you need readability metrics (Flesch-Kincaid, sentence stats, paragraph stats)
  • When you need to audit a draft for terminology, tone, and formatting consistency
  • When you need to validate SEO requirements on a finished piece
  • When you are doing a final polish pass before publication

Core Workflow

Step 1: Receive Draft, Edit Copy, and Blueprint

Read three inputs: the preservation draft (draft-N.md), the marked-up edit copy (draft-N-human-edits.md), and the original Architect blueprint. Confirm with the human that routing to the Judge has been approved (per the Carpenter's routing step; structural edits belong to the Architect, not here).

Parse the edit copy to extract two user-originated signal types (canonical definitions in ../_shared/markup-convention.md):

  • Auto-propagate: strikethroughs (~~text~~) and direct inline rewrites. These are user directives — apply unconditionally without asking.
  • Resolve: bracketed commentary ([text]) — questions, alternative phrasings, direction for the AI. For each bracket, draft a proposed resolution to present alongside the detection findings later.

The third signal type, Judge detection findings, is produced by Steps 2 and 3.

Step 2: Run Detection Passes in Order

Execute all five passes in sequence. Each pass builds on the context of prior passes.

  1. AI Voice Detection -- Broadest scan. Catches filler transitions, generic openings, hedge words, symmetrical structures, filler adverbs, and over-qualification. See references/ai-voice-detection.md.
  2. Strunk & White Rules -- Composition principles. Catches passive voice, needless words, negative form, vague language, loose sentence chains, separated modifiers, and weak endings. See references/strunk-white-rules.md.
  3. Readability Scoring -- Quantitative metrics. Calculates Flesch-Kincaid grade, sentence length stats, paragraph length stats, and flags outliers. See references/readability-scoring.md.
  4. Consistency Audit -- Cross-document checks. Catches terminology drift, tone shifts, formatting inconsistencies, and number/date format mismatches. See references/consistency-audit.md.
  5. SEO Validation -- Only when the Architect blueprint includes SEO requirements. Checks keyword placement, meta description, heading structure, and internal linking. Skip this pass entirely for non-SEO content.

Step 3: Consolidate All Three Signal Types into One Report

Merge the user's edits and the detection pass results into a single consolidated report with three sections:

  • Auto-propagate — list every strikethrough and direct rewrite the user made. These apply unconditionally; the list exists for transparency, not for approval.
  • Brackets to resolve — each bracketed comment from the edit copy, paired with the Judge's proposed resolution.
  • Detection findings — output of the 5 passes, grouped by severity (must-fix / review-and-decide), with the metrics summary.

See references/judge-consolidated-report.md for the report format.

Step 4: Present Report and Route via a Single AskUserQuestion

Deliver the full report. Do not make any changes to the draft yet. Use a single AskUserQuestion call covering every decision at once:

  • For each bracket: accept, modify, or reject the Judge's proposed resolution.
  • For each review-and-decide detection finding: apply or skip.
  • Routing choice: full Carpenter rebuild or light polish.

Routing criteria:

  • Full Carpenter rebuild — edits are substantial though not structural (multiple paragraphs rewritten, running threads added, significant tonal shifts). Rebuilding prose from the outline is cleaner than patching.
  • Light polish — edits are minor (grammar, word choice, small rephrasing within the existing structure). The Judge applies them inline.

Wait for explicit approval on every decision before proceeding.

Step 5: Execute the Routing Decision

Bundle the approved items into one set: auto-propagated edits (unconditionally) + accepted bracket resolutions + accepted detection findings. Then branch on the routing decision.

If routing = full Carpenter rebuild: Hand off the approved bundle to the Carpenter. The Carpenter integrates

阅读完整来源 ↗