Results for “api-token”

Use when working with API keys, credentials, tokens, certificates, or any sensitive configuration. This skill provides procedures for securely handling secrets throughout their lifecycle - from identification to storage, usage, rotation, and revocation.

Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices. Use when: plaid, bank account linking, bank connection, ach, account aggregation.

OpenClaw API gateway proxy for authenticated SaaS calls (100+ services in references/SERVICES.md). Use ONLY when making an HTTP request to a third-party service that requires the gateway's stored credentials. NOT for direct API calls with bearer tokens already in scope, NOT for monday.com (use monday-for-agents), NOT for WhatsApp (use heleni-whatsapp). Triggers: "call the X API", "fetch from <service>", "send to Slack via gateway", "use the gateway for".

Query Solana blockchain data with USD pricing — wallet balances, token portfolios with values, transaction details, NFTs, whale detection, and live network stats. Uses Solana RPC + CoinGecko. No API key required.

Perform reconnaissance, persistence, privilege escalation, and data pillaging on Microsoft 365/Entra ID tenants via the Microsoft Graph API using the GraphRunner PowerShell toolset.

Execute AEM Edge Delivery Services admin operations: manage content, cache, code, indexes, sitemaps, snapshots, logs, users, jobs, sites, config, secrets, API keys, tokens, profiles, and versioning. Also supports Document Authoring operations.

Access blockchain RPC endpoints via Quicknode to read onchain data including balances, token prices, transaction status, gas estimates, and block data across Base, Ethereum, Polygon, Solana, and Unichain. Supports both API key and x402 wallet-based pay-per-request access.

Interact with GitHub via the `gh` CLI. Use for issues (read, comment, file), pull requests (view, comment, check CI status), workflow runs, and `gh api` for queries the subcommands don't cover. Authentication is via the bot's GITHUB_TOKEN (already wired through `gh auth setup-git` at container start).

This skill should be used when the user asks to "create an index", "build a basket of top assets", "buy a weighted basket", "make a portfolio of assets", "equal-weight basket", "rebalance my portfolio", "track the top N tokens", or wants an automated, weighted multi-asset basket that buys in one pass and rebalances on a cadence. Builds the basket spec, delegates each buy and rebalance swap to the swap-integration Trading API flow, and records target weights in state.

Greenfield development path for products, tools, and systems that do not yet exist. G Stack validates the idea before anything is planned or built. Use when starting from zero: no existing codebase, no existing schema, no existing API that this extends. AUTO-FIRE immediately when the user says any of: - "new development", "/new-development [description]" - "I have an idea for [X]", "I want to build [X] from scratch" - "new product", "new tool", "new platform", "new application" - "build [X] — it doesn't exist yet", "start a new project" Do NOT use when an existing codebase already exists for the work — use /full-development for large brownfield work. If unsure: ask "Does any part of this already exist in code?" If yes → /full-development. This is the most token-intensive command. Use it when the investment is justified by the scope of what is being built.