AGENT SKILL

reprompt

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.

License 许可
MIT
所属仓库
ozioziel/Workville
最近更新
2026-11-11
Stars
★ 3
Forks
0

01 前言 Front Matter

name
reprompt
description
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.

03 SKILL.md 正文

What this skill does

Turns a rough ask into a tight working spec, then acts on it — the explicit, on-demand counterpart to the loop's automatic per-turn sharpener. Use it when a request is vague enough to be worth structuring out loud, or when the user literally asks you to "reprompt this".

How to run it

1. Capture the raw request

Take the text the user wants sharpened (everything after "reprompt this:", or the preceding message if they just say "reprompt that").

2. Load any learned profile

If ~/.stellar/profile.md exists (the optimizer distills it from real usage), read it and treat it as defaults — domain, typical scope, preferred stack, tone — unless the request contradicts them. Honor STELLAR_HOME if set.

3. Produce the sharpened spec

Rewrite the request into this structure. Keep it tight; don't pad.

Goal:        the outcome actually wanted (not the literal words)
Context:     relevant assumptions, environment, prior decisions
Task:        the smallest precise action(s) that achieve the goal
Constraints: scope limits, must-nots, non-negotiables
Success:     how we'll know it's done right

4. Gate on ambiguity

If a genuine ambiguity would change the result, ask 1–3 sharp questions first (one at a time) and fill the spec from the answers. If it's clear enough, proceed directly.

5. Act

Show the sharpened spec briefly, then execute on it (or hand off to the right stellar-build skill — e.g. find-stellar-idea, nicole-pm, tyler-architect). Don't make the user re-approve unless a clarifying answer is still pending.

Notes

  • This is the manual lever. The automatic version runs every turn via the UserPromptSubmit hook and needs no invocation; turn it off with STELLAR_BUILD_NO_REPROMPT=1.
  • The more you use stellar-build, the better both get: /optimize-skills refreshes ~/.stellar/profile.md from your traces, which feeds these rewrites.

04 同仓库更多 Skills

ozioziel
ozioziel/Workville

zk-proofs

Zero-knowledge proofs and privacy patterns on Stellar. Covers Groth16 verification in smart contracts via BLS12-381 host functions (CAP-0059, available), the BN254 + Poseidon proposals (CAP-0074/0075, status-sensitive), and concrete toolchain walkthroughs for Circom (on-chain verifiable today), Noir, and RISC Zero (attestation pattern until BN254 lands). Use when building privacy-preserving applications, ZK-verifier contracts, or wiring a proving toolchain to Stellar.

★ 3
ozioziel
ozioziel/Workville

tyler-architect

System architect and technical design leader. Use when the user asks to talk to Tyler or requests the architect.

★ 3
ozioziel
ozioziel/Workville

stellar-help

Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.

★ 3
ozioziel
ozioziel/Workville

stellar-competitive-landscape

Map the competitive landscape for a Stellar project idea. Use when a user says "who are my competitors on Stellar", "competitive analysis Stellar", "what already exists in this space on Stellar", "show me similar Stellar projects", "is anyone else building this on Stellar", "map the Stellar landscape for X" — or the Spanish/mixed-language equivalents, e.g. "cual es la competencia de X", "que tan saturado está este espacio", "que aspectos están menos explorados y la SDF/SCF están dispuestos a fondear", or "analiza la competencia de estos bounties". Also fires when a user (directly, or via a BMAD persona like justin-analyst) names a specific protocol/idea inline and asks about its competition, viability, or market whitespace — including "should we integrate [external protocol]" or "does anything like this already exist on Stellar" research, where the deliverable is the same landscape map applied to a build-vs-integrate decision. Queries the 728-project LumenLoop ecosystem database and Electric Capital developer activity to rank competitors by SCF funding history and repo activity.

★ 3
ozioziel
ozioziel/Workville

standards

Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits/withdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects), curated documentation links, and MCP servers (live tools such as Raven). Use when you need to know which SEP applies, or want a starting point for ecosystem integrations, official docs, or live MCP tooling.

★ 3
ozioziel
ozioziel/Workville

smart-contracts

Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory — development.md (storage/TTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, reviewing, securing, debugging, or shipping Stellar smart contracts, including anything the user calls "Soroban" — Soroban contracts, soroban-sdk, Soroban auth/storage/TTL errors, SEP-41 tokens, or SAC integration from contract code.

★ 3