potetos-for-everyone

In the author's own words, from each skill's SKILL.md — showing the first 30 of 49 files.

• architect

  Settle data shapes, ownership, boundaries, and interfaces before code crosses a function/module boundary. Use for non-trivial design work.

  skills/architect/SKILL.md on GitHub (opens in a new tab)

• arena

  Spawn parallel candidate implementations for the same task, cross-judge, and graft the best parts into the winning base. Use when exploring competing designs or critical artifacts.

  skills/arena/SKILL.md on GitHub (opens in a new tab)

• automate-me

  Create a personal mode skill from recurring workflow patterns in available history. Use when the user wants their own agent style encoded.

  skills/automate-me/SKILL.md on GitHub (opens in a new tab)

• blast-radius

  Prove what a small-looking change can affect before or after editing. Use for compatibility, caller, state, schema, or behavior impact analysis.

  skills/blast-radius/SKILL.md on GitHub (opens in a new tab)

• bro

  Restate the last technical explanation in plain human language with minimal jargon. Use when the user asks for a simpler version.

  skills/bro/SKILL.md on GitHub (opens in a new tab)

• create-verification-skill

  Generate a project-local verification skill that drives the real app and captures evidence. Use when setting up automated verification for a repo.

  skills/create-verification-skill/SKILL.md on GitHub (opens in a new tab)

• figure-it-out

  Design a rigorous custom playbook when no bundled playbook safely fits a large or unusual task. Use for cross-cutting ambiguous execution.

  skills/figure-it-out/SKILL.md on GitHub (opens in a new tab)

• how

  Trace how a subsystem works using code and runtime evidence. Use for architecture walkthroughs, data flow, call paths, and are-we-sure investigations.

  skills/how/SKILL.md on GitHub (opens in a new tab)

• interrogate

  Adversarially review a diff or design with independent lenses and evidence. Use before shipping contested or high-impact changes.

  skills/interrogate/SKILL.md on GitHub (opens in a new tab)

• maintain-verification-skill

  Repair a project verification skill whose feature map or commands drifted. Use when app behavior and verification docs no longer agree.

  skills/maintain-verification-skill/SKILL.md on GitHub (opens in a new tab)

• make-bot-ui

  Build a small operator UI over an agent/webhook backend. Use when buttons or controls should trigger an agent workflow.

  skills/make-bot-ui/SKILL.md on GitHub (opens in a new tab)

• no-comments

  Remove redundant comments, dead workaround explanations, and AI tells from code while preserving necessary constraints. Use when cleaning up code or diffs.

  skills/no-comments/SKILL.md on GitHub (opens in a new tab)

• poteto-mode

  Lauren Tan-inspired rigorous engineering mode for concise communication, deliberate decomposition, simple code, independent review when available, and runtime verification. Use for non-trivial engineering tasks or when the user asks for Poteto Mode/pstack-style rigor.

  skills/poteto-mode/SKILL.md on GitHub (opens in a new tab)

• principle-attack-the-premise

  Inventory who actually owns or exhibits the imbalance, then challenge the shared premise before writing another patch. Use when two or more fixes that share one premise have failed the same gate.

  skills/principle-attack-the-premise/SKILL.md on GitHub (opens in a new tab)

• principle-boundary-discipline

  Validate and normalize at boundaries, trust internal invariants, and keep business logic free of adapter noise. Use when at parsing, framework, process, network, storage, or user-input boundaries.

  skills/principle-boundary-discipline/SKILL.md on GitHub (opens in a new tab)

• principle-build-the-lever

  Prefer a script, codemod, generator, benchmark, or verifier that performs or proves the work repeatably over hand edits. Use when for repetitive, large, or verification-heavy work.

  skills/principle-build-the-lever/SKILL.md on GitHub (opens in a new tab)

• principle-encode-lessons-in-structure

  Turn recurring guidance into a type, lint, test, metadata flag, generator, runtime check, or skill so the system carries the lesson. Use when when the same corrective instruction appears more than once.

  skills/principle-encode-lessons-in-structure/SKILL.md on GitHub (opens in a new tab)

• principle-exhaust-the-design-space

  Build a few materially different cheap prototypes and compare evidence before committing to one design. Use when for novel interactions or architecture with no strong precedent.

  skills/principle-exhaust-the-design-space/SKILL.md on GitHub (opens in a new tab)

• principle-experience-first

  Optimize for the end-user experience unless the cost violates an explicit constraint. Use when product, UX, API design, or feature-scope tradeoffs arise.

  skills/principle-experience-first/SKILL.md on GitHub (opens in a new tab)

• principle-fix-root-causes

  Reproduce the symptom, trace causality until one mechanism explains it, and fix that mechanism rather than compensating for downstream effects. Use when during debugging and incident repair.

  skills/principle-fix-root-causes/SKILL.md on GitHub (opens in a new tab)

• principle-foundational-thinking

  Choose the core data structures, ownership, and sequencing first so downstream logic becomes simpler. Use when before writing logic, especially when state or concurrency is involved.

  skills/principle-foundational-thinking/SKILL.md on GitHub (opens in a new tab)

• principle-guard-the-context-window

  Route bulk exploration to isolated workers or files and bring back compact evidence summaries, not raw floods. Use when when reads, logs, fan-out, or generated output threatens to dominate context.

  skills/principle-guard-the-context-window/SKILL.md on GitHub (opens in a new tab)

• principle-laziness-protocol

  Bias toward deletion and the smallest change that fully solves the problem. Use when considering adding code, abstractions, dependencies, or speculative features.

  skills/principle-laziness-protocol/SKILL.md on GitHub (opens in a new tab)

• principle-make-operations-idempotent

  Design repeated execution to converge on the same correct end state rather than multiplying side effects. Use when for commands, lifecycle steps, retries, loops, or crash recovery.

  skills/principle-make-operations-idempotent/SKILL.md on GitHub (opens in a new tab)

• principle-migrate-callers-then-delete-legacy-apis

  Move callers to the new shape and delete the old path in the same migration wave instead of carrying a compatibility layer. Use when when replacing an internal api.

  skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md on GitHub (opens in a new tab)

• principle-minimize-reader-load

  Reduce indirection, mutable scope, and one-caller abstractions until the causal path is easy to hold in one mind. Use when when code requires too many hops, wrappers, hidden states, or mental joins.

  skills/principle-minimize-reader-load/SKILL.md on GitHub (opens in a new tab)

• principle-model-the-domain

  Encode the domain in the right structure: state machine, typed model, table, registry, reducer, boundary, or collection instead of scattered conditionals. Use when when stateful logic accumulates branches or repeated shape assumptions.

  skills/principle-model-the-domain/SKILL.md on GitHub (opens in a new tab)

• principle-never-block-on-the-human

  Run the experiment or make the reversible best-effort change, then show the result. Ask only for genuine preference, authority, or irreversible decisions. Use when when a reversible empirical or implementation choice can be resolved with available tools.

  skills/principle-never-block-on-the-human/SKILL.md on GitHub (opens in a new tab)

• principle-outcome-oriented-execution

  Converge on the target architecture rather than preserving temporary compatibility states as permanent complexity. Use when during planned migrations or rewrites with explicit phases.

  skills/principle-outcome-oriented-execution/SKILL.md on GitHub (opens in a new tab)

• principle-prove-it-works

  Verify the requested behavior against the real artifact or surface whenever possible; a proxy check only proves the proxy. Use when verifying changes, completing tasks, or claiming something is fixed.

  skills/principle-prove-it-works/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 184k stars · 6 skills
• taste-skillby Leonxlnx Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages 109k stars · 1 skill
• archifyby tt-a1i Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more. 93.1k stars · 5 skills
• marketingskillsby coreyhaines31 Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. 58.3k stars · 30 skills
• khazix-skillsby KKKKhazix 数字生命卡兹克开源的 AI Skills 合集 | Agent Skills: leader（帮你定义目标）, neat-freak 洁癖, hv-analysis, khazix-writer & more — Claude Code, Codex & 40+ agents 21.9k stars · 6 skills
• Kamiby tw93 👩 🚒 Good content deserves good paper. Layout rules and templates that let AI agents export PDF, PNG and editable PowerPoint. 12.2k stars · 1 skill