Api Integration
CheckedHelps with API, integration as part of agent workflows workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add autumnsgrove/lattice --skill api-integration -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
autumnsgrove
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Only contacts known or declared hosts: api.github.com.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
api.github.comsource hostNo obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned autumnsgrove/groveengine at edebdc71a7.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- edebdc71a7
- Scanned
- 1 file, 276 lines
About this skill
What it does
This skill assists AI agents with integrating external APIs into their workflows. It provides tools and guidance for building API clients, handling authentication (using a secrets.json file), implementing rate limiting, caching responses to reduce redundant requests, and gracefully managing errors through retries and backoff strategies. The skill includes example code snippets in both Python and Bash.
When to use it
- You need to access data or functionality from an external API within your agent's workflow (e.g., fetching weather data, interacting with a GitHub repository).
- Your agent needs to authenticate with an API using keys stored securely.
- The API you are integrating has rate limits that must be respected.
- You want to improve the efficiency of your agent by caching frequently accessed API responses.
Key capabilities
- API Authentication: Securely loads and uses API keys from a
secrets.jsonfile, preventing them from being committed directly into code. Supports environment variables as fallback for API keys. - Rate Limiting Handling: Includes retry mechanisms with exponential backoff to handle rate limits gracefully.
- Error Handling: Provides example error handling for HTTP errors (including 401 Unauthorized and 429 Rate Limited).
- Caching: Encourages caching of API responses to reduce redundant requests.
- Example Code: Offers sample code in Python (with retry functionality) and Bash for making basic GET requests with authentication.
Example prompts
- "Use the OpenWeatherMap API to get the current temperature in London."
- "Fetch my GitHub profile information using the provided API key."
- "Make a request to [API endpoint] and handle any rate limiting errors."
Tips & gotchas
- Secrets Management: Always store your API keys securely within the
secrets.jsonfile and never commit it to version control. - Rate Limits: Be mindful of API rate limits and implement appropriate backoff strategies to avoid being blocked.
- Authentication: Ensure that the API key used is valid and has the necessary permissions for the requested actions.