Skip to content
TrustedSkillsbeta
Back to all skills

Api Integration Specialist

Checked
davila7·vlatest·backend·MIT

Helps 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.

Installs under a different name. Its SKILL.md names it API Integration Specialist, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add davila7/claude-code-templates --skill "API Integration Specialist" -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

davila7

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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

    Makes no network calls.

    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.

  • No 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 davila7/claude-code-templates at 79182c51fb.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 351 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to connect and interact with external APIs, allowing for data retrieval, service invocation, and system integration. It supports authentication methods like OAuth and API keys, ensuring secure communication between systems.

When to use it

  • Integrating third-party services such as payment gateways or social media platforms into an application
  • Automating workflows by pulling real-time data from external sources like weather APIs or stock market feeds
  • Building custom tools that require interaction with RESTful or GraphQL-based endpoints

Key capabilities

  • Secure API authentication using OAuth and API keys
  • Support for RESTful and GraphQL API calls
  • Error handling and logging for API requests
  • Data parsing and transformation from API responses

Example prompts

  • "Connect to the GitHub API and retrieve my recent commits."
  • "Fetch weather data from OpenWeatherMap for New York City."
  • "Authenticate with Stripe using an API key and create a new customer profile."

Tips & gotchas

  • Ensure that all required API credentials are securely stored and not hardcoded in production environments.
  • Always validate and handle potential errors or rate limits imposed by external APIs to avoid disruptions.