Loading image...Kiro

Product

  • About Kiro
  • IDE
  • CLI
  • Web
  • Mobile
  • Crew
  • Pricing
  • Downloads

For

  • Enterprise
  • Startups
  • Students

Community

  • Overview
  • Ambassadors
  • Discord
  • Events
  • Powers
  • Shop
  • Showcase

Resources

  • Docs
  • Blog
  • Changelog
  • FAQs
  • Report a bug
  • Suggest an idea
  • Billing support

Social

Site TermsLicenseResponsible AI PolicyLegalPrivacy PolicyCookie Preferences
Loading image...Kiro
  • Enterprise
  • Pricing
  • Docs
SIGN INDOWNLOADS
Loading image...Kiro

Get Started

InstallationAuthenticationYour first project

Models

OverviewAvailable modelsReasoning effort

Features

How Kiro works
Specs
Steering
Hooks
MCP
Permissions
Custom agents
Agent Skills
Powers
CompactionKiroignoreCheckpoints and rewind
Built-in tools
Configuration scopes

IDE 1.x

What's new in 1.0
Setup & First Run
Editor
Chat
Experimental
Troubleshooting0.x reference

CLI

What's new in 3.0
Setup & First Run
Terminal UI
Chat
Headless modeACPAuto complete
Experimental
2.x reference

Crew

Quick startInstallationRunning 24/7
Chat
Agent Capabilities
Agents
Agent Templates
Integrations (MCP)
Skills
Steering
Hooks
Prompts
Features
Interfaces
Apps
ConfigurationSecurityTroubleshooting

Web - Preview

Setup & First RunIdentity Center
Connect your repositories
Working with the agent
Autonomous modeAutomations
Sandbox

Mobile - Preview

Overview

Commands and Reference

CLI commandsSlash commandsBuilt-in toolsExit codesSettingsIDE keyboard shortcuts

Billing

OverviewManaging your subscriptionUpgrading your planDowngrading your planCancelling your planPurchasing add-on creditsManaging your paymentsManaging usage notificationsManaging your taxesContacting billing supportDeleting your accountRelated questions

Enterprise

ConceptsOnboarding quickstart
Connecting your identity provider
Subscribe your teamManage subscriptions
Governance
Monitor and track
SettingsManaged updatesBillingIAMSupported regions

Privacy and Security

OverviewData protectionCode referencesCompliance validationInfrastructure securityIAM permissionsFirewalls, proxies, and data perimetersVPC endpoints (AWS PrivateLink)

Guides

Overview
Language support
Learn by playing

Migration

Migrating from Q DeveloperMigrating from VSCodeUpgrading from Q CLI
  1. Docs
  2. Crew
  3. Agent Capabilities
  4. Skills

Skills


Skills are markdown files that teach the agent specific capabilities — a workflow, a domain, a set of best practices. They load on-demand when relevant to the conversation, keeping context lean when they're not needed.

Managing skills

From the dashboard (recommended)

Open Agent Capabilities → Skills. You can:

  • View every installed skill's name and description
  • Toggle skills between always-on (loaded every session) and on-demand (loaded when relevant)
  • Edit skill content inline
  • Add new skills

From the filesystem

Skills are plain markdown files. Edit them with any editor — changes take effect on the next agent invocation (no restart needed). They live under ~/.kiro/crew/skills/.

How skills load

  • Always-on skills — full content injected into every session
  • On-demand skills — loaded only when your message matches the skill's trigger keywords

You don't need to tell the agent to use a skill. If you mention something that matches a skill's triggers, it loads automatically.

Built-in skills

Crew ships with skills for common workflows:

  • kirocrew-commands — reference for CLI subcommands and MCP tools
  • security-assistance — safe-by-default patterns for security-adjacent code
  • prepare-pr — pre-review build + test + description formatting
  • artifacts — creating and iterating on persistent artifacts
  • widgets — building interactive mcwidgets

Additional skills are available and visible in the Skills panel.

Creating a skill

For power users who want to teach the agent something custom. Create a file at ~/.kiro/crew/skills/my-skill/SKILL.md:

markdown
--- name: my-skill description: Explains how to do X in our codebase. triggers: [deploy, release, ship] always: false --- # My skill When the user asks about deploying: 1. Run the test suite first 2. Check the staging environment 3. Use the deploy script at scripts/deploy.sh

The triggers field lists keywords — when any appear in your message, the skill loads for that turn.

Page updated: August 4, 2026
Integrations (MCP)
Steering