What problem does it solve? Evaluating whether a source, repository, or news item is trustworthy usually means each caller hardcodes its own ad-hoc criteria. This Skill provides a shared, data-shaped contract — domain profiles with fixed sections for credibility axes, verification procedures, verdict vocabulary, and memory homes — so any evaluation workflow can route to a consistent, reusable standard. ## Core Features & Use Cases - Domain Profile Contract: Every profile answers six fixed sections (primary-source definition, CRAAP axis weights, staleness horizon, verification procedure, verdict vocabulary, memory home), and adding a new domain requires only one conforming profile file. - Shared Vocabulary and Procedures: A central reference defines the five CRAAP credibility axes and three verification procedures (signal-bundle liveness, SIFT/lateral reading, evidence-audit) that profiles cite rather than restate. - Record-Keeping Doctrine: Six binding rules (R1-R6) govern how evaluation records are stored — append-only logs, progressive disclosure, staleness re-verification, and provenance chains. - Use Case: When vetting an external GitHub repo for adoption, route to the external-repos profile to apply code-over-README authority weighting, the duplicate-detection gate, and the Steal/Adapt/Monitor/Skip verdict vocabulary. ## Quick Start Use the evaluation-domains skill to vet this external repository and tell me which credibility profile and verification procedure apply.
