agentuity-cli-cloud-apikey-get
Get a specific API key by id. Requires authentication. Use for Agentuity cloud platform operations
npx skills add majiayu000/claude-skill-registry --skill agentuity-cli-cloud-apikey-get-agentuity-examples --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Cloud Apikey Get Get a specific API key by id ## Prerequisites - Authenticated with `agentuity auth login` ## Usage ```bash agentuity cloud apikey get <id> ``` ## Arguments | Argument | Type | Required | Description | |----------|------|----------|-------------| | `<id>` | string | Yes | - | ## Examples Get item details: ```bash bunx @agentuity/cli cloud apikey get <id> ```
- Prerequisites
- Usage
- Arguments
- Examples
agentuity cloud apikey get <id> bunx @agentuity/cli cloud apikey get <id>
What does the agentuity-cli-cloud-apikey-get skill do?
Get a specific API key by id. Requires authentication. Use for Agentuity cloud platform operations
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill agentuity-cli-cloud-apikey-get-agentuity-examples --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.