Skip to content
cccskills
FreePublished on GitHub

find-stellar-idea

Help users discover what to build on Stellar. Use when a user says "what should I build on Stellar", "Stellar app ideas", "I want to build on Stellar but don't know what", "Stellar startup ideas", "find me a Stellar project idea", "I'm new to Stellar and want to build something", or "what's hot on Stellar right now". Interviews user sharply, then proposes ranked ideas grounded in real ecosystem gaps from the LumenLoop 728-project database and current SCF funding patterns.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md4.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

What this skill does

When invoked, do these four things in order.

1. Load context

Read both Stellar-specific data and broader crypto market signals. The combination matters: ideas that fit a Stellar ecosystem gap and align with broader investor thesis (a16z, YC, Alliance) are both ecosystem-coherent and fundable.

Stellar-specific:

  • ~/.claude/skills/data/lumenloop/projects.json — 728-project Stellar ecosystem catalog with categories, SCF funding history, GitHub links
  • ~/.claude/skills/data/electric-capital/stellar-repos.json — Stellar developer activity signal (~9000 repos). Use it to detect ecosystem velocity: count repos created or actively maintained in each category, identify orgs with multiple Stellar repos (likely serious builders), filter out bootcamp exercises (whitebelt, orangebelt, yellowbelt in the repo name) and student forks to get a clean signal of who's actually shipping. If the user picks a domain where velocity is high but LumenLoop catalog coverage is low, that's a "builders are here but undocumented" signal — strong place to enter.
  • ~/.claude/skills/data/lumenloop/scf/rounds.json — historical SCF funding patterns (categories funded, average grant size)

Broader crypto market signals:

  • ~/.claude/skills/data/ideas/a16z-big-ideas-2025.json — a16z's published "big ideas" thesis for 2025
  • ~/.claude/skills/data/ideas/a16z-state-of-crypto-2025.json — a16z's annual State of Crypto report
  • ~/.claude/skills/data/ideas/yc-requests-for-startups.json — YC's published Request for Startups list (what YC explicitly wants funded)
  • ~/.claude/skills/data/ideas/yc-crypto-companies.json — every YC-backed crypto company (competitive map + signal of what gets funded)
  • ~/.claude/skills/data/ideas/alliance-ideas.json — Alliance DAO's startup ideas

If any file is missing, proceed but note "(limited context — install fresh data with --update)".

2. Ask three sharp questions, one at a time

Wait for each answer before asking the next:

  1. Which Stellar domain pulls you? — payments, DeFi, stablecoins, RWA (real-world assets), DePIN, consumer apps, dev infrastructure, anchors, agentic payments, or something else.
  2. What's your timeline? — weekend hack, one month, one quarter, longer.
  3. What's your unfair advantage? — domain expertise, technical skill, distribution, network, capital. What do you have that most builders don't?

3. Propose three ranked ideas

For each idea, write:

  • One-line pitch. What it is, who it's for.
  • Why Stellar specifically. What Stellar capability (Soroban, anchors, low fees, native multi-currency, agentic payments, fast finality) makes this work better on Stellar than on another chain.
  • Ecosystem gap evidence. Cite from projects.json: what's already in this category and at what SCF funding levels, what's not.
  • Broader thesis fit. If the idea aligns with an a16z thesis, a YC RFS line item, or an Alliance DAO area, cite it. If it doesn't, say so plainly — Stellar-specific ideas without broader investor thesis can still be great, but the user should know.
  • Why it might fail. The single biggest risk.
  • First step. Smallest concrete thing they could do tomorrow.
  • SCF fit. Likely yes / no / maybe to receive SCF funding, based on recent round patterns.

Order: best fit for their constraints first; most ambitious last.

4. Close

End with: "Pick one to refine, or tell me what's missing and I'll regenerate. If you like one, I can route you to validate-stellar-idea or stellar-competitive-landscape next."

Constraints

  • Do not propose ideas requiring capital they didn't mention
  • Do not propose ideas outside their stated domain
  • Each idea must be specific enough to start tomorrow — not "build a social network"
  • If projects.json shows 5+ funded projects already doing this exact thing, either propose a clear differentiation angle or move on
  • If they pick "agentic payments" or "ZK proofs," lean into Stellar's recent capability investments — these are intentionally underbuilt and SCF is funding them heavily

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

The English summary is being prepared. Showing the original description.

stellar-zk/stellar-zk4Updated Oct 21, 2026

Agentic and machine-to-machine payments on Stellar. Covers x402 (HTTP 402 paid APIs via OZ Channels facilitator, fee-sponsored clients) and MPP (Machine Payments Protocol) in both Charge mode (per-request SAC) and Channel mode (off-chain commits, high-frequency). Defaults to USDC (SEP-41 SAC) on `stellar:testnet`/`stellar:pubnet` (CAIP-2). Use when selling a paid API to AI agents, building an x402 client, or designing a payment-channel architecture for high-frequency agent traffic.

The English summary is being prepared. Showing the original description.

stellar-zk/stellar-zk4Updated Oct 21, 2026

assets

Free

Stellar Assets (classic) + trustlines + Stellar Asset Contract (SAC) bridge to smart contracts. Covers asset issuance, distribution, authorization flags, clawback, regulated assets, trustline management, and the SAC interop layer that exposes classic assets as SEP-41 contract tokens. Use when tokenizing real-world assets, issuing stablecoins, managing trustlines, or bridging classic assets to smart contracts.

The English summary is being prepared. Showing the original description.

stellar-zk/stellar-zk4Updated Oct 21, 2026

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.

The English summary is being prepared. Showing the original description.

stellar-zk/stellar-zk4Updated Oct 21, 2026

Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.

The English summary is being prepared. Showing the original description.

stellar-zk/stellar-zk4Updated Oct 21, 2026

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

The English summary is being prepared. Showing the original description.

stellar-zk/stellar-zk4Updated Oct 21, 2026

See all skills by stellar-zk

Report a problem with this skill