internet-court/internet-court-skill / vendored/altlayer/altllm-portal-auth
altllm-portal-auth
VerifiedUse this skill when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login for the local altllm CLI. Do NOT use for API key management, billing history, or payment links.
AltLLM Portal Auth
Wallet login and session bootstrap for the local altllm CLI, including external signers such as Privy.
Shared Setup
Before the first
altllmcommand in a fresh checkout, read and follow:
../_shared/preflight.md../_shared/session-and-target.md
Command Index
| Command | Purpose |
|---|---|
login-wallet --private-key-env <name> | Sign in with a locally available private key from an environment variable |
login-wallet --private-key-file <path> | Sign in with a locally available private key from a file |
login-wallet --private-key <hex> --allow-unsafe-private-key-argv | Sign in with an inline private key when argv exposure is explicitly accepted |
login-wallet --prepare | Fetch a challenge for external signing |
login-wallet --nonce <nonce> --signature <sig> | Verify an externally signed challenge and save the session |
status | Show saved Portal session user and target URL status without exposing the token |
logout | Remove the local saved Portal session file |
Rules
- Do not assume the CLI must control the wallet private key.
- If the wallet can sign the challenge message, use the prepare + verify flow.
- External signers such as Privy are valid as long as they return a standard wallet signature for the challenge.
- If neither a local private key nor
--signatureis available, return the challenge payload and stop. - Before local auto-signing, validate that the returned challenge matches the requested wallet, chain, and expected AltLLM login challenge structure.
- For non-default, non-loopback API hosts, prefer
--prepareand external signing instead of local auto-signing. - Current backend support is still limited to EVM addresses and Ethereum-style signatures.
- Save the resulting session to
~/.altllm/portal-cli-session.jsonunless overridden. - Use
statusor itswhoamialias to confirm the saved user and target URL before running live commands. logoutonly removes the local session file. It does not revoke API keys.
Reference
See references/cli-reference.md for commands, payloads, and troubleshooting notes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |