docs-claims-evidence-review
Use when reviewing README or docs truthfulness, recruiter-facing claims, security claims, production-readiness claims, evidence maps, or unsupported project claims.
- License 许可
- MIT
- 最近更新
- 2026-05-04
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- docs-claims-evidence-review
- metadata
- { "internal": true }
- description
- Use when reviewing README or docs truthfulness, recruiter-facing claims, security claims, production-readiness claims, evidence maps, or unsupported project claims.
03 SKILL.md 正文
Docs Claims Evidence Review
Workflow
- Extract strong claims from README and docs.
- Classify claim strength: weak, moderate, or strong.
- Map each claim to file, test, or documentation evidence.
- Mark missing evidence explicitly.
- Recommend keep, weaken, remove, or add evidence.
Strong Claims
Never allow unsupported claims such as secure, production-ready, enterprise-grade, fully tested, scalable, robust, or battle-tested. Docs should stay positive but truthful.
Evidence Examples
- Security: middleware, auth checks, rate limits, headers, validation, threat model, security tests.
- Production-ready: deployment docs, env docs, smoke tests, error handling, observability.
- Fully tested: test framework, meaningful test files, coverage or test command evidence.
04 同仓库更多 Skills
dangerous-helper
Unsafe fixture skill for supply-chain audit tests.
benign-helper
Safe fixture skill for supply-chain audit tests.
skill-supply-chain-auditor
Use when reviewing installed skills, adding third-party skills, hardening agent workflows, checking skill correctness, removing duplicate skills, or investigating supply-chain, prompt-injection, secret-leakage, dependency-install, webhook, destructive-shell, manifest-quality, or resource-discovery risks.
refactor-with-tests
Use when splitting files, improving architecture, reducing duplication, changing internals, or preserving behavior through focused tests during refactors.
python-mcp-server-quality
Use when creating, auditing, or improving Python MCP servers, FastMCP tools, resources, prompts, stdio transports, streamable HTTP transports, MCP Inspector setup, or Python tool schemas.
python-backend-quality
Use when reviewing, creating, or improving Python services, CLIs, libraries, FastAPI, Django, Flask, pytest, uv, pyproject, typing, Pydantic, SQLAlchemy, async code, packaging, or deployment.