kiro-session — Skill Integration

How It Works

When triggered as a skill inside kiro-cli, commands output structured JSON. The LLM in your active conversation parses it and responds in natural language.

💬 You ask in chat

→

🤖 Skill runs --json

→

📋 JSON result

→

💬 Kiro answers naturally

In-Chat Experience

Inside a kiro-cli conversation

You: Find my sessions about Docker networking from this week

⚙ kiro-session search "docker network" --recent 7d --json

Kiro: Found 2 sessions:

• API Gateway Migration (4d ago, /home/user/docs, 58 turns)

Configured nginx reverse proxy for Docker containers on bridge network.

• Docker Compose Setup (5d ago, /home/user/infra, 34 turns)

Set up Docker network for multi-container app with custom subnets.

To resume one, run in your terminal:

kiro-session → select session → [r] Resume

Listing with filters

You: What sessions touched Dockerfile recently?

⚙ kiro-session list --file Dockerfile --recent 7d --json

Kiro: 3 sessions touched Dockerfile in the last 7 days:

• Docker Compose Setup (5d ago, infra, 34 turns)

• CI Pipeline Fix (2d ago, project-x, 22 turns)

• Production Deploy (6h ago, ops, 15 turns)

Under the Hood: --json

All non-interactive commands support --json for clean structured output — no ANSI codes, no progress bars.

Raw JSON output

$

{

"results": [

{

"id": "612381ac",

"name": "API Gateway Migration",

"dir": "docs",

"updated": "4d ago",

"turns": 58,

"snippet": "...nginx reverse proxy for docker..."

}

]

}

What Works in Skill Mode

✅

Available

search, list with all filters (--file, --cmd, --dir, --recent). All via --json.

🔀

Guided to Terminal