██████╗  ██████╗    ███████╗██╗  ██╗██╗██╗     ██╗     ███████╗
██╔══██╗██╔═══██╗   ██╔════╝██║ ██╔╝██║██║     ██║     ██╔════╝
██║  ██║██║   ██║   ███████╗█████╔╝ ██║██║     ██║     ███████╗
██║  ██║██║   ██║   ╚════██║██╔═██╗ ██║██║     ██║     ╚════██║
██████╔╝╚██████╔╝██╗███████║██║  ██╗██║███████╗███████╗███████║
╚═════╝  ╚═════╝ ╚═╝╚══════╝╚═╝  ╚═╝╚═╝╚══════╝╚══════╝╚══════╝

Warning

This is a WIP and changes often. Just like any code/software you find, don't blindly download and run it. Review it, learn what it does to make an educated decision if you should use it.

Do Skills

This is a collection of skills I've curated from across the inter-webs.

Browse the public skill docs. For site development, see site/README.md.

Skills.sh is a good way to discover and install skills, but it lacks many features. This repo is my temporary solution for installing skills on a per-project and global basis for day-to-day work and personal projects. Many are from people I've copied, borrowed, improved, and modified to fit my use cases.

Suggestions

I would suggest you take a peak at Matt Pocock Skills and Lauren Tan's PStack

Installation

To keep this easy, I use Skills.sh for installation and updates.

Skills are split by install scope. Global skills help in any repo; install them once per machine. Project skills only pay off when a project uses that stack; install them into the project.

# every global skill, once per machine
npx skills add https://github.com/edheltzel/Do-Skills/tree/master/skills/global -g

# one stack, from inside a project (TypeScript projects add the shared typescript group)
npx skills add https://github.com/edheltzel/Do-Skills/tree/master/skills/project/typescript
npx skills add https://github.com/edheltzel/Do-Skills/tree/master/skills/project/frontend

To install a specific skill, use its exact listed name. Names carry the do- prefix, except vendored skills that keep their upstream name (such as anatomy):

npx skills add edheltzel/Do-Skills --skill=<skill-name>

If you want to install for a specific agents, use the option flags ie: -a claude-code or -a claude-code -a pi

gap-utility.toml declares the skill names for GAP's gap add command and distro selection.

Available Skills

Skills are grouped by scope, then by group. The root table is an index; each scope and group README lists its skills.

Names carry a do- prefix so they do not collide with a harness command (/simplify vs /do-simplify). Vendored skills keep their upstream name (anatomy) so their documented command still works.

PR and council skills adapt tstack (MIT), snapshot 1085050f3baed1ac724caa4a8166145fb2ac88af.

We also use our own PStack plugin for pstack tools (ps-how, ps-why, ps-bro, ps-unslop, and the rest). Install it alongside these skills. This repo duplicates only do-no-comments, a harness-neutral copy of ps-no-comments.

Global

Useful in any repo, or none. Install once per machine with -g.

Group	Skills	Coverage
Core	13	Stack-agnostic foundations - review lenses, reasoning, testing, simplification, agent-legible repos, comments, design patterns, skill authoring, and AI-writing cleanup.
Workflow	21	Change delivery - the brainstorm, plan, work, debug, and ship loop (LFG), commits, docs, GitHub projects and stacks, PR workflow and review triage, worktrees, and technical writing.
Operations	4	Operating AI agents - delegation, handoffs, prompt audits, and project status check-ins.
Content	3	Audience-facing media - illustrations, diagrams, images, and visual explanations.
Personal	4	Personal extras you want everywhere - teaching, todo.txt, isometric explainer figures.

Project

Pay off only when a project uses that stack or product. Install into the project.

Group	Skills	Coverage
TypeScript	4	Language-wide TypeScript - standards, refactoring, and type-driven design. Install alongside frontend, backend, or tooling.
Frontend	9	Web frontend - Astro, CSS, React effects, design systems, landing pages, redesign audits, UX flows, cleanup, and review.
Backend	1	Backend engineering - Effect (TypeScript) services and code, and review for Effect, Go, Python, and Rust.
Tooling	3	CLIs and lightweight tools - TypeScript CLI scaffolding, zero-dependency patterns, and performance profiling.
Swift	3	Swift and Apple platforms - macOS desktop apps, iOS review, and cleanup.
Product	1	Product marketing - positioning, SEO and GEO discovery, launches, conversion, and retention.
Marketing	9	SEO marketing on the Ubersuggest MCP - keyword research, site audits, competitors, content briefs, AI visibility, and action plans.
Personal	1	Personal extras for specific projects - recipe diagrams.

The workflow (LFG)

One loop takes a change from idea to merged PR. Every step ends by naming the next one; pick it, pick another, or stop. /do-it runs the loop for you.

flowchart LR
  subgraph Shape
    B[do-brainstorm] --> P[do-plan] --> D[do-doc-review]
  end
  subgraph Build
    W[do-work] --> S[do-simplify] --> R[do-adversarial-review]
  end
  subgraph Ship
    C[do-commit] --> U[Publish] --> L[do-commit land]
  end
  subgraph Respond
    T[do-git-pr-review-triage]
  end
  D -->|you approve the plan| W
  R --> C
  U -->|review comments| T
  T -->|accepted fixes| W
  G[do-debug] --> W

Loading

Stage	Skills	You decide
Shape	do-brainstorm → do-plan → do-doc-review	Approve or annotate the plan (in Plannotator, if installed)
Build	do-work → do-simplify → do-adversarial-review	Which review findings to fix
Ship	do-commit (commit, cp, cpp, land); publication routing	Answer ask-user gates; say go before land
Respond	do-git-pr-review-triage → Build → Ship	Which comments to act on; approve replies before they post

Ways in. New idea: /do-brainstorm. Known feature: /do-plan. Bug: /do-debug (joins at Build). PR comments: /do-git-pr-review-triage.

Run it all. /do-it (LFG) runs Shape → Build → Ship without the menus and stops at an open PR with green CI. It still stops for decisions only you can make. Merging stays with you.

Step out. /do-handoff from any stage writes a note to docs/plans/handoffs/ and adds its open tasks to todo.txt, where do-regroup and do-gh-pm pick them up.

Creating a Skill

Each skill lives in its own folder under a scope and a group. Every skill folder and its frontmatter name: carry the do- prefix:

skills/<scope>/<group>/do-skill-name/SKILL.md

The skills CLI only finds skills up to three folders below skills/, so do not nest deeper.

Pick the scope first:

• global/ - useful in any repo, or none: methodology, writing, git and GitHub, agent operations, setup you run before a project has skills, personal tools
• project/ - assumes a specific language, framework, platform, or product the project must use

Then the group. Global groups: core, workflow, operations, content, personal. Project groups are the stack or product: typescript (language-wide, installed alongside the TS groups), frontend, backend, tooling, swift, product, personal. personal exists in both scopes: personal tools you want everywhere go in global/personal, ones you only use in certain projects go in project/personal. Group descriptions live in skills.sh.json.

The SKILL.md file contains YAML frontmatter and markdown instructions:

---
name: do-skill-name
description: A clear description of what this skill does and when to use it
---

# Skill Name

[Instructions for the agent go here]

When adding, removing, or renaming a skill, update the skills list in gap-utility.toml to match the skill frontmatter names.

After adding, moving, renaming, or changing a skill's behaviour or description, regenerate the catalog and re-sync its docs page (docs/, see .agents/writing-docs.md):

bash scripts/update-readme.sh

---

License

WTFPL, except skills/project/marketing/, which is Apache-2.0 (see its LICENSE).

---

Attributions

do-teach-me and the writing principles in do-skill-craft (from writing-great-skills) are adapted from Matt Pocock's Skills do-astro is adapted from Astrolicious do-illo is copied from tmchow/illo-skill do-marketing is adapted from proxysoul/SoulStack marketing (MIT) do-perf is adapted from proxysoul/SoulStack skills/enliven (MIT) marketing skills (ai-visibility, competitor-analysis, content-brief, content-demand-finder, keyword-research, project-setup, seo-action-plan, seo-foundations, site-audit) are copied from ubersuggest/seo-skills (Apache-2.0) do-landing-page and do-redesign are original to this repo. The ideas come from elayadesign/ai-design-skills and elayadesign/redesign-skill; nothing is copied, and no MIT grant is made (see NOTICE.md)