validate-knowledge
From the author
Prove that a knowledge base actually works before trusting it — after building or adopting docs, a knowledge graph, or a wiki, verify it can orient a fresh agent and resist false premises. Use at the end of an adoption, after a large docs change, or before relying on the graph to route work. Two methods: clean-context test agents answering known-answer and adversarial questions, and enforcement tests that plant a violation and confirm the linter catches it. A smoke test proves code runs; this proves the knowledge is correct, navigable, and honest.
Install
npx skills add llopresto87/Cypress --skill validate-knowledge -a claude-code
Installs to .claude/skills/validate-knowledge/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- verification-methodologymagnus919/agent-skillsVerify work against explicit criteria using direct, source-faithful evidence, reproducible checks, and clear verdicts. Use before declaring an artifact, implementation, or claim complete; do not use for exploratory research without pass/fail criteria.Science★ 147
- validate-markettamdogood/builder-essential-skillsRun an honest market-fit and viability audit of any project or idea and produce a decision doc, not code. Use when someone asks "is this viable as a business", "audit the market fit", "make the case and compare to competitors", "should I apply to YC or bootstrap", or wants to validate a project, product, or market before investing more time. Gathers verifiable traction data first, researches the competitive field, gets an independent cold read, writes a doc with pre-committed pass/middle/kill criteria and a concrete week-1 assignment, then hardens it with an adversarial review loop.Finance★ 225
- behavior-validationthiientv/godmodeValidates a running application, CLI, API, service, or generated artifact as a user or operator against a prewritten observable behavior contract while remaining source-blind. Use for acceptance checks, runtime proof, anti-fake probes, release smoke tests, or an independent companion to code review. Not for source-quality findings, root-cause diagnosis, or visual design judgment outside the contract.Testing★ 99
- validate-dataanthropics/knowledge-work-pluginsQA an analysis before sharing -- methodology, accuracy, and bias checks. Use when reviewing an analysis before a stakeholder presentation, spot-checking calculations and aggregation logic, verifying a SQL query's results look right, or assessing whether conclusions are actually supported by the data.OfficialTesting★ 32.5K
- validatehashgraph-online/awesome-codex-pluginsFreshly judge whether a finished change and its claims meet original acceptance: PASS, FAIL or NOT_PROVEN. Use when: asked for a go/no-go, sign-off or independent verdict.Other★ 1.4K
- verification-before-completionforyourhealth111-pixel/Vibe-SkillsCompletion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready. Requires fresh verification output before success claims. Do not use for root-cause debugging, TDD implementation, test-report packaging, or review-feedback triage.Testing★ 3.8K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in