Kiro — Skills
- File format
- Markdown
- Discovery path
.kiro/steering- Syllago install method
- Project scope, Direct copy
- Symlink support
- Yes
- Native frontmatter fields
name,description,license,compatibility,metadata
Features
How each feature converts to syllago's canonical format. See format conversion for what these statuses mean.
Fields
Native frontmatter or config fields this provider exposes. The first column is the provider's own field name; the canonical key column links to syllago's cross-provider equivalent.
| Provider field | Conversion | Canonical key | Summary |
|---|---|---|---|
compatibility | TranslatedConversion type: TranslatedActively mapped to the target provider’s equivalent field during conversion.Learn more → | compatibility | yaml frontmatter key: compatibility (optional) |
description | TranslatedConversion type: TranslatedActively mapped to the target provider’s equivalent field during conversion.Learn more → | description | yaml frontmatter key: description (required) |
license | TranslatedConversion type: TranslatedActively mapped to the target provider’s equivalent field during conversion.Learn more → | license | yaml frontmatter key: license (optional) |
metadata | TranslatedConversion type: TranslatedActively mapped to the target provider’s equivalent field during conversion.Learn more → | metadata_map | yaml frontmatter key: metadata (optional map) |
name | TranslatedConversion type: TranslatedActively mapped to the target provider’s equivalent field during conversion.Learn more → | display_name | yaml frontmatter key: name (required, slug-style identifier) |
displayName | Conversion type: No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost.Learn more → | — | Human-readable label distinct from the slug-style 'name' field; used by Kiro for UI display. |
keywords | Conversion type: No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost.Learn more → | — | Array of activation trigger words used by Kiro's automatic power-loading system. When a user mentions a keyword in conversation, Kiro activates the matching power. |
Other features
Behaviors, conventions, and capabilities that aren't tied to a single named field — things like path-based activation, discovery rules, and lifecycle behavior.
| Feature | Conversion | Summary |
|---|---|---|
canonical_filename | TranslatedConversion type: TranslatedActively mapped to the target provider’s equivalent field during conversion.Learn more → | Fixed filename POWER.md (required, all caps) |
project_scope | TranslatedConversion type: TranslatedActively mapped to the target provider’s equivalent field during conversion.Learn more → | Self-contained directory installed via Kiro Powers panel (UI installation, no fixed filesystem path) |
| steering/ directory | Conversion type: No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost.Learn more → | Optional steering/ subdirectory containing workflow-specific guidance files loaded on-demand. Complex powers can map different steering files to specific workflows to avoid context overload. |
| mcp.json bundled in power directory | Not portableConversion type: Not portableUnique to this provider — can’t be carried across providers.Learn more → | Optional mcp.json inside the power directory declaring MCP servers; server names referenced in POWER.md must match keys in this file. Environment variables are recommended for API keys and secrets. |
| Onboarding section in POWER.md | Not portableConversion type: Not portableUnique to this provider — can’t be carried across providers.Learn more → | Dedicated '# Onboarding' section whose instructions Kiro runs automatically on first activation, covering dependency validation and setup explanation. |
Sources
| Source |
|---|
| https://kiro.dev/docs/powers/create/ |