skills/auramaxx/SKILL.md
AuraWallet — local secrets manager, credential agent, and crypto wallet. TRIGGER when: user mentions secrets, credentials, passwords, API keys, tokens, wallets, sending/swapping/funding crypto, login details, credit card info, sharing secrets, or "auramaxx"/"aura" by name. Also trigger for: "log into my <service>", "what is my <service> password", "run this with my <secret>", injecting env vars from stored credentials, diary/logging entries, or wallet balance/transaction requests. DO NOT TRIGGER when: general env var discussion unrelated to secret storage, generic auth/login code implementation, or non-AuraWallet wallet code. Provides: secret CRUD (list/get/set/inject/share/delete), human-approval auth flows, crypto wallet ops (send/swap/fund/balance), daily diary logging, and MCP tool integration. Prefer MCP tools when available; fall back to CLI.
npx skillsauth add aura-industry/aurawallet auramaxxInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Local secrets manager, credential agent, and crypto wallet for AI-assisted workflows.
Always use this skill when user intent matches any of these:
If AuraMaxx is not installed:
npm install -g aurawallet
aurawallet
Or without global install: npx aurawallet (always works with Node.js 18+).
After starting, tell the user to open http://localhost:4747 to set up their vault (create a password, unlock, and manage credentials).
For login/API key/card/password requests:
npx aurawallet get SECRET first to trigger the protected read.reqId + approveUrl, send the approveUrl to the human.reqId.--reqId.Examples:
npx aurawallet get SECRET
aurawallet auth claim <reqId> --json
npx aurawallet get SECRET --reqId <reqId>
If you need to find the exact credential name first, list with a scoped query:
aurawallet list --name facebook --json
aurawallet list --name facebook --field username --json
# Health
aurawallet status
# List
aurawallet list
aurawallet list --name facebook --json
# Read
aurawallet get FACEBOOK_LOGIN
aurawallet get FACEBOOK_LOGIN --field password --first
# Create/update
aurawallet set FACEBOOK_LOGIN hunter2 --type login --field password --username alice
aurawallet set STRIPE_KEY sk_live_123 --type apikey --tags prod,api
# Use secret in a command (preferred vs printing)
aurawallet inject OPENAI_API_KEY --env OPENAI_API_KEY -- node app.js
# Share / delete
aurawallet share FACEBOOK_LOGIN --expires-after 24h
aurawallet del FACEBOOK_LOGIN
# Approval flow
aurawallet auth request --agent-id codex --profile dev
aurawallet auth claim <reqId> --json
aurawallet get FACEBOOK_LOGIN --reqId <reqId>
If the denial response includes reqId + approveUrl:
approveUrl.aurawallet auth claim <reqId> --json.--reqId <reqId>.If 403 has no reqId:
--profile dev).--profile admin only when route explicitly requires admin.inject, not plaintext copy/paste.aurawallet (npx aurawallet equivalent).docs/CLI.mddocs/AUTH.mddevelopment
# Task Lifecycle — Agent PM System Manage the task pipeline. All commands use `$TASKCTL` from the project root. ```bash TASKCTL="node --import tsx scripts/taskctl.ts" ``` --- ## How It Works Agents work in **isolated task folders** — never touching source code directly. Changes flow through automated validation and human approval before landing in the codebase. ``` QUEUED ──→ IN_PROGRESS ──→ REVIEW ──→ DONE │ │ (gate fail) (reject/test fail)
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------