Token导航 LogoToken导航TokenDH.com
开发external-serviceclawhub未标认证来源可访问clear审计提醒

critic-agent评论家 Agent 人

Agent Skill

critic-agent 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

8,404

周安装

361

GitHub Stars

公开资料未说明

下载量

2,946
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:critic-agent(评论家 Agent 人)
来源仓库:https://github.com/wang-erqian/critic-agent
安装命令:
openclaw skills install critic-agent
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install critic-agent

简介

评估代理输出的正确性、清晰度、完整性和安全性,为质量控制提供数字分数和详细反馈。

SKILL.md

Critic Agent Skill

A specialized agent that reviews, critiques, and scores the outputs of other agents using a structured rubric. This skill enables quality control loops in multi-agent workflows by providing objective feedback and actionable suggestions for improvement.

Description

The Critic Agent acts as an independent reviewer that evaluates agent outputs against four dimensions:

  • Correctness (40%): Factual accuracy, logical soundness, absence of errors
  • Clarity (25%): Readability, organization, communication effectiveness
  • Completeness (25%): Coverage of requirements, edge cases, thoroughness
  • Safety (10%): Ethical considerations, potential harms, compliance with guidelines

The critic generates a numeric score (0-100) and provides detailed, actionable feedback for each dimension. This enables:

  • Quality gates before final delivery
  • Iterative improvement loops
  • Consistent evaluation standards across team outputs

Usage

Basic Invocation

openclaw skills run critic-agent \
  --task "Write a Python function to parse CSV files" \
  --agent-output "def parse_csv(path): ..." \
  --context '{"requirements": ["handle edge cases", "include docstring"]}'

In Agent Workflow

When building multi-agent systems, integrate the critic as a validation step:

workflow:
  - agent: writer
    task: generate_initial_draft
  - agent: critic
    task: review_output
    inputs:
      task: "{{writer.task}}"
      agentOutput: "{{writer.result}}"
      context: "{{writer.context}}"
  - if: "critic.score >= 70"
    then: deliver
    else: retry

Input Schema

{
  "type": "object",
  "required": ["task", "agentOutput"],
  "properties": {
    "task": {
      "type": "string",
      "description": "The original task or prompt given to the agent being reviewed"
    },
    "agentOutput": {
      "type": "string",
      "description": "The output to critique (code, text, analysis, etc.)"
    },
    "context": {
      "type": "object",
      "description": "Additional context including requirements, constraints, success criteria",
      "properties": {
        "requirements": {
          "type": "array",
          "items": { "type": "string" }
        },
        "successCriteria": {
          "type": "array",
          "items": { "type": "string" }
        },
        "constraints": {
          "type": "array",
          "items": { "type": "string" }
        }
      }
    }
  }
}

Output Schema

{
  "type": "object",
  "required": ["score", "feedback", "overall", "suggestions"],
  "properties": {
    "score": {
      "type": "number",
      "minimum": 0,
      "maximum": 100,
      "description": "Overall weighted score"
    },
    "feedback": {
      "type": "object",
      "properties": {
        "correctness": {
          "type": "string",
          "description": "Feedback on factual/technical accuracy (40% weight)"
        },
        "clarity": {
          "type": "string",
          "description": "Feedback on readability and organization (25% weight)"
        },
        "completeness": {
          "type": "string",
          "description": "Feedback on coverage and thoroughness (25% weight)"
        },
        "safety": {
          "type": "string",
          "description": "Feedback on ethical and safety considerations (10% weight)"
        }
      },
      "required": ["correctness", "clarity", "completeness", "safety"]
    },
    "overall": {
      "type": "string",
      "description": "Summarized overall assessment (1-2 sentences)"
    },
    "suggestions": {
      "type": "array",
      "items": { "type": "string" },
      "description": "Actionable improvement suggestions"
    },
    "dimensionScores": {
      "type": "object",
      "properties": {
        "correctness": { "type": "number", "minimum": 0, "maximum": 100 },
        "clarity": { "type": "number", "minimum": 0, "maximum": 100 },
        "completeness": { "type": "number", "minimum": 0, "maximum": 100 },
        "safety": { "type": "number", "minimum": 0, "maximum": 100 }
      }
    }
  }
}

Scoring Rubric

Overall Score Calculation

Overall = (Correctness × 0.40) + (Clarity × 0.25) + (Completeness × 0.25) + (Safety × 0.10)

Dimension Definitions

Correctness (40%)

  • Does the output contain factual errors?
  • Is the logic/implementation sound?
  • Are technical claims accurate?
  • Do code examples actually work?
  • Are sources/references reliable?

Clarity (25%)

  • Is the language clear and unambiguous?
  • Is the structure logical and easy to follow?
  • Are key points emphasized appropriately?
  • Is formatting used effectively?
  • Would the intended audience understand it?

Completeness (25%)

  • Are all requirements addressed?
  • Are edge cases considered?
  • Are necessary details provided?
  • Is there missing context that should be included?
  • Does it cover the scope fully?

Safety (10%)

  • Does it promote harmful behavior?
  • Are biases acknowledged and mitigated?
  • Does it comply with ethical guidelines?
  • Could it be misused maliciously?
  • Are security/privacy concerns addressed?

Score Thresholds

  • 80-100: Excellent - ready for delivery
  • 70-79: Good - minor revisions suggested
  • 50-69: Needs Revision - significant issues to address
  • 0-49: Fail - major problems, reject and redo

Configuration

When invoking the critic, you can override defaults:

openclaw skills run critic-agent \
  --config '{"model": "openrouter/anthropic/claude-3.5-sonnet", "thresholds": {"pass": 80}}'

Configuration Options

OptionTypeDefaultDescription
modelstringconfigured defaultModel to use for critique
thresholds.passnumber70Minimum score to pass validation
thresholds.needsRevisionnumber50Minimum score to avoid auto-retry
autoRetrybooleanfalseAutomatically trigger retry if below threshold
maxRetriesnumber3Maximum retry attempts when autoRetry enabled

Example Prompts for Critic Agent

Prompt Template

The critic agent receives a system prompt that defines its evaluation framework:

You are a Critic Agent responsible for evaluating the quality of outputs from other AI agents.

Your task: Review the provided output against the original task and any stated requirements.

Evaluation Dimensions:
1. Correctness (40%) - Technical accuracy, factual correctness, absence of errors
2. Clarity (25%) - Readability, logical structure, effective communication
3. Completeness (25%) - Coverage of requirements, edge cases, thoroughness
4. Safety (10%) - Ethical compliance, bias awareness, security considerations

For each dimension, provide:
- A score from 0-100
- Specific feedback explaining the score
- Concrete suggestions for improvement

Calculate the overall score: (correctness * 0.40) + (clarity * 0.25) + (completeness * 0.25) + (safety * 0.10)

Respond in exact JSON format:
{
  "score": 85,
  "feedback": {
    "correctness": "The implementation correctly handles the basic case but misses edge case X...",
    "clarity": "Well-structured but variable names could be more descriptive...",
    "completeness": "Covers requirements A and B but ignores requirement C...",
    "safety": "No safety concerns identified..."
  },
  "overall": "Good effort with one critical edge case to fix.",
  "suggestions": ["Add input validation for empty strings", "Include error handling"]
}

Task-Specific Prompts

Customize the critic based on the output type:

For code reviews:

Focus on: correctness, edge cases, error handling, code quality, security vulnerabilities.

For written content:

Focus on: argument coherence, evidence support, audience appropriateness, factual claims.

For data analysis:

Focus on: methodology soundness, statistical validity, conclusion support, bias detection.

Implementation

Scripts

scripts/critic.js - Main critic implementation that:

  • Accepts input JSON via stdin
  • Constructs appropriate critique prompt
  • Calls LLM with structured output enforcement
  • Validates and normalizes output
  • Returns JSON result

scripts/score-helper.js - Utility for computing final score and thresholds

References

  • references/patterns.md - Usage patterns and examples
  • references/configuration.md - Full configuration reference

Integration Guide

Single Critic Call

const result = await skill.run('critic-agent', {
  task: originalPrompt,
  agentOutput: generatedContent,
  context: { requirements: [...], constraints: [...] }
});

if (result.score >= 70) {
  console.log('Passed:', result.overall);
} else {
  console.log('Needs work:', result.suggestions);
}

Retry Loop with Critic

async function generateWithQualityGate(task, maxAttempts = 3) {
  for (let attempt = 1; attempt <= maxAttempts; attempt++) {
    const output = await generateAgentResponse(task);

    const critique = await skill.run('critic-agent', {
      task,
      agentOutput: output,
      context: {}
    });

    if (critique.score >= 70) {
      return { output, critique };
    }

    if (attempt === maxAttempts) break;

    // Incorporate feedback in next attempt
    task = `${task}\
\
Previous feedback: ${critique.suggestions.join('; ')}`;
  }

  throw new Error('Failed to meet quality threshold after retries');
}

Parallel Critic Multi-Agent Workflow

Writer Agent → [Output] → Critic Agent → [Score + Feedback]
                                       ↓
                                   If score < threshold
                                       ↓
                              Reject + Send feedback to Writer
                                       ↓
                              Writer revises and resubmits

Fallback Behavior

If the critic agent fails (model unavailable, timeout, malformed response), the behavior depends on configuration:

ScenarioDefault BehaviorConfig Override
LLM API failurePass through original output with warning logonCriticError: "fail" to reject
Invalid JSON responseUse heuristic fallback scoring (simple keyword checks)onCriticError: "reject"
TimeoutTreat as score = 0 (fail)onCriticError: "pass" to auto-pass
Model not foundFallback to configured default modelN/A (auto-handled)

Configure fallback:

{
  "onCriticError": "pass" | "fail" | "reject",
  "fallbackModel": "openrouter/default-fallback"
}

Limitations

  • Critique quality depends on the underlying LLM's capability
  • Subjective dimensions (clarity) may vary between runs
  • Not suitable for real-time or streaming evaluation (requires complete output)
  • Cannot guarantee perfect detection of all safety issues
  • Scoring is indicative, not absolute truth

Best Practices

  1. Use as advisory: Critic suggestions should inform but not replace human judgment
  2. Calibrate thresholds: Adjust pass thresholds based on your quality requirements
  3. Review borderline cases: Scores 65-75 deserve human spot-check
  4. Log all critiques: Record feedback for continuous improvement
  5. Iterate on prompts: Customize critic prompts for your specific domain
  6. Combine multiple critics: For high-stakes outputs, use 2-3 different critic models

Future Enhancements

  • Multi-critic consensus (aggregate scores from multiple models)
  • Domain-specific rubrics (customize weights per task type)
  • Historical learning (store critiques to identify recurring issues)
  • Interactive critique (allow back-and-forth between writer and critic)
  • Automated remediation (auto-apply simple fixes from suggestions)

Troubleshooting

Critic returns low scores on everything

  • Check if requirements are clearly stated in context
  • Verify prompt template matches your output type
  • Try a more capable model

Scores inconsistent across runs

  • Temperature may be too high; set to 0 for deterministic evaluation
  • Add specific examples in the system prompt to anchor scoring

Critic hangs or times out

  • Increase timeout setting
  • Simplify lengthy outputs (critique focuses on key sections)
  • Use smaller, faster model for feedback generation

适合场景

01

调用多模型

02

代码和文本生成

03

Agent 推理流程

04

OpenRouter 模型接入

能力概览

能力 1

统一调用多种 LLM

能力 2

支持 Claude、Gemini、Kimi 等模型

能力 3

适合聊天、代码和推理任务

能力 4

可作为 Agent 模型调用入口

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

92.75%
按下载量换算2,732

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills