Kiro Support Cases
File and track AWS Support cases for Kiro without leaving the IDE. Two backends:
AWS Support MCP Server (primary) and
Agent Toolkit (aws-mcp, fallback).
On activation
If intent is clear (e.g. "file a case for X"), go straight to the matching workflow.
Otherwise reply with just this menu — no preamble, no capability tour:
What do you need?
- Raise a case 2. Track a case 3. Read history 4. Reply 5. Resolve 6. Check access / setup
For "get started" / "check access" / "setup": run the read-only describe_support_cases
probe and report the result in one line (e.g. "Access confirmed — no open cases. What next?").
Do not explain what the power does, list its features, or show example code unless asked.
First-run onboarding
Before the first case in a session, confirm the environment is ready — silently, in this order.
Surface a step only if it fails; if all pass, continue to the task without narrating the checks.
uvx present — the MCP server launches via uvx. If uvx --version fails, point to the
install guide.AWS_PROFILE set — confirm mcp.json has a real profile, not the <your-aws-profile>
placeholder. If it's still the placeholder, ask the user to set it and reconnect the server.- Access probe — run
describe_support_cases once. Success → proceed. AccessDenied or
SubscriptionRequiredException → setup. Server won't start → fall back to aws-mcp.
Available MCP servers
Configured in mcp.json. Both backends reach the same AWS Support API with the same
IAM permissions (support:*) and require a Business+ support plan.
Primary — awslabs.aws-support-mcp-server (typed tools; all arguments use snake_case):
| Tool |
Purpose |
describe_support_cases |
List/search cases — also the read-only access probe |
describe_communications |
Full communication history for a case |
add_communication_to_case |
Reply to a case (optional attachments) |
create_support_case |
File a new case |
resolve_support_case |
Close a case (reopenable within 7 days) |
describe_services |
List services + category codes |
describe_severity_levels |
List severity levels + SLAs |
describe_create_case_options |
Valid categories/severities for a service |
describe_supported_languages |
List supported languages |
add_attachments_to_set |
Upload files → returns attachmentSetId |
describe_attachment |
Download an attachment by ID |
Fallback — aws-mcp (Agent Toolkit): runs aws support … CLI commands (kebab-case flags,
--region us-east-1) when the primary server can't start. CLI equivalents for each tool above are
in filing-and-tracking-cases.
Output contract (applies to EVERY response)
- No narration. Never write "Let me…", "Now I understand…", "Now I'll…". Just act, then report.
- No unsolicited overviews. Don't explain what the power does, list capabilities, or show
example workflows/code unless the user asks. They activated it; they know what it's for.
- No multi-section essays. No "1. What this does / 2. Setup / 3. Example" structures.
- No behind-the-scenes. Don't narrate which tools run internally, IAM/plan requirements, or
fallback servers unless the user asks or something fails.
- Lead with the result. Tool ran → one-line outcome → at most one short next-step question.
- Batch questions. All missing info in one message. Never drip questions across turns.
- Skip what you know. OS is in system context. Don't re-ask for anything already provided.
- Confirm once. Show the case body a single time for approval, then file. No recaps after.
Formatting
Brevity and polish aren't opposites — format for scannability, not length.
- Bold the lead. Start with the outcome in bold (e.g. Access confirmed), then a short clause.
- Bullets for capabilities. When listing what the power does, use a tight bulleted list with
the verb bolded (Raise, Track, …) — one line each, no sentences.
- Inline code for examples. Put example prompts and identifiers in backticks
(
file a normal case: Kiro chat keeps disconnecting on macOS), not fenced code blocks.
- Label the closer. End with a bolded lead-in for the next step (e.g. Next up: …).
- No headers, no tables, no emojis in chat replies — they add height without adding signal.
- Keep the whole thing scannable in one glance: bold anchors, short lines, ≤10 lines total.
When asked for an overview / walkthrough / example (e.g. the install "try it out" prompt)
Comply, but stay bounded — a request for an overview is not license for an essay:
- Overview: one short sentence, or one line per capability. No section headers.
- Setup/verify: run
describe_support_cases, report the one-line result. Don't recount the
guide's steps or explain what you're about to do.
- Example: one sentence describing the most common flow (filing a case). No code block, no
step-by-step internals, unless the user asks.
- Total: aim for ≤10 lines. End with one next-step question.
kiro-support files and tracks AWS Support cases without leaving Kiro:
- Raise a new case
- Track case status
- Read a case's history
- Reply to support
- Resolve a case
Typical flow: tell me an issue — e.g. file a normal case: Kiro chat keeps disconnecting on macOS — and I'll draft it, show you the body once for approval, then file on your OK.
Next up: file one, or check something else?
Steering guides — MUST read before acting
These files contain the detailed workflows, templates, and procedures for this skill. They are
located in the references/ directory alongside this SKILL.md file.
You MUST use read_file to load the matching file from this skill's references/ directory
BEFORE executing any intent. The files are located at:
skills/kiro-support/references/<filename> relative to the power root.
Do not attempt to file, track, reply, resolve, or troubleshoot without first reading the relevant
guide. Load only what the current intent requires; don't read them all up front.
| Intent |
File to read |
When to load |
| Filing, tracking, replying, resolving a case |
references/filing-and-tracking-cases.md |
Always before filing, replying, tracking, or resolving. Contains the required 4-step workflow, case body template, severity mapping, tool arguments, and attachment rules. |
| Backend selection, onboarding, IAM/permissions, troubleshooting |
references/setup.md |
Always before handling access errors, AccessDenied, SubscriptionRequiredException, server connection failures, or when user asks about setup/configuration. Contains backend fallback logic and the admin email template. |
| Capturing diagnostics, secrets reminder, attaching logs |
references/case-safety-and-diagnostics.md |
Always when filing a case. Contains the auto-capture workflow, session lookup, debug log location, attachment size rules, and secrets reminder. |
Filing a case requires reading TWO files:
- Read
references/filing-and-tracking-cases.md for the workflow and template.
- Read
references/case-safety-and-diagnostics.md for diagnostics collection.
Follow both fully. In particular: always offer capture these to auto-gather session data and
debug logs before drafting the case body. Do not skip diagnostics gathering.
Licenses
This power integrates with the AWS Support MCP Server (awslabs.aws-support-mcp-server, Apache-2.0 license).
This power integrates with MCP Proxy for AWS (mcp-proxy-for-aws, the aws-mcp / Agent Toolkit backend, Apache-2.0 license).
The reference files and SKILL.md are original content authored by the power author and are distributed as part of this power.
Telemetry
- Primary backend (
awslabs.aws-support-mcp-server): no client-side telemetry is documented or collected by the server.
- Fallback backend (
mcp-proxy-for-aws): collects telemetry by default. This power ships with
--disable-telemetry set in mcp.json, so telemetry is off out of the box. To re-enable it,
remove that flag from the aws-mcp args and reconnect the server.
- This power itself adds no additional telemetry, analytics, or usage tracking.
Privacy
- What leaves your machine: only the AWS Support case content you approve — subject, severity,
category, body, and any attachment you explicitly add — sent to the AWS Support API using your own
AWS credentials. Nothing is filed, replied to, or resolved without your confirmation.
- Local reads are opt-in: the power reads local Kiro session data (
~/.kiro/sessions/…) and
workspace debug logs (.kiro/debug/) only when you say capture these. It announces the read
before touching the filesystem.
- Secrets: the power reminds you to strip secrets (passwords, tokens, keys) from logs before
they're included in a case. Review case content before approving.
- No third parties: the power sends data only to the AWS Support API via your credentials; it
does not transmit your code, logs, or session data to any other endpoint.
1---2name: kiro-support3description: File and track AWS Support cases for Kiro issues without leaving the IDE. Use when creating, tracking, replying to, or resolving AWS Support cases, or when checking Support API access.4license: Apache-2.05---67# Kiro Support Cases89File and track AWS Support cases for Kiro without leaving the IDE. Two backends:10[AWS Support MCP Server](https://awslabs.github.io/mcp/servers/aws-support-mcp-server) (primary) and11[Agent Toolkit](https://aws.amazon.com/products/developer-tools/agent-toolkit-for-aws/) (`aws-mcp`, fallback).1213## On activation1415If intent is clear (e.g. "file a case for X"), go straight to the matching workflow.16Otherwise reply with just this menu — no preamble, no capability tour:1718> What do you need?19> 1. Raise a case 2. Track a case 3. Read history 4. Reply 5. Resolve 6. Check access / setup2021For "get started" / "check access" / "setup": run the read-only `describe_support_cases`22probe and report the result in one line (e.g. "Access confirmed — no open cases. What next?").23Do not explain what the power does, list its features, or show example code unless asked.2425## First-run onboarding2627Before the first case in a session, confirm the environment is ready — silently, in this order.28Surface a step only if it fails; if all pass, continue to the task without narrating the checks.29301. **`uvx` present** — the MCP server launches via `uvx`. If `uvx --version` fails, point to the31 [install guide](https://docs.astral.sh/uv/getting-started/installation/).322. **`AWS_PROFILE` set** — confirm `mcp.json` has a real profile, not the `<your-aws-profile>`33 placeholder. If it's still the placeholder, ask the user to set it and reconnect the server.343. **Access probe** — run `describe_support_cases` once. Success → proceed. `AccessDenied` or35 `SubscriptionRequiredException` → [setup](references/setup.md). Server won't start → fall back to `aws-mcp`.3637## Available MCP servers3839Configured in [`mcp.json`](../../mcp.json). Both backends reach the same AWS Support API with the same40IAM permissions (`support:*`) and require a Business+ support plan.4142**Primary — `awslabs.aws-support-mcp-server`** (typed tools; all arguments use `snake_case`):4344| Tool | Purpose |45| --- | --- |46| `describe_support_cases` | List/search cases — also the read-only access probe |47| `describe_communications` | Full communication history for a case |48| `add_communication_to_case` | Reply to a case (optional attachments) |49| `create_support_case` | File a new case |50| `resolve_support_case` | Close a case (reopenable within 7 days) |51| `describe_services` | List services + category codes |52| `describe_severity_levels` | List severity levels + SLAs |53| `describe_create_case_options` | Valid categories/severities for a service |54| `describe_supported_languages` | List supported languages |55| `add_attachments_to_set` | Upload files → returns `attachmentSetId` |56| `describe_attachment` | Download an attachment by ID |5758**Fallback — `aws-mcp`** (Agent Toolkit): runs `aws support …` CLI commands (kebab-case flags,59`--region us-east-1`) when the primary server can't start. CLI equivalents for each tool above are60in [filing-and-tracking-cases](references/filing-and-tracking-cases.md#toolkit-fallback-cli).6162## Output contract (applies to EVERY response)6364- **No narration.** Never write "Let me…", "Now I understand…", "Now I'll…". Just act, then report.65- **No unsolicited overviews.** Don't explain what the power does, list capabilities, or show66 example workflows/code unless the user asks. They activated it; they know what it's for.67- **No multi-section essays.** No "1. What this does / 2. Setup / 3. Example" structures.68- **No behind-the-scenes.** Don't narrate which tools run internally, IAM/plan requirements, or69 fallback servers unless the user asks or something fails.70- **Lead with the result.** Tool ran → one-line outcome → at most one short next-step question.71- **Batch questions.** All missing info in one message. Never drip questions across turns.72- **Skip what you know.** OS is in system context. Don't re-ask for anything already provided.73- **Confirm once.** Show the case body a single time for approval, then file. No recaps after.7475### Formatting7677Brevity and polish aren't opposites — format for scannability, not length.7879- **Bold the lead.** Start with the outcome in bold (e.g. **Access confirmed**), then a short clause.80- **Bullets for capabilities.** When listing what the power does, use a tight bulleted list with81 the verb bolded (**Raise**, **Track**, …) — one line each, no sentences.82- **Inline code for examples.** Put example prompts and identifiers in backticks83 (`file a normal case: Kiro chat keeps disconnecting on macOS`), not fenced code blocks.84- **Label the closer.** End with a bolded lead-in for the next step (e.g. **Next up:** …).85- **No headers, no tables, no emojis** in chat replies — they add height without adding signal.86- Keep the whole thing scannable in one glance: bold anchors, short lines, ≤10 lines total.8788### When asked for an overview / walkthrough / example (e.g. the install "try it out" prompt)8990Comply, but stay bounded — a request for an overview is not license for an essay:9192- **Overview:** one short sentence, or one line per capability. No section headers.93- **Setup/verify:** run `describe_support_cases`, report the one-line result. Don't recount the94 guide's steps or explain what you're about to do.95- **Example:** one sentence describing the most common flow (filing a case). No code block, no96 step-by-step internals, unless the user asks.97- **Total:** aim for ≤10 lines. End with one next-step question.9899<example>100<scenario>User: "help me get started"</scenario>101<bad>A three-part essay: what the power does, a walkthrough of the setup guide, a code102example, and a menu of six next steps.</bad>103<good>[runs describe_support_cases] "Access confirmed — no open cases yet. Want to file one,104or check something else?"</good>105</example>106107<example>108<scenario>Overview + example, formatted for scannability (still ≤10 lines).</scenario>109<good>110**Access confirmed** — no open cases, you're set up.111112**kiro-support** files and tracks AWS Support cases without leaving Kiro:113114- **Raise** a new case115- **Track** case status116- **Read** a case's history117- **Reply** to support118- **Resolve** a case119120**Typical flow:** tell me an issue — e.g. `file a normal case: Kiro chat keeps disconnecting on121macOS` — and I'll draft it, show you the body once for approval, then file on your OK.122123**Next up:** file one, or check something else?124</good>125</example>126127<example>128<scenario>Prompt asks for a brief overview + step-by-step setup + a simple example.</scenario>129<bad>Runs the probe, then writes "1. What this power does" (capability list), "2. Setup status"130(recaps the guide + IAM/plan notes), "3. A simple example" (code block + behind-the-scenes131tool sequence), then a six-option menu.</bad>132<good>[runs describe_support_cases] "Access confirmed — no open cases, you're set up.133This power files and tracks AWS Support cases from Kiro: raise, track, reply to, or resolve134cases. Typical use: tell me an issue like 'file a normal case: Kiro chat keeps disconnecting on135macOS' and I'll draft it, show you the body, and file on your OK. Want to try one?"</good>136</example>137138## Steering guides — MUST read before acting139140These files contain the detailed workflows, templates, and procedures for this skill. They are141located in the `references/` directory alongside this SKILL.md file.142143**You MUST use `read_file` to load the matching file from this skill's `references/` directory144BEFORE executing any intent.** The files are located at:145`skills/kiro-support/references/<filename>` relative to the power root.146147Do not attempt to file, track, reply, resolve, or troubleshoot without first reading the relevant148guide. Load only what the current intent requires; don't read them all up front.149150| Intent | File to read | When to load |151| --- | --- | --- |152| Filing, tracking, replying, resolving a case | `references/filing-and-tracking-cases.md` | **Always** before filing, replying, tracking, or resolving. Contains the required 4-step workflow, case body template, severity mapping, tool arguments, and attachment rules. |153| Backend selection, onboarding, IAM/permissions, troubleshooting | `references/setup.md` | **Always** before handling access errors, `AccessDenied`, `SubscriptionRequiredException`, server connection failures, or when user asks about setup/configuration. Contains backend fallback logic and the admin email template. |154| Capturing diagnostics, secrets reminder, attaching logs | `references/case-safety-and-diagnostics.md` | **Always** when filing a case. Contains the auto-capture workflow, session lookup, debug log location, attachment size rules, and secrets reminder. |155156**Filing a case requires reading TWO files:**1571. Read `references/filing-and-tracking-cases.md` for the workflow and template.1582. Read `references/case-safety-and-diagnostics.md` for diagnostics collection.159160Follow both fully. In particular: always offer `capture these` to auto-gather session data and161debug logs before drafting the case body. Do not skip diagnostics gathering.162163---164165## Licenses166167This power integrates with the [AWS Support MCP Server](https://github.com/awslabs/mcp) (`awslabs.aws-support-mcp-server`, Apache-2.0 license).168169This power integrates with [MCP Proxy for AWS](https://github.com/aws/mcp-proxy-for-aws) (`mcp-proxy-for-aws`, the `aws-mcp` / Agent Toolkit backend, Apache-2.0 license).170171The reference files and `SKILL.md` are original content authored by the power author and are distributed as part of this power.172173## Telemetry174175- **Primary backend** (`awslabs.aws-support-mcp-server`): no client-side telemetry is documented or collected by the server.176- **Fallback backend** (`mcp-proxy-for-aws`): collects telemetry by default. This power ships with177 `--disable-telemetry` set in [`mcp.json`](../../mcp.json), so telemetry is off out of the box. To re-enable it,178 remove that flag from the `aws-mcp` args and reconnect the server.179- This power itself adds no additional telemetry, analytics, or usage tracking.180181## Privacy182183- **What leaves your machine:** only the AWS Support case content you approve — subject, severity,184 category, body, and any attachment you explicitly add — sent to the AWS Support API using your own185 AWS credentials. Nothing is filed, replied to, or resolved without your confirmation.186- **Local reads are opt-in:** the power reads local Kiro session data (`~/.kiro/sessions/…`) and187 workspace debug logs (`.kiro/debug/`) only when you say `capture these`. It announces the read188 before touching the filesystem.189- **Secrets:** the power reminds you to strip secrets (passwords, tokens, keys) from logs before190 they're included in a case. Review case content before approving.191- **No third parties:** the power sends data only to the AWS Support API via your credentials; it192 does not transmit your code, logs, or session data to any other endpoint.
kirodotdev