kiro-research
Research AWS topics using Kiro CLI as an AWS expert (readonly mode). Use for: AWS documentation, error investigation, CloudFormation/CDK questions, AWS best practices. Note: Uses Kiro's training knowledge only (no web search).
What this skill does
# Kiro Research Skill
This skill provides integration with Kiro CLI for AWS research and troubleshooting tasks.
Kiro runs in **readonly mode** - answering from its trained AWS expertise without web search.
## Prerequisites
- Kiro CLI installed (visit https://kiro.dev or download from AWS)
- AWS credentials configured (for AWS-specific operations)
## Available Scripts
All scripts are located in `${CLAUDE_PLUGIN_ROOT}/scripts/`.
### 1. Check Installation
```bash
${CLAUDE_PLUGIN_ROOT}/scripts/check-kiro.sh
```
Verifies Kiro CLI is installed and accessible.
### 2. Research Mode (kiro-cli chat)
```bash
${CLAUDE_PLUGIN_ROOT}/scripts/kiro-ask.sh "your research question"
```
Use for:
- AWS service documentation lookup
- CloudFormation/CDK troubleshooting
- AWS error investigation
- Best practices inquiry
- Architecture recommendations
Example:
```bash
${CLAUDE_PLUGIN_ROOT}/scripts/kiro-ask.sh "How do I configure VPC endpoints for S3?"
```
## Workflow
1. First, verify Kiro CLI is available using `check-kiro.sh`
2. For research tasks, use `kiro-ask.sh` with the research prompt
3. Summarize findings and provide actionable recommendations
## Kiro CLI Options Reference
| Option | Description |
|--------|-------------|
| `--no-interactive` | Run without user input (used by scripts) |
| `--agent <AGENT>` | Specify agent to use |
| `--model <MODEL>` | Specify model to use |
| `-a, --trust-all-tools` | Allows model to use any tool without confirmation |
| `--trust-tools=<TOOL_NAMES>` | Trust only specific tools (e.g., `--trust-tools=fs_read,fs_write`) |
## Error Handling
- **Timeout**: Commands timeout after 120 seconds
- **Not installed**: Provides installation instructions
- **Credentials**: Prompts to configure AWS credentials if needed
## Input Sanitization
For security, prompts are sanitized before execution:
- Newlines and carriage returns are removed (multi-line prompts become single-line)
- Backticks (`) and dollar signs ($) are stripped to prevent prompt injection
## Notes
- This skill uses `context: fork` to isolate large outputs from the main conversation context.
- **Readonly mode**: Kiro answers from its training knowledge only (no web search or external tools).
- For web search needs, use Claude's built-in WebSearch or Gemini instead.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.