docs-claims-evidence-review

Use when reviewing README or docs truthfulness, recruiter-facing claims, security claims, production-readiness claims, evidence maps, or unsupported project…

Skill by priyanshuchawda

IndexedMIT★ 1

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/priyanshuchawda-docs-claims-evidence-review

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Use when reviewing README or docs truthfulness, recruiter-facing claims, security claims, production-readiness claims, evidence maps, or unsupported project claims.

Use cases: security

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/docs-claims-evidence-review

What's inside

Skill name: docs-claims-evidence-review
Description: Use when reviewing README or docs truthfulness, recruiter-facing claims, security claims, production-readiness claims, evidence maps, or unsupported project claims.
License: MIT
Metadata: internal: true
Instructions: 21 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Docs Claims Evidence Review

## Workflow

1. Extract strong claims from README and docs.
2. Classify claim strength: weak, moderate, or strong.
3. Map each claim to file, test, or documentation evidence.
4. Mark missing evidence explicitly.
5. 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.

From priyanshuchawda/codeaudit, MIT.

Signals

Stars: 1
Forks: 0
Open issues: 0
Last commit (this folder): May 4, 2026 (5 months ago)
Last release: May 4, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/priyanshuchawda/codeaudit
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from priyanshuchawda

Cite this page

docs-claims-evidence-review skill. Agent Mart. https://agentmart.dev/skills/priyanshuchawda-docs-claims-evidence-review (last updated 2026-10-24)