← all skills

poteto

@poteto seed · attribution · source repo

0 followers · 26 skills

1. ▌
   Oops · poteto

   Infrastructure fix for broken builds, failed tests, stale state, and environment drift. Covers both user-project and Noodle-internal failures. Triggers when builds break, tests fail, state is stale, or environment drifts. Use on 'oops', 'fix the build', 'tests are failing', 'something broke', 'broken build'.
   0
   installs
2. ▌
   Plan · poteto bundle

   Systematic planning for medium-to-large tasks. Gathers context, identifies domain skills, writes phased plans to brain/plans/. Does NOT implement. Use for new features, multi-file refactors, or architectural changes — not small fixes. Triggers: "plan this", "break this down".
   0
   installs
3. ▌
   Todo · poteto

   Add, complete, or view items in the brain/todos.md backlog. Use when the user says "todo", "add a todo", "mark done", "what's on the backlog", "show todos", "list tasks", "check off", or wants to manage their task list.
   0
   installs
4. ▌
   Brain · poteto

   Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers after debugging sessions, mistakes, corrections, architectural decisions, or any insight worth preserving across sessions. Use on 'add to brain', 'remember this', 'write a note', or brain/ modifications.
   0
   installs
5. ▌
   Codex · poteto

   Run Codex CLI (exec, resume) for parallel work, delegating tasks to another model, or background code generation. Handles code analysis, refactoring, and automated editing. Includes Spark vs standard guidance. Triggers: "codex", "run codex", "use codex to".
   0
   installs
6. ▌
   Commit · poteto

   Create conventional commit messages. Use when the user says "commit this", "save changes", "git commit", asks to commit code, write a commit message, or format git history. Follows conventional commits specification.
   0
   installs
7. ▌
   Noodle · poteto bundle

   Operate the Noodle CLI — explain commands, find flags, create/edit .noodle.toml config. Also covers writing skills for Noodle: the orders pipeline, task-type schedule fields, stage composition, and the orders-next.json schema. Use when running noodle commands, editing .noodle.toml, writing or updating a skill's schedule field, authoring new task-type skills, or asking "how to run noodle", "noodle help", "configure noodle".
   0
   installs
8. ▌
   Refine · poteto

   Sharpen todo items in brain/todos.md into precise, actionable prompts via targeted questioning. Triggers: "refine", "refine todos", "clarify todos".
   0
   installs
9. ▌
   Review · poteto

   Review plans and code changes. Walks Architecture → Code Quality → Tests → Performance, numbering issues with tradeoff options. Triggers: "review", "review this", "code review", "look over this", "check my changes", "audit", "critique", "what do you think", "sanity check".
   0
   installs
10. ▌
    Unslop · poteto

    Remove AI writing patterns from prose. Use for docs, READMEs, blog posts, any non-code text that should sound human. Triggers: "unslop", "humanize", "make this sound human", "clean up this writing", "edit for voice", "de-AI this text".
    0
    installs
11. ▌
    Execute · poteto bundle

    Implementation methodology for executing tasks. Handles scoping, decomposition, worktree workflow, verification, and commit conventions. Triggers: "execute", "implement", "build this", "code this".
    0
    installs
12. ▌
    Quality · poteto bundle

    Post-cook quality gate. Reviews completed cook work for correctness, scope discipline, and principle compliance. Emits stage_message events with findings. Triggers after execute stages, on '/quality', 'review this', 'check the work', 'assess quality'.
    0
    installs
13. ▌
    Reflect · poteto

    Reflect on the conversation and update the brain. Use when wrapping up, after mistakes or corrections, or when significant codebase knowledge was gained. Triggers: "reflect", "remember this".
    0
    installs
14. ▌
    Testing · poteto bundle

    Test-driven development workflow for Noodle. Use when testing changes, writing tests, fixing bugs, creating fixtures, or running the test suite. Triggers: "test", "write a test", "fix this bug", "add a fixture", "run tests", "TDD", or any task involving verification of code changes.
    0
    installs
15. ▌
    Ast Grep · poteto bundle

    Structural code search via ast-grep — use when code shape and element relationships matter, not just text. E.g., "find async functions without error handling", "refactor foo(a, b) to foo({ a, b })". Use Grep for simple name lookups.
    0
    installs
16. ▌
    Meditate · poteto bundle

    Audit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities. Triggers: "meditate", "audit the brain", "prune brain", "review skills", "consolidate notes", "prune notes".
    0
    installs
17. ▌
    Ruminate · poteto bundle

    Mine past Claude Code and Codex conversations for uncaptured patterns, corrections, and knowledge. Cross-references with existing brain content. Triggers: "ruminate", "mine my history", "what have I been working on", "review past sessions", "extract learnings".
    0
    installs
18. ▌
    Schedule · poteto bundle

    Orders scheduler. Reads .noodle/mise.json, writes .noodle/orders-next.json. Schedules work orders based on backlog state, plan phases, session history, and task type schedules. Triggers when orders are empty, after backlog changes, when the loop re-evaluates, or when /schedule is invoked.
    0
    installs
19. ▌
    Worktree · poteto

    Use for concurrent sessions, agent team isolation, or any work needing a separate branch. Critical for multi-agent workflows. Triggers: "worktree", "new worktree", "clean up worktrees", "need isolation", or when spawning agent teams.
    0
    installs
20. ▌
    Debugging · poteto

    Systematic root-cause debugging methodology. Use for any technical problem — errors, failures, unexpected behavior, or when stuck. Triggers: "debug", "fix this", "what's wrong", "investigate".
    0
    installs
21. ▌
    Find Skills · poteto

    Discover and install agent skills from the open ecosystem. Use IMMEDIATELY when the user asks "how do I do X", "find a skill for X", "is there a skill for X", "can you do X" for specialized capabilities, wants to extend agent functionality, mentions a domain they wish they had help with, or asks about tools/templates/workflows that might exist as installable skills.
    0
    installs
22. ▌
    Skill Creator · poteto bundle

    Guide for creating or updating skills — specialized knowledge, workflows, and tool integrations packaged for Claude.
    0
    installs
23. ▌
    Go Best Practices · poteto bundle

    Production Go patterns — lifecycle, concurrency, config, testing, CI. Use when writing, reviewing, or refactoring Go code. Triggers on Go code review, Go refactoring, or 'go best practices'.
    0
    installs
24. ▌
    Interaction Design · poteto bundle

    Design and implement microinteractions, motion design, transitions, and user feedback patterns. Use when adding polish to UI interactions, implementing loading states, creating gesture-based interactions, designing hover/focus states, building notification/toast systems, adding scroll-triggered animations, implementing drag-and-drop, or creating delightful user experiences.
    0
    installs
25. ▌
    React Best Practices · poteto bundle

    React performance optimization guidelines. Use when writing, reviewing, or refactoring React components, hooks, effects, data fetching, or bundle optimization. Includes useEffect best practices — when NOT to use effects and better alternatives. Triggers: "when writing React code", "reviewing a React PR", "why is this component re-rendering", "reviewing code for performance issues", "optimizing bundle size".
    0
    installs
26. ▌
    Make Interfaces Feel Better · poteto bundle

    Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.
    0
    installs