CLI Execution
CLI execution best practices covering RTK token compression, AWS discover-then-execute patterns, output control, and bash/zsh scripting with logging. Use when running CLI commands, querying AWS resources, writing automation scripts, or working with shell tooling.
Install
npx skills add aws-samples/sample-kiro-cli-multiagent-development --skill cli-executiongit clone --depth 1 https://github.com/aws-samples/sample-kiro-cli-multiagent-development.git /tmp/sample-kiro-cli-multiagent-development
mkdir -p ~/.claude/skills
cp -r /tmp/sample-kiro-cli-multiagent-development/skills/cli-execution ~/.claude/skills/cli-executionPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# CLI Execution ## RTK — Token Compression Prefix read-heavy, side-effect-free commands with `rtk` to compress their output 60–90% before it enters context: ```bash rtk cargo test rtk git log rtk git status rtk npm run build rtk pytest rtk grep -r foo . rtk ls rtk tree rtk diff ``` **Never prefix mutating or destructive commands with `rtk`** (`git push`, `git commit`, `rm`, `npm install`, `npm publish`, deploys, `terraform apply`, `kubectl apply/delete`). Run those as normal commands so they pass through the destructive-command guard hook unaltered. A `rtk-compress` hook auto-compresses read-only, rtk-supported commands even if the prefix is forgotten. Mutating and unsupported commands run normally regardless. ## AWS — Discover Then Execute There is no built-in AWS tool. Work with AWS in two steps: 1. **Discover** — use the AWS Knowledge MCP server to find the right service/API/CLI command and read the relevant documentation (parameters, ARNs, required IAM actions). 2. **Execute** — run the actual `aws` CLI command in the shell. Read-only calls (`describe-*`, `list-*`, `get-*`, `s3 ls`) are auto-compressed by RTK; write/mutating calls run normally and prompt per `permissions.yaml`. Prefer least-privilege and verify parameters/permissions against the MCP docs before executing. ### Pagination Control Always use `--no-cli-pager` for complete results in a single response:
Details
- Skill name
cli-execution- Path
skills/cli-execution/SKILL.md- License
- MIT-0
- Repo updated
- 9 September 2026
FAQ
What does the CLI Execution skill do?
CLI execution best practices covering RTK token compression, AWS discover-then-execute patterns, output control, and bash/zsh scripting with logging. Use when running CLI commands, querying AWS resources, writing automation scripts, or working with shell tooling.
How do I install the CLI Execution skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add aws-samples/sample-kiro-cli-multiagent-development --skill cli-execution. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is CLI Execution popular?
It lives in aws-samples/sample-kiro-cli-multiagent-development, which has 43 GitHub stars and 9 forks.
Related skills
Agentcore Patterns
43aws-samples/sample-kiro-cli-multiagent-development
Verified Amazon Bedrock AgentCore patterns for Runtime handlers, Gateway MCP clients with SigV4/IAM auth, Memory session management with Strands, and Bedrock cross-region inference-profile IAM policies. Use when building or debugging AgentCore-based agents.
AWS Technical Docs
43aws-samples/sample-kiro-cli-multiagent-development
AWS technical documentation patterns covering procedures, lists, tables, titles, error messages, and content patterns. Use when writing AWS service documentation, procedures, troubleshooting guides, tutorials, or getting started content.
Cloudwatch Dashboards
43aws-samples/sample-kiro-cli-multiagent-development
AWS CloudWatch dashboard observability patterns including dashboard hierarchy, widget selection, CDK implementation, metric math, alarms, and cross-account monitoring. Use when creating dashboards, setting up observability, or instrumenting workloads with CloudWatch.
Developing Packages R
67jeremy-allen/claude-skills
Building robust R packages with modern tidyverse patterns. Use this skill when creating or maintaining R packages, designing APIs, choosing dependencies, implementing input validation, writing error messages, or deciding between internal and exported functions. Covers dependency strategy, tidyverse API design patterns, validation approaches, error handling with cli/rlang, testing levels, and documentation priorities.
Triage
115javiarmesto/ALDC-AL-Development-Collection
Reactive support for EXISTING Business Central AL code — reproduce, localize, root-cause, and recommend a minimal fix for bugs, regressions, and incidents. Read-only on code: produces a diagnosis and hands the fix to @al-implementer. The dynamic counterpart to the static audit (/aldc:audit). Use when you start from a symptom ("this throws", "this is slow", "broke after the last change").
Metaprogramming Rlang
67jeremy-allen/claude-skills
Tidy evaluation and programmatic tidyverse patterns using rlang. Use this skill when writing functions that accept column names as arguments, building tidyverse-compatible APIs, or working with data-masking and injection operators. Covers embracing with {{}}, injection (!! and !!!), dynamic dots, .data/.env pronouns, name injection with glue syntax, bridge patterns between selection and data-masking, and package development with rlang.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.