Automated summary
Lists a project’s agents on the Agentuity cloud platform through the `agentuity cloud agent list` CLI command.
Strengths
- Simple read-only command to run
- Supports JSON output for automation
- `--verbose` option shows full descriptions
Limitations
- Requires authentication and project context
- `--deploymentId` is marked required in the options table even though the examples omit it
- Only covers listing, not creating or modifying agents
Use it when you need an inventory of agents tied to an Agentuity deployment.
Do not use it to manage or modify agents, or outside the Agentuity platform.
Security analysis
SafeThe skill only documents a read-only Agentuity CLI command for listing cloud agents. It requires authentication and project context, and does not instruct destructive actions, secret exfiltration, obfuscated payloads, or safety bypasses.
No concerns found
How this analysis is madeExamples
List the Agentuity cloud agents for my current project and show the result as JSON.Show verbose details for the Agentuity cloud agents in deployment dep_abc123.Run `agentuity cloud agent list --verbose` in my project directory.name: agentuity-cli-cloud-agent-list description: List agents for a project. Requires authentication. Use for Agentuity cloud platform operations version: "0.0.103" license: Apache-2.0 allowed-tools: "Bash(agentuity:*)" metadata: command: "agentuity cloud agent list"
Cloud Agent List
List agents for a project
Prerequisites
- Authenticated with
agentuity auth login - Project context required (run from project directory or use
--project-id)
Usage
agentuity cloud agent list [options]
Options
| Option | Type | Required | Default | Description |
|--------|------|----------|---------|-------------|
| --deploymentId | string | Yes | - | Filter by deployment ID |
| --verbose | boolean | No | false | Show full descriptions |
Examples
List items:
bunx @agentuity/cli cloud agent list
Use verbose option:
bunx @agentuity/cli cloud agent list --verbose
Show output in JSON format:
bunx @agentuity/cli --json cloud agent list
Output
Returns: array
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/cloud-agent-list-mrwakb59/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/cloud-agent-list-mrwakb59' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/cloud-agent-list-mrwakb59/download' --output '.skill-downloads/cloud-agent-list-mrwakb59/SKILL.md.part' && mv '.skill-downloads/cloud-agent-list-mrwakb59/SKILL.md.part' '.skill-downloads/cloud-agent-list-mrwakb59/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash(agentuity:*)
Original excerpt: Prerequisites
- Authenticated with
agentuity auth login - Project context required (run from project directory or use
--project-id)
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/cloud-agent-list-mrwakb59/SKILL.md' && test -s '.skill-downloads/cloud-agent-list-mrwakb59/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/agentuity-cli-cloud-agent-list' && cp -R '.skill-downloads/cloud-agent-list-mrwakb59' '.claude/skills/agentuity-cli-cloud-agent-list'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/cloud-agent-list-mrwakb59'openskills read 'cloud-agent-list-mrwakb59'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/cloud-agent-list-mrwakb59/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.