Agent skill
agentuity-cli-cloud-keyvalue-delete-namespace
Delete a keyvalue namespace and all its keys. Requires authentication. Use for Agentuity cloud platform operations
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/design/agentuity-cli-cloud-keyvalue-delete-namespace
Metadata
Additional technical details for this skill
- tags
- destructive deletes-resource slow requires-auth requires-project
- command
- agentuity cloud keyvalue delete-namespace
SKILL.md
Cloud Keyvalue Delete-namespace
Delete a keyvalue namespace and all its keys
Prerequisites
- Authenticated with
agentuity auth login - Project context required (run from project directory or use
--project-id)
Usage
agentuity cloud keyvalue delete-namespace <name> <confirm>
Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
<name> |
string | Yes | - |
<confirm> |
string | Yes | - |
Examples
Delete staging namespace (interactive):
bunx @agentuity/cli kv delete-namespace staging
Delete cache without confirmation:
bunx @agentuity/cli kv rm-namespace cache --confirm
Force delete production:
bunx @agentuity/cli kv delete-namespace production --confirm
Output
Returns JSON object:
{
"success": "boolean",
"namespace": "string",
"message": "string"
}
| Field | Type | Description |
|---|---|---|
success |
boolean | Whether the deletion succeeded |
namespace |
string | Deleted namespace name |
message |
string | Confirmation message |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?