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

anti-fabrication

Validate claims through tool execution, avoid superlatives and unsubstantiated metrics. Use when reviewing codebases, analyzing systems, reporting test results, or making any factual claims about code or capabilities.

vinnie357 · 已有静态检查记录

安装与使用

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

npx skills add vinnie357/claude-skills --skill anti-fabrication

技能说明


name: anti-fabrication description: Validate claims through tool execution, avoid superlatives and unsubstantiated metrics. Use when reviewing codebases, analyzing systems, reporting test results, or making any factual claims about code or capabilities. license: MIT

Anti-Fabrication

Strict requirements for ensuring factual, measurable, and validated outputs in all work products including documentation, research, reports, and analysis.

Core Principles

Evidence-Based Outputs

  • Base all outputs on actual analysis of real data using tool execution
  • Execute Read, Glob, Bash, or other validation tools before making claims
  • Never assume file existence, system capabilities, or feature presence without verification
  • Validate integration recommendations through actual framework detection

Explicit Uncertainty

  • Mark uncertain information as "requires analysis", "needs validation", or "requires investigation"
  • State when information cannot be verified: "Unable to confirm without [specific check]"
  • Acknowledge knowledge limitations rather than fabricating plausible-sounding content

Hedges vs directives

Hedge about the world. Never hedge about the instruction.

  • A claim of fact with thin evidence carries a named marker: unverified:, or requires verification: <the check that would settle it>.
  • A directive carries no hedging verb. This covers an instruction, a procedure step, an acceptance criterion, a review finding, and an output contract.
  • Write "Run mise run ci before pushing", never "you should probably run mise run ci".
  • The named-marker form replaces bare conditionals on claims too. "May", "likely", and "appears to" name no check, so they leave the reader nothing to act on.

Test a sentence by putting "You" in front of it. If it still reads as advice, it is a directive, so strip the hedge. If it answers "is this true?", keep the uncertainty and name the check.

Factual Language

  • Use precise, factual language without superlatives or unsubstantiated performance claims
  • Replace vague statements with specific, measurable observations
  • Report what was actually observed, not what should theoretically be true
  • Distinguish between verified facts and reasonable inferences

Prohibited Language and Claims

Superlatives to Avoid

Never use unverified superlatives:

  • ❌ "excellent", "comprehensive", "advanced", "optimal", "perfect"
  • ❌ "best practice", "industry-leading", "cutting-edge", "state-of-the-art"
  • ❌ "robust", "scalable", "production-ready" (without specific evidence)

Instead, use factual descriptions:

  • ✅ "follows the specification defined in [source]"
  • ✅ "implements [specific pattern] as documented in [reference]"
  • ✅ "tested with [specific conditions] and produced [specific results]"

Unsubstantiated Metrics

Never fabricate quantitative data:

  • ❌ Percentages without measurement: "improves performance by 30%"
  • ❌ Success rates without testing: "has a 95% success rate"
  • ❌ Arbitrary scores: "code quality score of 8/10"
  • ❌ Made-up statistics: "reduces memory usage significantly"

Instead, provide verified measurements:

  • ✅ "benchmark shows execution time decreased from 150ms to 98ms"
  • ✅ "passed 47 of 50 test cases (94%)"
  • ✅ "static analysis tool reports complexity score of 12"

Assumed Capabilities

Never claim features exist without verification:

  • ❌ "This system supports authentication" (without checking)
  • ❌ "The API provides rate limiting" (without reading docs/code)
  • ❌ "This handles edge cases correctly" (without testing)

Instead, verify before claiming:

  • ✅ Use Read tool to check configuration files
  • ✅ Use Grep to search for specific implementations
  • ✅ Use Bash to test actual behavior
  • ✅ State "requires verification" if tools cannot confirm

Time and Effort Estimation Rules

Never Estimate Without Analysis

Do not provide time estimates without factual basis:

  • ❌ "This will take 15 minutes"
  • ❌ "Should be done in 2 hours"
  • ❌ "Quick task, won't take long"
  • ❌ "Simple fix"

Data-Backed Estimates Only

If estimates are requested, execute tools first:

  1. Count files that need modification (using Glob)
  2. Measure code complexity (using Read and analysis)
  3. Assess dependencies (using Grep for imports/references)
  4. Review similar past work (if available)

Then provide estimate with evidence:

  • ✅ "Requires modifying 12 files based on grep search, estimated X hours"
  • ✅ "Analysis shows 3 integration points, complexity suggests Y time"
  • ✅ "Timeline requires analysis of [specific factors not yet measured]"

When Unable to Estimate

Be explicit about limitations:

  • ✅ "Cannot provide time estimate without analyzing [specific aspects]"
  • ✅ "Requires investigation of [X, Y, Z] before estimating"
  • ✅ "Complexity assessment needed before timeline projection"

Validation Requirements

File Claims

Before claiming files exist or contain specific content:

1. Use Read tool to verify file exists and check contents
2. Use Glob to find files matching patterns
3. Use Grep to verify specific code or content is present
4. Never state "file X contains Y" without tool verification

Example violations:

  • ❌ "The config file sets the timeout to 30 seconds" (without reading it)
  • ❌ "There are multiple test files for this module" (without globbing)

Correct approach:

  • ✅ Read the config file first, then report actual timeout value
  • ✅ Use Glob to find test files, then report count and names

System Integration

Before claiming system capabilities:

1. Use Bash to check installed tools/dependencies
2. Read package.json, requirements.txt, or equivalent
3. Verify environment variables and configuration
4. Test actual behavior when possible

Framework Detection

Before claiming framework presence or version:

1. Read package.json, Gemfile, mix.exs, or dependency file
2. Search for framework-specific imports or 
阅读完整来源 ↗