research-source-evaluation

When searching for authoritative sources for skills or validating existing source links.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill provides a comprehensive framework for identifying and validating authoritative technical sources. It establishes a five-tier credibility system—ranging from official documentation and RFCs to community forums—ensuring that information is sourced from the most reliable origins. By utilizing advanced search strategies and a rigorous validation checklist (covering recency, domain authority, and versioning), the skill helps users eliminate outdated or unverified data, significantly enhancing the accuracy and integrity of technical research.

Use Cases

  • Technical Documentation Discovery: Finding the most recent and official documentation for specific software versions to avoid using deprecated features or outdated APIs.
  • Fact-Checking Technical Claims: Verifying the accuracy of blog posts, tutorials, or AI-generated snippets against Tier 1 sources like W3C specifications or official GitHub repositories.
  • Knowledge Base Maintenance: Auditing and validating existing resource links within a company's internal documentation to ensure they remain relevant and authoritative.
  • Deep-Dive Research: Using optimized search operators and domain-specific filters to conduct thorough research on emerging technologies while filtering out low-quality content.
nameresearch-source-evaluation
descriptionWhen searching for authoritative sources for skills or validating existing source links.
version1.0.0
tokens~400
confidencehigh
- https//www.w3.org/TR/
last_validated2025-01-10
next_review2025-01-24
tags[research, sources, validation, skills]

When to Use

When searching for authoritative sources for skills or validating existing source links.

Patterns

Source Tiers (Credibility)

Tier 1 (Highest):
  - Official docs (react.dev, supabase.com/docs)
  - RFCs, W3C specs
  - GitHub source code

Tier 2:
  - Official blogs (vercel.com/blog)
  - Release notes, changelogs
  - Core team members' posts

Tier 3:
  - Reputable tech companies (AWS, Google, etc.)
  - Well-known authors (Kent C. Dodds, Dan Abramov)

Tier 4:
  - Stack Overflow (high votes, recent)
  - GitHub issues (official repos)

Tier 5 (Lowest):
  - Personal blogs, tutorials
  - Medium articles (verify author)

Search Strategy

# Primary search (official)
"[technology] site:docs.*.com OR site:*.dev"

# Version-specific
"[technology] [version] documentation"

# Latest practices
"[technology] best practices 2024 2025"

# Breaking changes
"[technology] migration guide OR breaking changes"

Source Validation Checklist

✅ Domain is official project domain
✅ Content dated within 12 months
✅ Author is maintainer/team member
✅ Links to source code or spec
✅ No outdated version warnings

Anti-Patterns

  • Using StackOverflow answers >2 years old
  • Blog posts without checking official docs
  • Ignoring version numbers in examples
  • Trusting AI-generated content without verification

Verification Checklist

  • Source is Tier 1-3
  • Content is recent (<12 months)
  • No deprecation warnings on page
  • Multiple sources agree on pattern