Display the API key for the currently authenticated user. Requires authentication. Use for managing authentication credentials
Scanned 6/4/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill agentuity-cli-auth-apikey-agentuity-sdk-explorer-3 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Agentuity Cli Auth Apikey?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-agentuity-cli-auth-apikey)More formats (shields.io, HTML) on the badges page.
---
name: agentuity-cli-auth-apikey
description: Display the API key for the currently authenticated user. Requires authentication. Use for managing authentication credentials
version: "0.1.2"
license: Apache-2.0
allowed-tools: "Bash(agentuity:*)"
metadata:
command: "agentuity auth apikey"
tags: "read-only fast requires-auth"
---
# Auth Apikey
Display the API key for the currently authenticated user
## Prerequisites
- Authenticated with `agentuity auth login`
## Usage
```bash
agentuity auth apikey
```
## Examples
Print the API key:
```bash
bunx @agentuity/cli auth apikey
```
Output API key in JSON format:
```bash
bunx @agentuity/cli --json auth apikey
```
## Output
Returns JSON object:
```json
{
"apiKey": "string"
}
```
| Field | Type | Description |
|-------|------|-------------|
| `apiKey` | string | The API key for the authenticated user |
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...