Skip to content
TrustedSkillsbeta
Back to all skills

Azure Aigateway

Checked
tyler-r-kendrick·vlatest·cloud·MIT

Automates Azure API Gateway configuration and deployment based on Kendrick's specifications for streamlined cloud integration.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tyler-r-kendrick/agent-skills --skill azure-aigateway -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

tyler-r-kendrick

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 tyler-r-kendrick/agent-skills at b6b5c287c7.

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

Scanned
3 files, 2,097 lines
Copies in repo
3 — all of them scanned
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 allows AI agents to interact with Azure OpenAI services through an API gateway. It handles authentication, rate limiting, and request routing to ensure secure and efficient access to models like GPT-3 and Codex. The gateway provides a centralized point of control for managing all requests to Azure OpenAI resources.

When to use it

  • Securely Accessing Azure OpenAI: When you need to integrate Azure OpenAI into an AI agent without exposing your API keys directly.
  • Managing Rate Limits: To prevent exceeding rate limits imposed by Azure OpenAI and ensure consistent performance.
  • Centralized Control: For organizations needing a single point of management for all interactions with their Azure OpenAI resources.

Key capabilities

  • Authentication to Azure OpenAI services
  • Rate limiting enforcement
  • Request routing to specific models (e.g., GPT-3, Codex)

Example prompts

  • "Send the following prompt to Azure OpenAI: 'Write a short poem about cats.'"
  • "Translate this text into French using the Codex model: [text]"
  • "Summarize this article and send it to Azure OpenAI for analysis."

Tips & gotchas

  • Requires proper configuration of your Azure OpenAI API keys within the skill's settings.
  • Be mindful of Azure OpenAI’s content filtering policies when crafting prompts.