Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/smart-sourcing
Selects optimal sources for tool calls, balancing accuracy with token cost. Use before research tasks or when deciding whether a claim needs verification.
Passed 15 of 20 test cases with the skill, and 7 of 20 without it.
and 6 more in the full report
9 fixed8 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our compliance team needs a timeline of major Kubernetes release dates from 1.28 through 1.30 to check lifecycle support windows. Write a brief lifecycle table.
| Checked | Without skill | With skill |
|---|---|---|
| The lifecycle table attaches sourcing markers to the Kubernetes release dates. | Missed | Passed |
The instructions your model reads when the skill loads.
Intelligent sourcing that requires citations only when the cost is justified by the value of verification.
Full sourcing is prohibitively expensive (10-16x token increase). Smart sourcing targets high-value claims where verification materially improves accuracy.
| Claim Type | Example | Why Source |
|---|---|---|
| Version numbers | "Python 3.12 added..." | Versions change, easy to verify |
| Performance claims | "30% faster than..." | Quantitative claims need evidence |
| Security recommendations | "Use bcrypt for..." | Security advice must be current |
| API specifications | "The function accepts..." | APIs change between versions |
| Release dates | "Released in Q4 2025" | Factual, verifiable |
| Pricing/limits | "Free tier allows 1000 requests" | Business terms change |
| Deprecated features | "X was removed in version Y" | Breaking changes need verification |
| Claim Type | Example | Why No Source |
|---|---|---|
| General concepts | "Async improves concurrency" | Foundational knowledge |
| Code examples | Demonstrative snippets | Illustrative, not factual claims |
| Opinion/preference | "Consider using..." | Clearly framed as suggestion |
| Common knowledge | "Git tracks changes" | Universal understanding |
| Logical derivations | "Therefore, X implies Y" | Reasoning, not factual claim |
| Syntax | "Use def for functions" | Language documentation is stable |
Is this a factual claim?
├── No → No source needed
└── Yes → Would being wrong cause harm?
├── No (minor inconvenience) → No source needed
test cases passed, vs 7 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.