Terminal
Terminal/Skill
Looks up library docs, issues, and release notes to answer coding questions with evidence for your library version.
By Tavily
Works with
npx skills add tavily-ai/use-case-skills --skill developer-atlasAnswer the coding question with evidence that applies to the user's version and environment. Use Tavily to discover official docs, repository discussions, changes, and releases, then read the sources needed to verify the answer. This workflow uses general web search; it does not assume a dedicated code index or complete repository coverage.
tvly search --help, tvly extract --help), or linked REST contract before selecting optional parameters. See tool selection and runnable examples when choosing an interface or handling unsupported options. Companion endpoint skills from tavily-ai/skills cover broader setup and endpoint usage when installed; they are not required to follow the examples here.| Question | First move | What establishes the answer |
|---|---|---|
| Exact error | Search the sanitized error and library; if needed, remove variable paths, line numbers, and IDs and retry once. | Matching conditions in a report, maintainer explanation, or relevant source. A similar message alone does not establish the cause. |
| How to use an API | Search the full short question with library and version; prefer official versioned docs. | The applicable signature, defaults, example, and constraints. |
| Known bug or regression | Find the issue, then the linked fix, release notes, and applicable tag. | Whether the fix actually shipped in the user's version, and whether it was reverted or requires a flag. |
| Changed contract or migration | Read both versions' docs and the migration guide or change. | The exact before/after behavior and the required user action. |
| Version-specific behavior | Inspect the provided version or lockfile, then retrieve that version's docs, tagged source, or releases. | Evidence tied to that version, not an undated page or current default branch. |
| Compare libraries | Search each library's official docs for the requested criteria, then supplement with relevant external experience. | Separate documented capabilities, measured results, and opinion; do not treat anecdotes as benchmarks. |
owner/repo. include_domains=["github.com"] filters a host, not a repository. Verify the returned URL's owner and repository; query text and site: hints are not guaranteed exact filters.answer help discovery; they are not proof of a release or API contract. If returned raw_content already establishes the claim, avoid fetching it again.query and chunks_per_source, or read the canonical full page through an available read-only tool. Do not assume even a full-page extraction contains all dynamic comments or diffs.results and failed_results; account for requested URLs missing from either collection. A successful request can still have incomplete coverage.indexed flags or per-type coverage contract; do not invent them. Follow any warnings or partial-result indicators the available interface actually returns.Retry-After or short backoff. If the server requests a long wait, report it. Stop on invalid credentials, exhausted quota, or a keyless cap; report the required login/reset time without changing credentials, buying credits, or switching identities.Lead with the answer or likely explanation, then include only what the question needs:
For manual validation, the source repository includes an isolated Codex discovery guide and test cases.