← Back to Skills Marketplace
Awscli
by
HypertextAssassinRajith
· GitHub ↗
· v0.1.2
956
Downloads
2
Stars
1
Active Installs
3
Versions
Install in OpenClaw
/install awscli
Description
Manage AWS Lightsail and EC2 instances using AWS CLI
README (SKILL.md)
AWS CLI Control Skill
This skill manages AWS Lightsail instances.
Requirements
-
AWS CLI installed on host
-
AWS credentials configured (IAM user or role)
-
Environment variables:
- AWS_REGION
- ALLOWED_INSTANCES
Environment Variables
This skill requires the following environment variables:
- AWS_REGION (e.g., ap-southeast-1)
- ALLOWED_INSTANCES (comma-separated list)
Example:
AWS_REGION=ap-southeast-1 ALLOWED_INSTANCES=Ubuntu,Binami
Available Operations
1. List Instances
action: "list"
Example: { "action": "list" }
2. Reboot Instance
action: "reboot"
instance: "\x3Cinstance-name>"
Example: { "action": "reboot", "instance": "Ubuntu-1" }
3. Start Instance
action: "start"
instance: "\x3Cinstance-name>"
4. Stop Instance
action: "stop"
instance: "\x3Cinstance-name>"
Notes
- Only use structured JSON input.
- Do NOT generate AWS CLI commands.
- Instance names must exactly match existing Lightsail instances.
Usage Guidance
Do not install blindly. This skill will run the local 'aws' CLI using whatever AWS credentials are configured on the host, but the registry metadata does not declare those credentials — verify before installing. Specific points to consider:
- The skill only implements Lightsail commands (not EC2) despite the description mentioning EC2.
- SKILL.md and index.js require AWS_REGION and ALLOWED_INSTANCES, but the published metadata shows no required env vars; the skill will fail or behave unexpectedly if those are not set.
- index.js uses ALLOWED_INSTANCES without null checks and will throw if the env var is missing; ensure ALLOWED_INSTANCES is set and formatted correctly (the code does not trim values).
- package.json sets "type": "commonjs" but index.js uses ES module import/export — this is a runtime mismatch and may cause the skill to fail.
- Because the skill executes the 'aws' binary, it will act with whatever IAM permissions the host credentials provide. Only enable this skill in an environment where the AWS credentials are appropriately scoped (least privilege) and test in a safe account before using in production.
If you still want this skill: ensure AWS CLI is installed, configure a dedicated IAM principal with minimal Lightsail permissions, set AWS_REGION and ALLOWED_INSTANCES explicitly, and prefer testing in an isolated environment. If you need EC2 control, request clarification or a corrected version that actually implements EC2 and fixes the package/type and input validation issues.
Capability Analysis
Type: OpenClaw Skill
Name: awscli
Version: 0.1.2
The skill is benign. It securely manages AWS Lightsail instances by using `execFile` with arguments passed as an array, preventing shell injection. User-provided instance names are strictly validated against an `ALLOWED_INSTANCES` environment variable, and the `SKILL.md` explicitly instructs the AI agent 'Do NOT generate AWS CLI commands,' mitigating prompt injection risks. There is no evidence of data exfiltration, persistence, or other malicious intent.
Capability Assessment
Purpose & Capability
The skill's description says 'Lightsail and EC2' but both the SKILL.md and the code only implement AWS Lightsail operations. The registry metadata lists no required env vars or credentials, yet SKILL.md and index.js require AWS_REGION and ALLOWED_INSTANCES and expect AWS CLI credentials/configuration. This is a clear mismatch between claimed purpose and actual requirements.
Instruction Scope
SKILL.md instructs using AWS CLI and requires AWS_REGION and ALLOWED_INSTANCES; the runtime code executes the 'aws' binary via child_process. The SKILL.md says 'Do NOT generate AWS CLI commands' (consistent with the skill executing them), but it does not declare or explain that the host must have AWS credentials configured. The instructions permit the agent to run commands that will use host AWS credentials — a sensitive action not declared in registry metadata.
Install Mechanism
There is no install spec (instruction-only with a small code file). No external downloads or package installs are declared, so nothing is written to disk beyond the included index.js. Risk from install mechanism itself is low.
Credentials
The skill requires AWS_REGION and ALLOWED_INSTANCES (SKILL.md and code) and implicitly requires AWS CLI credentials, but the registry metadata lists no required env vars or primary credential. The code trusts ALLOWED_INSTANCES without null checks and will error if the env var is absent. Asking for host AWS credentials (via configured AWS CLI) is proportionate to managing instances — but the absence of that requirement in metadata and lack of input validation are problematic.
Persistence & Privilege
The skill is not force-installed (always:false) and does not request persistent system-wide privileges or modify other skills. Autonomous invocation is allowed by default (not flagged on its own).
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install awscli - After installation, invoke the skill by name or use
/awscli - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.2
- Added requirements section specifying AWS CLI installation, credentials, and environment variables needed.
- Documented new mandatory environment variables: AWS_REGION and ALLOWED_INSTANCES.
- Provided example values for environment variables.
- Clarified instructions on environment setup for correct skill usage.
v0.1.1
- Internal updates to index.js and package.json.
- No changes to user-facing features or documentation.
v0.1.0
awscli skill version 0.1.0 changelog:
- Initial release with core functionality to manage AWS Lightsail instances.
- Supports listing, starting, stopping, and rebooting instances via structured JSON input.
- Ensures instance names must exactly match existing Lightsail instances.
- Direct AWS CLI command generation is disabled for safety.
Metadata
Frequently Asked Questions
What is Awscli?
Manage AWS Lightsail and EC2 instances using AWS CLI. It is an AI Agent Skill for Claude Code / OpenClaw, with 956 downloads so far.
How do I install Awscli?
Run "/install awscli" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Awscli free?
Yes, Awscli is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Awscli support?
Awscli is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Awscli?
It is built and maintained by HypertextAssassinRajith (@hypertextassassinrajith); the current version is v0.1.2.
More Skills