AI Skill Report Card
Researching With Verified Sources
Quick Start14 / 15
Query: "What's the latest version of the React framework?"
- Run a web search:
react latest version release notes - Pull URLs/snippets directly from search results (never type one from memory)
- Cross-check against a second source (e.g., npm registry page + official React blog)
- Answer with inline citations:
- React 19 was released in December 2024, adding Actions and the
usehook. React Blog - The npm registry confirms
react@19.0.0as the current stable tag. npm
- React 19 was released in December 2024, adding Actions and the
Recommendation▾
Add an example showing conflicting sources being surfaced explicitly, since that's a stated step but not demonstrated
Workflow14 / 15
Progress:
- Step 1: Classify the query — current/time-sensitive fact, static knowledge, or opinion/analysis
- Step 2: If current or fact-based, execute at least one targeted search
- Step 3: For complex/contentious topics, gather 2–3 independent sources
- Step 4: Extract only URLs explicitly present in tool results — never construct, guess, or "fix" a link
- Step 5: Write answer in bullet points, attaching
[Source Name](url)next to each claim it supports - Step 6: If sources conflict, surface the disagreement explicitly rather than picking one silently
- Step 7: If search returns nothing usable, say so plainly and stop
Search query construction:
- Use specific, targeted terms (product names, version numbers, dates) rather than vague phrasing
- Run follow-up searches if the first pass is ambiguous or too broad
- For contentious/political/medical/financial topics, deliberately search for multiple viewpoints (e.g., add site-specific or "criticism"/"analysis" qualifiers)
Source hierarchy (prefer higher):
- Official documentation / primary source (vendor docs, government data, original research)
- Reputable news outlets / established industry publications
- Secondary analysis or aggregator sites
- Forums, social media, unverified blogs (use only to corroborate, never as sole source)
Recommendation▾
Include guidance on how many searches is 'enough' before declaring no usable results, to reduce ambiguity
Examples17 / 20
Example 1: Input: "Is there a recall on [specific car model] right now?" Output:
- Searches
[model] recall 2024 NHTSA - Finds NHTSA database entry and a manufacturer press release
- Response: "Yes — a recall was issued for the fuel pump assembly. NHTSA The manufacturer's statement confirms affected VIN ranges. Manufacturer Press Release"
Example 2: Input: "What do experts think about a new, obscure economic theory?" Output:
- Searches the theory name + "criticism" and + "analysis"
- Finds only one low-quality forum thread, no academic or news coverage
- Response: "I could not find verified live data on this. The only results were unverified forum discussions, which don't meet sourcing standards for a factual claim."
Example 3: Input: "What year did World War II end?" Output: Static, well-established historical fact — answer directly without forcing a search: "World War II ended in 1945." (A search may still be run if the user wants a cited source, but it's not mandatory for settled historical facts.)
Recommendation▾
Expand the source hierarchy section with a brief example of ranking sources for a real query to make the framework more concrete
Best Practices
- Attach citations directly beside the specific claim, not bundled in a footnote at the end
- When sources disagree, present both: "Source A reports X A, while Source B states Y B."
- Prefer the most recent source when timeliness matters; note publication dates explicitly for anything date-sensitive
- Keep summaries neutral — report what sources say, don't editorialize
- Use bullet points and short paragraphs for scannability
Common Pitfalls
- Never invent, autocomplete, or "clean up" a URL — only use exactly what the search tool returned
- Never present a single forum post or unverified blog as sufficient evidence for a contentious claim
- Don't skip searching just because the topic "feels" familiar — if it's time-sensitive, verify anyway
- Don't bury a lack of results behind a vague or hedged answer — state plainly that nothing verified was found
- Don't cite a source for a claim it doesn't actually support — match citation to specific sentence, not general topic