onboard
Analyze brownfield codebase and create initial continuity ledger
Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Analyze brownfield codebase and create initial continuity ledger
Verify debug/dev artifacts are removed before commit. Use at session end to apply 'good boy scout' rule - leave code cleaner than you found it.
Guide through TDD process for adding new safety patterns - from threat identification to commit
Document leftover tasks as GitHub issues with full correlation to branch, PR, and original work plan. Use when ending a session with incomplete work that another agent should pick up.
Use when users need to simulate unbiased beta testers for CLI tools. Creates tester personas, models their environment, and runs terminal-first exploratory testing based only on documentation and observed termi...
Navigate and understand the Leather monorepo structure. Use when adding new code, finding existing implementations, or understanding package relationships. Helps locate the right package for new features and un...
Testing conventions and patterns for the Leather monorepo. Use when writing tests, creating test fixtures, or following TDD workflow. Covers Vitest setup, naming conventions, and common patterns.
Generate product changelog entries, X/Twitter posts, and Slack announcements for Leather wallet releases. Use when creating release communications including changelog entries for app.leather.io/changelog, annou...
Gas optimization analysis and implementation for Solidity contracts. Triggers on weasel gas, weasel optimize, or weasel efficiency.
Solidity code simplification and refactoring for clarity and maintainability. Triggers on weasel simplify, weasel refactor, or weasel clean up.
False positive filtering for Weasel static analysis results. Triggers on weasel filter, weasel triage, or weasel clean report.
Code explanation and understanding for Solidity smart contracts. Triggers on weasel explain, weasel what does, or weasel walkthrough.
Audit report writing for smart contract vulnerabilities. Triggers on weasel report, weasel write up, or weasel document.
Project overview and audit preparation for smart contract security. Triggers on weasel overview, weasel scope, or weasel onboard.
Proof of Concept exploit writing for Solidity vulnerabilities. Triggers on weasel poc, weasel prove, weasel exploit, or weasel demonstrate.
Static analysis and security review for Solidity smart contracts. Triggers on weasel analyze, weasel audit, weasel scan, weasel review, or weasel check.
Attack hypothesis validation for smart contracts. Triggers on weasel validate, weasel check attack, or weasel verify.
Write integration and unit tests for this codebase. Generate test files following repo patterns. Use when adding tests, improving coverage, writing test cases, or creating test suites.
Navigate and map this monorepo structure. Find files, packages, and dependencies. Use when asked to locate code, understand package relationships, find where something is defined, or explore repo structure.
Handle Drizzle database schema changes safely. Generate and apply migrations, add tables and columns. Use when modifying database schema, adding tables, creating migrations, or making database changes.
Split large tasks across multiple Claude Code sessions or branches. Coordinate parallel work with merge gates. Use when task is too large for one session, want parallel work, or need to split work across branch...
Scan codebase for secrets, API keys, credentials, and PII. Detect hardcoded sensitive data. Use when auditing for secrets, checking for exposed keys, reviewing security, or scanning for PII.
Structured implementer-verifier-reviewer pipeline for high-quality code. Artifact-based handoffs between roles. Use when needing rigorous review process, handoff between roles, or review pipeline for critical c...
Debug and fix CI/CD pipeline failures. Analyze workflow logs, identify issues, and apply fixes. Use when CI is failing, build errors occur, tests fail in CI, or pipeline is broken.
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.