Altllm Portal Auth Agent Skill

Use 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.

2k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

1529

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/internet-court/internet-court-skill --skill altllm-portal-auth

What comes with it

3 880 bytes besides the instruction

LICENSE

references/cli-reference.md

The instruction itself

5 sections, as written by the author

AltLLM Portal Auth

Wallet login and session bootstrap for the local altllm CLI, including external signers such as Privy.

Shared Setup

> Before the first altllm command 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 --signature is 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 --prepare and 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.json unless overridden.
Use status or its whoami alias to confirm the saved user and target URL before running live commands.
logout only removes the local session file. It does not revoke API keys.

Reference

See references/cli-reference.md for commands, payloads, and troubleshooting notes.

Other skills for the same job

different authors, same section of the catalogue

Edgartools

by christophacham

×2

Python library for accessing, analyzing, and extracting data from SEC EDGAR filings. Use when working with SEC filings, financial statements (income statement, balance sheet, cash flow), XBRL financial data, insider trading (Form 4), institutional holdings (13F), company financials, annual/quarterly reports (10-K, 10-Q), proxy statements (DEF 14A), 8-K current events, company screening by ticker/CIK/industry, multi-period financial analysis, or any SEC regulatory filings.

Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences.

2k tokens

Spec To Code Compliance

by christophacham

×1

Verifies code implements exactly what documentation specifies for blockchain audits. Use when comparing code against whitepapers, finding gaps between specs and implementation, or performing compliance checks for protocol implementations.

Architecture Reference

by ComeOnOliver

×1

Quick reference for Portfolio Buddy 2 project structure. Use when: adding new features, modifying existing components, understanding data flow, or onboarding to the codebase. Contains component hierarchy, hook patterns, and utility functions.

CCXT cryptocurrency trading library. Use for cryptocurrency exchange APIs, trading, market data, order management, and crypto trading automation across 150+ exchanges. Supports JavaScript/Python/PHP.

52k tokens

Generating Solana Projects

by ComeOnOliver

×1

Generates complete Solana blockchain projects with Anchor framework (v0.32.1) and Next.js frontend including Rust smart contracts, tests, and wallet integration. Use when creating Solana dApps, NFT marketplaces, token programs, DAOs, DeFi protocols, or when user mentions Solana, Anchor, or blockchain projects.

9k tokens

X402

by browser-use

Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or "build it in" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.

4k tokens

How to use it

Copy the folder

Take internet-court/altllm-portal-auth from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.