verify-primary-sources

Fetch and read primary documentation to verify architectural, API, or security claims.

4|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/jcdendrite/claude-config --skill verify-primary-sources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-primary-sources
Source: https://github.com/jcdendrite/claude-config/tree/main/claude/.claude/skills/verify-primary-sources
Command: npx skills add https://github.com/jcdendrite/claude-config --skill verify-primary-sources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents confident-but-wrong migrations, designs, and security/API decisions caused by relying on secondary summaries that omit critical scope like version, configuration, or migration path.

Core Features & Use Cases

  • Secondary sources as leads: Treat agent claims, blog posts, and paraphrased “docs say” statements as pointers that must be validated against the primary material.
  • Primary source verification: Fetch the vendor/project’s official documentation, changelog/release notes/migration guide, spec/RFC, or relevant source code to confirm the claim in context.
  • Scope-preserving conclusions: Ensure the final recommendation carries the correct qualifiers (which version/mode/API surface/migration path) rather than using an unscoped interpretation.
  • First-pass correction: Forces verification on the first research cycle so the next step is not “go fetch the primary source” after a mismatch is discovered.

Quick Start

When you are about to make a design, migration, or security-related decision from a cited claim, ask me to verify it by fetching and reading the primary source and summarizing what it actually supports in the correct scope.

Frequently Asked Questions about verify-primary-sources

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify API migration claims from secondary sources?

Verify API migration claims by treating secondary sources as leads, fetching official vendor documentation, and reading the primary source to confirm behavior changes with the correct version scope.

Why does relying on agent summaries cause security decisions to fail?

Relying on agent summaries causes security decisions to fail because they often omit critical scope like configuration modes or version support, leading to confident but wrong architectural implementations.

What is primary source verification for dependency validation?

Primary source verification for dependency validation is the process of fetching official changelogs, release notes, or specs to confirm relayed claims instead of trusting paraphrased documentation summaries.

How do I preserve scope when checking documentation for behavior changes?

Preserve scope when checking documentation by reading the surrounding context of the primary source to ensure final recommendations carry correct qualifiers regarding version, API surface, and migration path.

When do I need to fetch primary documentation during a research workflow?

Fetch primary documentation during a research workflow when you are about to make a design, migration, or security-related decision from a cited claim that requires validation before acting.

What should I do if the primary source cannot be found during documentation verification?

If the primary source cannot be found during documentation verification, you must clearly flag the uncertainty rather than proceeding with an unscoped interpretation of the secondary material.