AGENT SKILLS · EQUIPAGGIAMENTO / poteto

poteto · Agent Skills

7 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

poteto
Community

meditate

- 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".

installazioni
1
GitHub Stars
267
Aggiornato
19 mar
poteto
Community

unslop

- 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".

installazioni
1
GitHub Stars
305
Aggiornato
19 mar
poteto
Community

interrogate

Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.

installazioni
1
GitHub Stars
78
Aggiornato
14 giu
poteto
Community

poteto-mode

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

installazioni
1
GitHub Stars
78
Aggiornato
14 giu
poteto
Community

principle-separate-before-serializing-shared-state

Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.

installazioni
1
GitHub Stars
78
Aggiornato
14 giu
poteto
Community

principle-subtract-before-you-add

Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.

installazioni
1
GitHub Stars
78
Aggiornato
14 giu
poteto
Community

tdd

Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.

installazioni
1
GitHub Stars
78
Aggiornato
14 giu