use-external-api
/use-external-api
Use a library, SDK, CLI or web API correctly by checking the installed version and real docs instead of relying on memory. Use this whenever code calls a third-party package or service, when you are unsure of a method or parameter name, or when an API call fails. It prevents invented methods and outdated usage.
- Author
- yaohuangguan ↗
- Repository
- agent-playbook ↗
- Licence
- MIT
- Last repository change
- 07.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use a library, SDK, CLI or web API correctly by checking the installed version and real docs instead of relying on memory. Use this whenever code calls a third-party package or service, when you are unsure of a method or parameter name, or when an API call fails. It prevents invented methods and outdated usage.
Original author description
Use a library, SDK, CLI or web API correctly by checking the installed version and real docs instead of relying on memory. Use this whenever code calls a third-party package or service, when you are unsure of a method or parameter name, or when an API call fails. It prevents invented methods and outdated usage.
How it works
- When to use
- Steps
- Adding a dependency
- Stop and ask when
- Common mistakes
- Report
SKILL.md preview
--- name: use-external-api description: Use a library, SDK, CLI or web API correctly by checking the installed version and real docs instead of relying on memory. Use this whenever code calls a third-party package or service, when you are unsure of a method or parameter name, or when an API call fails. It prevents invented methods and outdated usage. --- # Use an external API Your memory of an API may be wrong or out of date, and invented method names often look correct. The installed code and current docs are the truth. ## When to use Any time you call something you did not write, unless the same call already exists in this repository. ## Steps 1. **Find the existing usage.** Search this repository first, and copy how it creates clients, handles errors and sets timeouts. 2. **Find the exact version.** | Stack | Check | | --- | --- | | JavaScript | The lockfile, or `node_modules/<pkg>/package.json` | | Python | `pip show <pkg>` | | Go | `go.mod`, or `go list -m <module>` | | Rust | `Cargo.lock` | | Java | `mvn dependency:tree` | 3. **Read the source of truth.** In order of trust: 1. Types or source of the installed package 2. Official docs for that version 3. The official changelog or migration guide Blog posts and forum answers can show you where to look, but confirm with one of these. 4. **Confirm that each name exists.** Search the installed package for each method and parameter you plan to use. If you cannot find it, do not use it. 5. **Run a small check.** Try the call in a small script or test, using a sandbox or test key. Do not use production data or paid operations for this. 6. **Handle real conditions.** Check each of these: - Timeouts on every network call - Rate limits, and which errors can be retried - Pagination, so that you do not read only the first page - Idempotency keys for writes that may be retried - Partial failure, and a response in an unexpected shape 7. **Isolate the integration.** Keep calls to the service in one place, so that tests can stub the network and upgrades touch one file. 8. **Test it.** Stub at the network, with responses taken from real docs or real sandbox calls. Follow `write-tests`. 9. **Finish.** Follow `verify-and-report`, and state which docs or version you used. ## Adding a dependency Ask first if the task did not call for one. Check that it is maintained, its license suits the project, and the standard library or an existing dependency cannot do the job. Confirm the exact package name from its official source, because similar names can be malicious. Pin it with the lockfile. ## Stop and ask when - The call needs real credentials you do not have. - The call costs money, sends messages or changes real data. - Docs and installed code disagree, and you cannot tell which is right. ## Common mistakes | Tempting move | Why it fails | Do this instead | | --- | --- | --- | | Write the call from memory | Names and defaults change | Check the installed version | | Retry on any error | A repeated write can duplicate an effect | Retry only safe errors | | Read only the first page | Silently loses data | Follow pagination | | Use `latest` | Builds change without notice | Pin the version | | Fake a response from your imagination | The test passes and production fails | Base it on a real response | | Put an API key in the code | It leaks through history | Read it from the environment | ## Report ```markdown Package or API: <name, version> Source checked: <installed types or docs URL> Check run: <what you called, and the result> Handles: <timeouts, retries, pagination, idempotency> Not verified: <anything not exercised for real> ```
Versions
The database has no other skills named use-external-api.
Database snapshot: 13.11.2026 · package version 3442c3b5831d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90library-docs-lookup
When writing code against an external library, framework, SDK, or API, look up its CURRENT documentation with the context7 MCP tools instead of relying on memory. Use whenever you import/call a third-party package or hit an unfamiliar or fast-moving API. - 100get-api-docs
Use this skill when you need documentation for a third-party library, SDK, or API before writing code that uses it — for example, "use the OpenAI API", "call the Stripe API", "use the Anthropic SDK", "query Pinecone", or any time the user asks you to write code against an… - 100find-docs
Retrieves up-to-date documentation, API references and code examples for any developer technology. Use when the user asks about, or you need docs for, a specific library, framework, SDK, CLI tool or cloud service - even well-known ones, as training data may be outdated. Prefer… - 100get-api-docs
Use this skill when you need documentation for a third-party library, SDK, or API before writing code that uses it — for example, "use the OpenAI API", "call the Stripe API", "use the Anthropic SDK", "query Pinecone", or any time the user asks you to write code against an… - 96read-docs
Read current or version-specific official documentation for libraries, frameworks, SDKs and APIs instead of relying on memory, which may be outdated. Use for setup and configuration, code examples using a named library, migrations, compatibility questions or library-specific… - 100ctxhub-get-api-docs
Use this skill to get documentation for third-party APIs, SDKs, or libraries before writing code that uses them, so you have the latest accurate docs instead of stale training data. Triggers: any task like "use the OpenAI API", "call the Stripe API", "use the Anthropic SDK",…