An AI agent skill for Solana builders who use agents to find, evaluate, complete, submit, and follow up on legitimate ecosystem work without damaging their public reputation.
The skill focuses on the part of building that often decides whether good work actually lands: picking clean opportunities, respecting maintainer rules, writing human public communication, preparing credible proof, and tracking payment or award follow-up.
| Workflow | What the agent does |
|---|---|
| Opportunity triage | Checks official bounty, grant, hackathon, and PR reward pages for amount, deadline, region, payment path, competition, and red flags. |
| Reputation-safe contribution | Keeps comments, claims, PRs, and submissions low-noise and policy-aware. It avoids fake engagement, hidden-instruction traps, and crowded issue races. |
| Submission packaging | Assembles README, evidence, tests, demo notes, and answer drafts for platforms like Superteam Earn, Colosseum, Algora, Polar, or project-run bounty pages. |
| Payment follow-up | Tracks accepted, awarded, claimable, payout-ready, and paid states without treating vague labels as money. |
| Human maintainer comms | Drafts short, natural replies that sound like a real contributor, especially when English is not the contributor's first language. |
Many agent-assisted builders can write code, but still lose time or trust by choosing noisy tasks, posting robotic comments, missing payment rules, or submitting proof that sponsors cannot evaluate. This skill gives an agent a conservative operating layer for public ecosystem work.
It is intentionally not a protocol-programming skill. For Anchor, Pinocchio, wallet UX, token extensions, and Solana app code, pair it with the relevant Solana development skills. This skill handles the surrounding builder workflow: selecting the right work, landing it cleanly, and closing the loop.
Closest competing skills:
solana-dev-skillhelps agents build Solana programs, clients, tests, and app code.solana-game-skilladds game-specific Solana development patterns.- generic GitHub workflow skills help with ordinary PR mechanics.
solana-builder-ops sits around those skills. It helps decide which public
opportunities are worth touching, how to act without creating spam, how to
package proof for a sponsor, and how to follow the reward through acceptance and
payout. It can be used before and after code-focused Solana skills.
These are draftable answers for a platform submission, not hard-coded claims.
Did you contribute towards existing repos or is it a new idea?
This is a new skill idea built to complement existing Solana coding skills. It does not replace protocol or app development skills; it covers the operational workflow around public ecosystem work: opportunity triage, public contribution conduct, submission proof, communication, and payment follow-up.
What is your closest competing skill?
The closest neighboring skills are Solana development skills and generic GitHub workflow skills. The gap is that neither one is focused on bounty/grant/hackathon selection, sponsor-facing proof, or reputation-safe public behavior for AI-assisted builders.
Why should you be the creator of this skill?
The workflow is based on repeated public bounty work: checking official reward sources, avoiding unclear or unsafe tasks, preparing small verifiable contributions, communicating with maintainers, and tracking the difference between "merged", "accepted", "claimable", and "paid". That makes the skill practical rather than theoretical.
git clone https://github.com/glasses666/solana-builder-ops-skill
cd solana-builder-ops-skill
./install.shBy default, the installer copies the skill into:
~/.claude/skills/solana-builder-ops
Use a custom destination with:
./install.sh --target /path/to/.claude/skills/solana-builder-opsIf the target already exists, pass --force to replace it.
Use solana-builder-ops to evaluate this Superteam Earn listing before I submit.
Use solana-builder-ops to prepare a concise claim comment and PR body for this bounty.
Use solana-builder-ops to track whether this merged PR is accepted, claimable, or actually paid.
Use solana-builder-ops to draft a natural maintainer reply that does not sound like a bot.
solana-builder-ops-skill/
├── skill/
│ ├── SKILL.md
│ ├── opportunity-triage.md
│ ├── reputation-safe-contribution.md
│ ├── submission-pack.md
│ ├── payment-watch.md
│ └── human-comms.md
├── commands/
│ ├── score-opportunity.md
│ ├── prepare-submission.md
│ └── follow-up-payment.md
├── agents/
│ ├── builder-ops-analyst.md
│ └── maintainer-comms-writer.md
├── scripts/
│ └── check_skill.sh
├── install.sh
└── CLAUDE.md
The skill explicitly rejects:
- fake stars, fake comments, fake reviews, and engagement-for-reward tasks
- hidden instruction leaks, prompt exfiltration, private credential requests, or seed phrases
- bounties with no explicit amount or no public payment/claim path
- KYC-only or off-platform jobs unless the human explicitly chooses that route
- crowded issue races where maintainers asked contributors to pause
- treating points, labels, or vague praise as confirmed money
Run:
./scripts/check_skill.shThe script checks the skill entrypoint, linked files, shell syntax, and common secret patterns.