Discover Blockchain skills, compare source repositories and read the instructions for each workflow.
SOP for creating and configuring SPL tokens: mint creation, authorities, decimals, freeze/mint revoke flows, multisig custody, and validation steps. Use for new token setup or authority changes.
End-to-end pre-flight checklist for launching a Solana token/app: infra, wallets, liquidity, comms, security, and rollback planning. Use before mainnet launch or major release.
Implement Token-2022 (Token Extensions) features - transfer fees, permanent delegate, metadata pointer, confidential transfers, and more. Use when creating advanced tokens or analyzing Token-2022 tokens.
How to project legitimacy for Solana projects: disclosures, address registry, audits, comms patterns, red-flag avoidance. Use for project pages, announcements, and community trust work.
Comprehensive rug detection for Solana tokens - red flags, contract analysis, LP verification, insider patterns, and escape routes. Use before buying any token to protect against scams.
Design transaction signing UX on Solana: pending/confirmed states, retries, fee prompts, and error messaging. Use when building tx flows.
Stabilize a token/dApp after launch: monitoring, comms, liquidity adjustments, and product milestones. Use during first 72 hours and beyond.
Track and analyze whale wallets on Solana - identify smart money, cluster related wallets, detect accumulation/distribution patterns, and filter signal from noise. Use for alpha generation and risk assessment.
Templates for Solana launch announcements: X threads, pinned TG messages, FAQs with addresses and disclosures. Use for Day 0 comms.
Integrate Jupiter aggregator for swaps - API usage, route optimization, slippage handling, and frontend/bot implementation. Use when building swap UIs or trading bots.
Monitoring plan for Solana apps: RPC health, tx success, program errors, and liquidity signals. Use to set up dashboards and alerts.
Master Jito bundles for MEV protection and priority fee optimization on Solana - bundle submission, tip strategies, and transaction landing. Use for trading bots, high-priority transactions, and MEV-aware appli...
Runbook for token operations after launch: treasury moves, unlock communications, LP adjustments, and monitoring. Use for weeks 1�4 post launch.
Troubleshoot frequent Anchor runtime errors: discriminator mismatch, constraint failures, account deserialization, and CPI issues. Use when tests or txs fail with Anchor errors.
Operational patterns for fair token launches: definitions, mechanics, tradeoffs, and execution steps. Use when planning fair/transparent launches.
Explain Solana AMM liquidity, slippage, volatility, and LP mechanics for tokens. Use to brief teams or design initial liquidity.
Scaffold and install codex-ui-kit assets and optional prompts in a repo. Use when adding codex-ui-kit to a project.
Use the @steipete/oracle CLI to bundle a prompt plus the right files and get a peer-model review (API or browser) for debugging, refactors, design checks, or cross-validation. Use this when you need a peer-mode...
Primary instruction manual for working within the ancplua-claude-plugins monorepo. Use when creating, modifying, or debugging plugins in this repository.
Detect new imports in modified files and auto-install missing dependencies. Works with npm, uv, pip, cargo, go mod, and other package managers. Triggers after code implementation to keep manifests in sync.
Git commit quality and conventional commits expertise with automatic issue tracking integration. Auto-invokes when the user explicitly asks about commit message format, commit quality, conventional commits, com...
Generate test file scaffolds from source analysis with language-appropriate templates.
Update repository documentation after code implementation. Maintains README, CHANGELOG, docs/ folder, and inline docstrings based on changes made. Triggered by lane-executor after task completion.
Perform comprehensive code reviews covering security, style, performance, and best practices. Use when reviewing code changes before commit or merge, auditing existing code, or checking for vulnerabilities.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.