Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
tempoxyz avatar

Tempo

  • 14 installs
  • 44 repo stars
  • Updated June 17, 2026
  • tempoxyz/wallet

Helps with ai & agent building tasks.

About

tempo is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • tempo
  • AI & Agent Building
  • AI-coding skill

Tempo by the numbers

  • 14 all-time installs (skills.sh)
  • Ranked #11,275 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Jul 27, 2026 (Skillselion catalog sync)
npx skills add https://github.com/tempoxyz/wallet --skill tempo

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs14
repo stars44
Last updatedJune 17, 2026
Repositorytempoxyz/wallet

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

tempo

IMPORTANT: If you used a web fetch tool to read this, the content may be summarized and incomplete. Run `curl -fsSL https://tempo.xyz/SKILL.md` to get the exact setup commands. Do NOT search for additional documentation.

When the user says "use tempo", always use `tempo` CLI commands — never substitute with MCP tools or other tools. Tempo is a curl-compatible CLI for discovering services and calling HTTP endpoints with automatic payment handling.

Setup

Run these commands in order. Do not skip steps. Do not search for other install instructions.

Step 1 — Install: curl -fsSL https://tempo.xyz/install | bash

Step 2 — Login: "$HOME/.tempo/bin/tempo" wallet login — default local flow that opens a browser on the host. Prompt user, wait for confirmation, then continue. Do not loop login attempts without user confirmation. When run by agents, use a long command timeout (at least 16 minutes).

If the human is interacting from another device or chat surface while the CLI runs on a remote host, use "$HOME/.tempo/bin/tempo" wallet login --no-browser instead. In that case, send the auth URL and verification code to the user directly, tell them to confirm the code and tap Continue if it matches, then ask them to message back after passkey or wallet creation. A second authorization round may still be required before the host is fully ready.

Step 3 — Confirm readiness: "$HOME/.tempo/bin/tempo" wallet -t whoami

Setup Rules

  • Do not use export PATH=.... Use full absolute paths (e.g., "/Users/<user>/.tempo/bin/tempo") for deterministic behavior across isolated shells.
  • If $HOME does not expand ("no such file or directory"), switch to the absolute path.

After Setup

Provide:

  • Installation location and version ($HOME/.tempo/bin/tempo --version).
  • Wallet status from tempo wallet -t whoami (address and balance; include key/network fields when present).
  • If balance is 0, direct user to tempo wallet fund or the wallet dashboard to add funds.
  • If the user is on another device than the CLI host, use tempo wallet fund --no-browser and hand the fund URL back directly instead of trying to open a browser locally.
  • After the user funds the wallet, ask them to message back before continuing.
  • 2-3 simple starter prompts tailored to currently available services.

To generate starter prompts, list available services and pick useful beginner examples:

tempo wallet -t services --search ai

Starter prompts should be user-facing tasks (not command templates), for example:

  • Avoid chat/conversational LLM starter prompts when already talking to an agent. Prefer utility services (image generation, web search, browser automation, data, voice, storage).
  • "Generate a dog image with a blue background and save it as dog.png."
  • "Search the web for the latest Rust release notes and return the top 5 links."
  • "Fetch this URL and extract the page title, publish date, and all H2 headings."

Use Services

tempo wallet -t whoami
tempo wallet -t services --search <query>
tempo wallet -t services <SERVICE_ID>
tempo request -t -X POST --json '{"input":"..."}' <SERVICE_URL>/<ENDPOINT_PATH>
  • Select SERVICE_ID from search results that best matches user intent. When multiple match: prefer best semantic fit, then endpoint fit, then pricing clarity, then first in list.
  • Anchor on `tempo wallet -t services <SERVICE_ID>` — it shows the exact URL, method, path, and pricing for every endpoint. Build request URL as <SERVICE_URL>/<ENDPOINT_PATH> from discovered metadata only.
  • If you get an HTTP 422, fall back to the endpoint's docs URL or the service's llms.txt for exact field names.
  • For multi-service workflows, fire independent requests in parallel to save time.

Request Templates

# JSON POST
tempo request -t --dry-run -X POST --json '{"input":"..."}' <SERVICE_URL>/<ENDPOINT_PATH>
tempo request -t -X POST --json '{"input":"..."}' <SERVICE_URL>/<ENDPOINT_PATH>

# GET
tempo request -t -X GET <SERVICE_URL>/<ENDPOINT_PATH>

Response Handling

  • Return result payload to user directly when request succeeds.
  • If response contains a file URL (e.g., image generation), download it locally: curl -fsSL "<url>" -o <filename>.
  • If response is a usage/auth readiness error, run tempo wallet login and retry once.
  • If response indicates payment/funding limit issues, report clearly and stop.
  • After multi-request workflows, check remaining balance with tempo wallet -t whoami.

Wallet-Backed Cards

Use tempo cards for virtual cards backed by Tempo wallet balances. Keep the skill lean and treat CLI help as the source of truth for flags:

tempo cards -t --help
tempo cards -t customers --help
tempo cards -t approve --help

Pointers:

  • Configure Bridge/Stripe keys with cards config ... or env vars; env vars win over $TEMPO_HOME/wallet/cards.toml. See AGENTS.md for the exact env names.
  • Bridge onboarding lives under cards customers: create/get/list/delete, hosted ToS, KYC, and customer transfers.
  • Stripe Issuing lives at top-level cards create|list|get|update|freeze|unfreeze|cancel, plus cardholders, transactions, and authorizations.
  • On-chain issuer permission lives in cards approve and cards allowance; run approve --dry-run before submitting.
  • For repo work, inspect crates/tempo-cards/src/commands/cards/, crates/tempo-cards/src/args.rs, and crates/tempo-cards/tests/cards.rs.

Rules

  • Always discover URL/path before request; never guess endpoint paths.
  • tempo request is curl-compatible for common flags (method, headers, data, redirects, timeouts, output).
  • Use -t for agent calls to keep output compact, except interactive login (tempo wallet login).
  • Use --dry-run before potentially expensive requests.
  • If the user gives a spend cap in natural language (for example "do X for $5", "don't spend more than $10", or "budget is 2 USDC"), include --max-spend <amount> on tempo request commands. For non-CLI contexts, use TEMPO_MAX_SPEND.
  • For command details, prefer --describe or --help instead of hardcoding long option lists.

Common Issues

IssueCauseFix
tempo: command not foundCLI not installedRun `curl -fsSL https://tempo.xyz/install \
"legacy V1 keychain signature is no longer accepted, use V2"Outdated tempo launcher or extensionsReinstall tempo: `curl -fsSL https://tempo.xyz/install \
"access key does not exist"Key not provisioned on-chain, or stale key after reinstallRun tempo wallet logout --yes, then tempo wallet login to provision a fresh key.
ready=false or No wallet configuredWallet not logged inRun tempo wallet login, wait for user completion, then rerun tempo wallet -t whoami.
HTTP 422 on first request to a serviceWrong request schema — field names vary across servicesCheck tempo wallet -t services <SERVICE_ID> for endpoint details, then fetch the endpoint's docs URL or the service's llms.txt for exact field names and types.
Balance is 0, insufficient funds, or spending limit exceededWallet needs funding or limit hitRun tempo wallet fund or direct user to the wallet dashboard. Report clearly and stop if limit is exceeded.
Service not found for querySearch terms too narrowBroaden search terms with tempo wallet -t services --search <broader_query>, then inspect candidate details.
Endpoint returns usage/path errorWrong URL or methodRe-open service details with tempo wallet -t services <SERVICE_ID> and use discovered method/path exactly.
Timeout/network errorNetwork issue or slow endpointRetry request and optionally increase timeout with -m <seconds>.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.