How to Use npx to Add AWS Agent Toolkit Skills: A Complete Guide

You can add AWS Agent Toolkit skills to any compatible AI agent by running npx skills add aws/agent-toolkit-for-aws/skills, which downloads the Markdown-based skill definitions from the repository and registers them with your agent's runtime.

The aws/agent-toolkit-for-aws repository distributes reusable instruction bundles—called skills—as plain-text Markdown files that guide AI coding agents through AWS-specific tasks. Using npx to add these skills requires no local installation of additional binaries, allowing you to integrate AWS capabilities into Claude Code, Codex, Cursor, Kiro, or any MCP-compatible agent instantly.

Understanding AWS Agent Toolkit Skills

Skills in the AWS Agent Toolkit are self-contained instruction sets stored in the repository's skills/ directory. Each skill follows a standardized structure defined in individual SKILL.md manifest files, which contain metadata, input definitions, and reference links for specific AWS workflows.

Key files governing the skill architecture include:

• skills/README.md – Documents the layout of skill directories and explains how agents discover available capabilities
• skills/**/SKILL.md – Individual skill manifests (e.g., skills/core-skills/aws-serverless/SKILL.md) that define deployment procedures, architecture patterns, and validation steps
• README.md (lines 94-99) – Contains the quick-start reference for the npx skills add command that initializes the installation process

Installing Skills with npx

The npx skills add command executes a three-stage registration process without requiring permanent installation of the skills package. Because npx ships with npm ≥ 5.2, the command runs the latest registry version directly.

When you execute npx skills add aws/agent-toolkit-for-aws/skills, the following occurs:

1. Fetch – The tool clones or accesses the aws/agent-toolkit-for-aws repository, targeting the skills/ subdirectory
2. Copy – Each sub-folder under skills/ (such as core-skills/aws-serverless/ or specialized-skills/web-and-mobile-development/aws-amplify/) replicates into your local skill root directory
3. Register – The agent's discovery process scans the skill root, indexes the SKILL.md manifests, and exposes capabilities through the AWS MCP server

The skill root location depends on your agent runtime but can be overridden using environment variables defined by your specific agent implementation.

Practical Installation Examples

Basic Installation

Install the complete skill set from the main branch:

npx skills add aws/agent-toolkit-for-aws/skills

Verify Installation

Confirm that skills copied correctly by listing the core serverless skill directory:

ls $AGENT_SKILL_ROOT/core-skills/aws-serverless

Using Skills in Prompts

Invoke a specific skill using the @ syntax supported by most compatible agents:

@aws-serverless:deploy

Update to Latest Version

Refresh your local skills to match the current repository state:

npx skills add aws/agent-toolkit-for-aws/skills --upgrade

Pin to Specific Versions

Install skills from a specific tag or commit for reproducible environments:

npx skills add aws/agent-toolkit-for-aws@v1.4.3/skills

Skill Discovery and MCP Registration

After installation, the AWS MCP server manages skill exposure to your agent. The server references the .cursor-plugin/marketplace.json file to understand how UI-based agents like Cursor should import the repository structure, while the plugins/aws-core/README.md documents how to activate the MCP server configuration after skills are installed.

This architecture keeps skill definitions decoupled from agent binaries—you can modify, add, or remove skills without rebuilding your agent environment. The MCP server logs every skill-load operation, providing an audit trail of which AWS capabilities were available during specific coding sessions.

Cross-Agent Compatibility and Security

The npx approach ensures cross-agent compatibility, functioning identically across Claude Code, GitHub Copilot (Codex), Cursor, Kiro, and custom agents that honor the skill-root convention. Because skills reside in a public, version-controlled repository, agents can verify the cryptographic hash of each installed skill directory before execution, preventing tampering with instruction sets.

This design supports version-pinning for compliance scenarios, allowing teams to lock agents to specific skill releases (e.g., v1.2.0) while maintaining the ability to audit exactly which AWS guidance the agent followed during infrastructure deployments.

Summary

• Use npx skills add aws/agent-toolkit-for-aws/skills to install AWS capabilities without permanent package installation
• Skills are Markdown-based instruction sets stored under the skills/ directory, with metadata defined in individual SKILL.md files
• The installation process fetches, copies, and registers skills into your agent's skill root, making them discoverable via the AWS MCP server
• Version-pinning syntax (@v1.4.3) enables reproducible agent configurations for security-sensitive environments
• The same command works across Claude Code, Codex, Cursor, Kiro, and other MCP-compatible agents

Frequently Asked Questions

What is the exact npx command to add AWS Agent Toolkit skills?

Run npx skills add aws/agent-toolkit-for-aws/skills to fetch and register the complete skill set. This command, referenced in the repository's README.md at lines 94-99, requires no prior installation of the skills package because npx executes it directly from the npm registry.

Where are the skill files located in the repository?

Skill definitions reside in the skills/ folder at the repository root. Each skill maintains its own subdirectory containing a SKILL.md manifest file—for example, skills/core-skills/aws-serverless/SKILL.md contains the serverless deployment instructions and metadata.

Can I use AWS Agent Toolkit skills with agents other than Claude Code?

Yes. The skill installation mechanism works with any agent that supports the skill-root convention, including GitHub Copilot (Codex), Cursor, Kiro, and custom MCP-compatible implementations. The .cursor-plugin/marketplace.json file specifically defines how Cursor imports these skills through its marketplace interface.

How do I update skills to a specific version rather than the latest?

Append the version tag to the repository path: npx skills add aws/agent-toolkit-for-aws@v1.4.3/skills. This pins your agent to that specific release, ensuring consistent behavior across different development environments and providing auditability for compliance requirements.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}