Help us improve
Share bugs, ideas, or general feedback.
From skills-toolkit
Template for building verifiable ground truth skills with structures for definitions, facts, metrics, and validation criteria. Auto-invokes on requests for skill templates or validation frameworks.
npx claudepluginhub youngleadersdottech/young-leaders-tech-marketplace --plugin skills-toolkitHow this skill is triggered — by the user, by Claude, or both
Slash command
/skills-toolkit:ground-truth-templateThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This template guides the creation of ground truth skills - verifiable, canonical reference documentation that provides definitive facts, definitions, and validation criteria. Replace all `[PLACEHOLDER]` values with actual verified information.
Verifies epistemic quality of documents pre-RAG ingestion, producing Clarity-Gated Documents (CGD) and validating Source of Truth (SOT) files to prevent LLM hallucination risks.
Validates SKILL.md files against Anthropic guidelines and the agentskills specification with structural, semantic, and security checks.
Guides creating, editing, and verifying skills using a TDD cycle: write test scenarios, watch agents fail, write skill, verify compliance, refactor loopholes.
Share bugs, ideas, or general feedback.
This template guides the creation of ground truth skills - verifiable, canonical reference documentation that provides definitive facts, definitions, and validation criteria. Replace all [PLACEHOLDER] values with actual verified information.
---
name: [project]-[domain]-ground-truth
description: Ground truth documentation for [PROJECT_NAME] [DOMAIN] providing canonical definitions, verified facts, and validation criteria. Auto-invoke when user discusses [TOPIC_1], [TOPIC_2], or validates [VALIDATION_SCENARIO]. Do NOT load for general [DOMAIN] discussions without [PROJECT_NAME] context.
allowed-tools: []
version: 1.0.0
category: Ground Truth
tags: [[project], [domain], reference, validation]
source: [CANONICAL_SOURCE_URL_OR_LOCATION]
verified-date: [YYYY-MM-DD]
next-review: [YYYY-MM-DD]
---
Description Engineering Guidance:
✅ DO include:
❌ DON'T use:
Example Good Description:
Ground truth documentation for Phoenix payment processing providing canonical transaction states, error codes, and retry policies. Auto-invoke when user discusses payment flows, error handling, or validates transaction logic. Do NOT load for general payment discussions outside Phoenix.
Purpose: Single source of truth for terms, concepts, and classifications
[TERM_NAME]Definition: [PRECISE_CANONICAL_DEFINITION]
Source: [AUTHORITATIVE_SOURCE] (verified [DATE])
Related Terms:
[RELATED_TERM_1]: [BRIEF_DEFINITION][RELATED_TERM_2]: [BRIEF_DEFINITION]Anti-Patterns (What this is NOT):
[COMMON_MISCONCEPTION_1][COMMON_MISCONCEPTION_2]Example Usage:
[CODE_EXAMPLE_OR_REAL_WORLD_USAGE]
Purpose: Quantifiable, verifiable information with sources
[CATEGORY_NAME]| Metric/Fact | Value | Source | Verified Date |
|---|---|---|---|
[METRIC_1] | [VALUE] [UNIT] | [SOURCE_LINK] | [YYYY-MM-DD] |
[METRIC_2] | [VALUE] [UNIT] | [SOURCE_LINK] | [YYYY-MM-DD] |
[METRIC_3] | [VALUE] [UNIT] | [SOURCE_LINK] | [YYYY-MM-DD] |
Calculation Method (if applicable):
[FORMULA_OR_CALCULATION_METHODOLOGY]
Freshness Policy:
[DAILY/WEEKLY/MONTHLY/QUARTERLY][TIME_PERIOD] requires reverification[YYYY-MM-DD]Purpose: Definitive workflows, state machines, and process flows
[PROCESS_NAME]States:
[STATE_1] → [STATE_2] → [STATE_3] → [FINAL_STATE]
State Transitions:
| From State | Event/Trigger | To State | Constraints |
|---|---|---|---|
[STATE_1] | [EVENT_1] | [STATE_2] | [CONDITION] |
[STATE_2] | [EVENT_2] | [STATE_3] | [CONDITION] |
[STATE_3] | [EVENT_3] | [FINAL_STATE] | [CONDITION] |
Error States:
[ERROR_STATE_1]: Triggered by [ERROR_CONDITION] → Recovery: [RECOVERY_PROCESS][ERROR_STATE_2]: Triggered by [ERROR_CONDITION] → Recovery: [RECOVERY_PROCESS]Source: [TECHNICAL_SPEC_LINK_OR_DOC] (version [VERSION], dated [DATE])
Purpose: Definitive rules for validating implementations, data, or behaviors
[DOMAIN_NAME]Required Properties:
- Property: [PROPERTY_1]
Type: [DATA_TYPE]
Constraints: [VALIDATION_RULES]
Example Valid: [VALID_EXAMPLE]
Example Invalid: [INVALID_EXAMPLE]
- Property: [PROPERTY_2]
Type: [DATA_TYPE]
Constraints: [VALIDATION_RULES]
Example Valid: [VALID_EXAMPLE]
Example Invalid: [INVALID_EXAMPLE]
Business Rules:
[RULE_1]: [DETAILED_DESCRIPTION]
[EXAMPLE][COUNTER_EXAMPLE][RULE_2]: [DETAILED_DESCRIPTION]
[EXAMPLE][COUNTER_EXAMPLE]Validation Test Cases (Reference):
Test ID: [TEST_ID]
Description: [WHAT_IS_BEING_TESTED]
Input: [TEST_INPUT]
Expected Output: [EXPECTED_RESULT]
Source: [TEST_SPEC_LOCATION]
Purpose: Canonical error taxonomy with meanings and resolutions
[CATEGORY]| Error Code | Error Name | Meaning | Resolution | Severity |
|---|---|---|---|---|
[CODE_1] | [NAME] | [DESCRIPTION] | [FIX_STEPS] | [CRITICAL/HIGH/MEDIUM/LOW] |
[CODE_2] | [NAME] | [DESCRIPTION] | [FIX_STEPS] | [CRITICAL/HIGH/MEDIUM/LOW] |
Error Code Format:
Pattern: [REGEX_PATTERN_OR_FORMAT]
Example: [EXAMPLE_ERROR_CODE]
Purpose: Canonical lists, enumerations, and classification schemes
[ENUM_NAME]| Value | Display Name | Description | Deprecated? |
|---|---|---|---|
[VALUE_1] | [DISPLAY_1] | [DESCRIPTION] | No |
[VALUE_2] | [DISPLAY_2] | [DESCRIPTION] | No |
[VALUE_3] | [DISPLAY_3] | [DESCRIPTION] | ⚠️ Yes (since [DATE]) |
Source: [API_SPEC_OR_SCHEMA_LOCATION]
Before finalizing ground truth skill, verify:
Content Quality:
[PLACEHOLDERS] replaced with actual verified valuesSource Attribution:
Validation Quality:
Metadata & Tracking:
source field in frontmatter points to canonical documentationverified-date is currentnext-review date set based on freshness policyallowed-tools: [] set (ground truth is read-only reference)Security & Scope:
.claude/skills/projects/[name]/ground-truth/)Creating New Ground Truth Skill:
User: "Create a ground truth skill for Phoenix payment error codes"
Claude: [Loads this template skill, uses structure to create Phoenix-specific ground truth]
Validating Implementation:
User: "Is this transaction state valid according to ground truth?"
Claude: [Loads project ground truth skill, checks against canonical state definitions]
Do NOT Use This Template For:
Update Triggers:
Staleness Warning:
If next-review date has passed, skill should display:
⚠️ STALE GROUND TRUTH: Last verified [DATE], review overdue by [DAYS] days.
Please reverify before relying on this information.
Version Control:
version field using semantic versioning (1.0.0 → 1.1.0 for additions)Template Source: Phase 2 requirements + validation framework Template Version: 1.0.0 Last Updated: 2025-10-20 Validation: Ready for Phase 2 implementation