kaankacar

Benchmark stellar-build skills to measure quality and the lift from optimization. Use when the user says "bench my skills", "bench-skills", "benchmark skills", "did optimization help", "measure my skills", "stellar-loop bench", or wants to quantify whether /optimize-skills actually improved things. Held-out eval prompts scored by an LLM judge, reproducible with fixed seeds. Fully local.

Explain and control the stellar-build learning loop — the system that improves your skills from how you use them. Use when the user says "learning loop", "how does the learning loop work", "what is the learning loop", "self-improving skills", "stellar-loop", "show my skill usage", "is tracing on", or wants an overview / status of the local trace-capture + optimize + bench cycle.

Compile your local stellar-build usage traces into sharper skills. Use when the user says "optimize my skills", "optimize-skills", "improve my skills from usage", "learn from my traces", "stellar-loop optimize", or wants the learning loop to refine installed skills based on how they've actually been used. DSPy-style prompt optimization over the local trace store at ~/.stellar/traces — fully local, reversible.

Rewrite a rough request into a sharp, structured prompt before acting on it. Use when the user says "reprompt this", "reprompt", "improve this prompt", "make this prompt better", "structure this request", or hands you a vague/underspecified ask you should sharpen first. Complements the automatic per-turn sharpener (the UserPromptSubmit hook) for explicit, heavier rewrites. Personalizes from ~/.stellar/profile.md when present.

Senior software engineer for story execution and code implementation. Use when the user asks to talk to Elliot or requests the developer agent.

Strategic business analyst and requirements expert. Use when the user asks to talk to Justin or requests the business analyst.

Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.

Technical documentation specialist and knowledge curator. Use when the user asks to talk to Bri or requests the tech writer.

Drive the Stellar / Soroban network from any AI agent (Hermes, OpenClaw, Claude Code, Cursor) using the @stellar-agent-kit npm package or its MCP server. Use when the user asks about sending XLM/USDC, trustlines, swaps (Soroswap), lending (Blend), token issuance, Soroban contracts, fiat on/off-ramps (anchors), or building a Stellar-aware AI agent.

Build a SAFE autonomous Stellar agent with @stellar-agent-kit/runner. Covers layered defence (network sandbox, action allowlist, spend caps, human-in-loop, smart-account policies), free OpenRouter LLM setup with NVIDIA Nemotron, cron-style runOnce for resumable scheduled agents, and how to verify each safety layer with tests. Use when building autonomous bots that move money on Stellar.

Build a Mexican-peso ↔ USDC/CETES remittance flow on Stellar via Etherfuse SPEI on/off-ramps. Covers KYC handling, customer-id permanence gotcha, testnet vs mainnet URLs, and the on-chain swap step. Use when building MXN remittance, payout-to-bank, or USDC-from-pesos flows.

Turn an HTTP API into an x402-paid endpoint that AI agents can buy from on Stellar (USDC settlement, ~5s finality, sub-cent fees, zero-XLM clients). Or, write an agent that pays for x402-paywalled APIs. Covers seller (@x402/express) and buyer (@stellar-agent-kit/plugin-payments) sides plus testnet runbook.

Work through the issues assigned to the user on the stellar/stellar-dev-skill repo (the AI-skills repo behind skills.stellar.org): find the open issues assigned to them, pick one (or go oldest-first), understand what it asks, create a branch, implement a best-effort fix following the repo's conventions — skill content, site code, or catalog cards — verify it (Raven fact-checks, compile checks, pnpm build), commit, and automatically open a PR that links the issue and flags any assumptions — then hand the new PR to the stellar-dev-skill-pr-review skill for review. Use whenever the user asks you to work on / solve / fix / clear the issues assigned to them on stellar-dev-skill, or turn a specific stellar-dev-skill issue into a PR. This is the write-and-open-PR counterpart to stellar-dev-skill-pr-review (which only reviews existing PRs). Do NOT use for reviewing/merging PRs, for stellar/stellar-docs (that's stellar-docs-issue-solver), or for issues that need a product/design decision rather than a change you can i

Review pull requests on the stellar/stellar-dev-skill repo (the AI-skills repo behind skills.stellar.org) as a maintainer would. Works two ways: given a specific PR URL/number, evaluate just that one; or given no specific PR, find every PR awaiting the user's review and work through them one at a time. For each PR: pull context, classify what it touches (skill content, site code, ecosystem cards, CI), verify it the right way for that class (Raven fact-checks, compile-against-real- crates, pnpm build, preview or local render), then approve + merge when confident, comment and hand off when something needs a human, or close duplicates — giving a very short report after each PR before the next. Use whenever the user pastes a stellar-dev-skill PR link, or asks you to review/triage/clear the PRs waiting on them on stellar-dev-skill or skills.stellar.org. Do NOT use for stellar/stellar-docs (that's stellar-docs-pr-review), for writing new skills, or for opening PRs from issues (that's stellar-dev-skill-issue-solver)

Work through the issues assigned to the user on the stellar/stellar-docs repo: find the open issues assigned to them, pick one (or go oldest-first), understand what it asks, create a branch, implement a best-effort docs fix following the repo's conventions, verify it, commit, and automatically open a PR that links the issue and flags any assumptions — then hand the new PR to the stellar-docs-pr-review skill for preview testing. Use whenever the user asks you to work on / solve / fix / clear the issues assigned to them on stellar-docs, "take a look at my issues," or turn a specific stellar-docs issue into a PR. This is the write-and-open-PR counterpart to stellar-docs-pr-review (which only reviews existing PRs). Do NOT use for reviewing/merging PRs (use stellar-docs-pr-review), for non-stellar-docs repos, or for issues that require a product/design decision rather than a docs change.

Review pull requests on the stellar/stellar-docs repo as a maintainer would. Works two ways: given a specific PR URL/number, evaluate just that one; or given no specific PR, find every PR awaiting the user's review and work through them one at a time. For each PR: pull context, read the repo's contribution guidance, test what it changes on its Kube preview build (pagination, sidebar labels, breadcrumbs, page parity vs production), verify factual/Stellar claims with the Raven MCP, then approve + merge when confident, comment and hand off when something needs a human, or close it when it's a duplicate — giving a very short report after each PR before the next. Use whenever the user pastes a stellar-docs PR link, or asks you to review/triage/clear the PRs waiting on them, work their review queue, or look at what's waiting for them on stellar-docs. Do NOT use for writing new docs content, for non-stellar-docs repos, or for opening PRs from issues.

Survive on Stellar. Kill agents. Earn XLM.

Interactive guide for creating new Claude Code skills. Walks the user through use case definition, frontmatter generation, instruction writing, folder structure setup, and validation. Use when user says "create a skill", "build a skill", "new skill", "make a skill", "skill-creator", or asks to "scaffold a skill", "generate SKILL.md", or "help me write a skill".

Autonomous crypto trading for AI agents on Stellar with portfolio management, correlation analysis, tax-loss harvesting, Sharpe optimization, AI-powered trading signals, institutional features including multi-sig wallets, sub-accounts, compliance reporting, and asset policies. Execute trades across 3+ pools, split large orders for optimal execution. Now with WASM hot path, flash loan arbitrage, transaction bundling, comprehensive portfolio analytics, and enterprise-grade security.

End-to-end Stellar development playbook (Jan 2026). Covers Soroban smart contracts (Rust SDK), Stellar CLI, JavaScript/Python/Go SDKs for client apps, Stellar RPC (preferred) and Horizon API (legacy), Stellar Assets vs Soroban tokens (SAC bridge), wallet integration (Freighter, Stellar Wallets Kit), smart accounts with passkeys, testing strategies, security patterns, and common pitfalls. Optimized for payments, asset tokenization, DeFi, and financial applications.