Skip to main content

Using the Imgwire Agent Skill

Use the Imgwire Agent Skill when you want a coding agent to understand Imgwire's SDKs, upload flows, transformation options, CDN URL patterns, MCP tools, and CLI workflows before it edits your application.

The skill is published from Blackhawk-Software/imgwire-skills. It gives agents Imgwire-specific instructions so they can choose the right SDK, avoid exposing server keys, create upload-token endpoints, upload generated assets, and render transformed images through Imgwire.

Install the skill​

The recommended install path is Vercel's skills package manager.

Install the skill globally for Codex:

npx skills add Blackhawk-Software/imgwire-skills --skill imgwire-skill --agent codex --global

Install the skill globally for Claude Code:

npx skills add Blackhawk-Software/imgwire-skills --skill imgwire-skill --agent claude-code --global

To install it only in the current project, omit --global:

npx skills add Blackhawk-Software/imgwire-skills --skill imgwire-skill --agent codex

Useful install options:

  • Add --yes when you want a non-interactive install.
  • Add --copy when you want to copy the skill files instead of symlinking them.
  • Run npx skills add Blackhawk-Software/imgwire-skills --list to inspect available skills before installing.

Restart your agent session after installation so the skill can be discovered.

What the skill helps agents build​

Use the skill when an agent is working on Imgwire integration code or docs. It is designed for tasks like:

  • Adding browser, React, React Native, or Expo image uploads.
  • Adding backend endpoints that issue upload tokens for signed frontend uploads.
  • Uploading local, generated, or remotely hosted images to Imgwire.
  • Generating transformed CDN URLs with format: "auto" and quality: "auto".
  • Rendering responsive images with Imgwire SDK helpers or components.
  • Choosing the right SDK for Node.js, Python, Ruby, Go, browser JavaScript, React, or React Native.
  • Using the Imgwire MCP server or CLI for local, CI, static-site, and agent-driven image workflows.

Example prompt:

Use $imgwire-skill to add signed Imgwire uploads to this React app.

Another useful prompt:

Use $imgwire-skill to replace local generated hero images with Imgwire CDN URLs.

Use it with the Imgwire MCP server​

The skill can guide an agent through application code, but the Imgwire MCP Server gives the agent authorized Imgwire account access through OAuth. Use both together when you want the agent to manage image workflows directly, such as uploading generated documentation images, creating publishable client tokens, listing image records, or generating transformed CDN URLs.

The MCP server is also environment-aware. Authorized MCP connections are scoped to a specific Imgwire Environment, so the agent works against the same Environment your app uses.

Use it with the Imgwire CLI​

The Imgwire CLI is useful when an agent needs a shell workflow instead of MCP. For example, an agent can run CLI commands to upload a local file, import a remote asset URL, generate a CDN URL, or inspect account resources during a docs or build workflow.

Prefer MCP when OAuth-linked access is available. Use the CLI when you need repeatable terminal commands, CI scripts, or a fallback for agents that cannot connect to remote MCP servers.

Security notes​

The skill teaches agents to keep Server API Keys in trusted backend, local, or CI environments only. Do not put sk_... values in browser code, React Native bundles, public static output, or prompts that may be stored outside your control.

For frontend applications, use a Client Key and signed uploads when your backend should decide who can upload. For backend applications, keep the Server API Key in a server-only environment variable and use the Backend Quickstart for upload and upload-token examples.

Last updated at: May 9, 2026