Loading...
Loading...
Found 44 Skills
Run the sefirot loop and confirm with the user if there are any questions
Use this skill when you need security analysis of Solidity smart contract code. User cases: auditing Solidity contracts, identifying re-entrancy bugs, detecting access control issues, reviewing unsafe external calls, evaluating code before deployment, gate-checking contracts in transaction pipelines, or performing security assessments.
Issue Workflow Stage 3——Fix code precisely based on confirmed root cause and solution, verify the effect, and document it in {slug}-fix-note.md. This is the final stage of the issue workflow—no verification loop means the workflow is incomplete. Two entry points: the standard path is triggered from easysdd-issue-analyze (with existing {slug}-analysis.md), and the quick path is triggered directly from easysdd-issue-report (without {slug}-analysis.md, as the root cause was determined by AI reading code during the report stage). Trigger scenarios: user says 'Start fixing the bug', 'Fix according to analysis', 'Start modifying code'. During repair, only modify the files stated in the solution; do not optimize casually or introduce new abstractions—these actions will make the scope spread to untraceable levels.
Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec. Phrasings: "check drift", "audit the spec", "does the code still match §V", "check invariants", "spec vs code".
Guide for extracting code or pseudocode from images using OCR and implementing it correctly. This skill should be used when tasks involve reading code, pseudocode, or algorithms from images (PNG, JPG, screenshots) and executing or implementing the extracted logic.
Synthesize outputs from multiple AI models into a comprehensive, verified assessment. Use when: (1) User pastes feedback/analysis from multiple LLMs (Claude, GPT, Gemini, etc.) about code or a project, (2) User wants to consolidate model outputs into a single reliable document, (3) User needs conflicting model claims resolved against actual source code. This skill verifies model claims against the codebase, resolves contradictions with evidence, and produces a more reliable assessment than any single model.
Build AdonisJS 6 features from scratch through production. Full lifecycle - build, debug, test, optimize, refactor. Follows TypeScript-first, Lucid ORM, and AdonisJS conventions.
Fixes blocking IO, unnecessary allocations, sync-in-async with keep/discard verification
Implement approved technical plans phase-by-phase, including code changes, verification, and progress updates directly in the plan file. Use this whenever the user asks to execute a plan, implement from a plan document, continue plan-based work, resume from checked/unchecked tasks, or "do phase 1/2/3" from an implementation plan in `rpi/plans/`, even if they do not explicitly name this skill.
Intelligently upgrade npm dependencies with breaking change research for major version updates. Use when the user asks to "update dependencies", "upgrade npm packages", "check for updates", or "update npm deps".
Execute a GRACE development plan in controller-managed parallel waves with selectable safety profiles, batched graph sync, and scoped reviews.
Use when you have a spec or requirements for a multi-step task, before writing implementation code. Helps break down complex features into bite-sized, verifiable tasks.