Main
Start with one skill and make it muscle memory: use
/prd-doc-writer,/issue-triage, or/github-repo-searchinstead of ad-hoc prompting.Treat skills as team SOPs: fork the repo, tweak the questions/outputs, and standardize names so everyone runs the same flow.
Keep dependencies ready: README calls out
agent-browser+ghlogin, which prevents broken steps when a skill needs browsing or GitHub APIs.Use the catalog as a map: 27 skills are grouped into coding, thinking/writing, and office lanes—pick lanes that match your current bottleneck.
Source-backed notes
- README states the repo contains 27 skills grouped into 3 categories (coding, thinking/writing, office).
- README shows the default Claude Code skills directory as
~/.claude/skills/and installs viagit clone. - README notes dependencies: agent-browser plus an authenticated
ghCLI session.
FAQ
- Where do I install the repo?: Clone it into
~/.claude/skills/(README) or copy individual skill folders you need. - How do I run a skill?: In Claude Code CLI, type the slash command like
/image-assistantor/prd-doc-writer(README examples). - What if a skill needs GitHub access?: README recommends
ghalready logged in so repo search/issue flows work reliably.