docs-claim-check
De la autor
Fact-check public docs, verify a README against a repo, audit release notes, or find stale/overstated claims using supplied evidence. Advisory findings only. Not for standalone code/security review, fixes or command execution; use it only for eligible claims in mixed requests. When using this skill, never edit files and run no commands except to load its SKILL.md at the exact host-catalog path. Use an already supplied full body without rereading. Follow the native loader or, for command-backed loading, one safely quoted literal cat of that path; no other file, shell expansion, chaining, redirection or pipeline. Resolve aliases only from host-provided mappings, without commands. If the path is unresolved or loading fails, is denied or finishes incomplete, stop and request full instructions; do not probe, retry, use shell paging or elevate. The command exception never covers target/evidence reads. Disclose loading and its outcome, including failure; a prohibited attempt invalidates the assessment.
Instalare
npx skills add kyungseo/skillstead --skill docs-claim-check -a claude-code
Se instalează în .claude/skills/docs-claim-check/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 83
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- verifying-claimsoaustegard/claude-skillsCheck that a document's claims about code are actually true by reading the prose, the code, and the tests and reporting (or fixing) where they disagree. Use whenever the user wants to verify a README, guide, spec, or docstring still matches the code; whenever they mention documentation drift, doc-code sync, "is this still accurate", stale docs, or keeping docs/tests/code consistent; before publishing or merging a docs change; or as a periodic doc-accuracy sweep. The agent reads the prose's meaning directly — there is no claim-comment DSL to maintain. Pairs with TDD — the test suite is the deterministic behavioral gate, this skill is the semantic prose-vs-reality review.Testare★ 154
- ai-audit-docsarcasilesgroup/ai-engineeringAudits documentation files against actual repo state. Detects dead references (links to nonexistent files/URLs), false claims (doc says feature X exists but the code doesn't), outdated version numbers, and references to commands that don't exist. Input: path to docs dir or specific files (defaults to docs/ README.md AGENTS.md). Output: ranked markdown table of findings with severity and location. Report-only, NO auto-fix. Trigger phrases: "audit docs", "check documentation", "verify docs", "docs review", "documentation audit".Planificare★ 61
- skill-checkclaude-world/director-mode-liteValidate skill/command file format and structure. Use after creating or editing a skill, before committing skill changes, or when a skill fails to load or trigger.Redactare★ 80
- docs-guardamElnagdy/guard-skillsReview generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.Testare★ 1.3K
- microsoft-docssandbaseai/sandbase-skillsResearch and evaluate microsoft docs with current authoritative sources, provenance, and explicit evidence gaps. Use when the user asks for microsoft docs findings or verification.Știință★ 201
- docs-auditorInfrasity-Labs/dev-gtm-claude-skillsAudits any developer documentation site across 33 checks in 7 categories and produces a scored report (out of 100) with Pass / Warn / Fail status per check. Use this skill whenever a user provides a docs URL and asks to audit it, review it, score it, check its quality, or evaluate it for AI discoverability, SEO, structure, content, or completeness. Also trigger when the user says "run a docs audit", "audit these docs", "check this documentation", "how good are the docs for X", or pastes a docs URL with any evaluative intent. Always use this skill — do not attempt a freeform docs review without following this structured workflow.Marketing★ 143
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te