Skip to content
Back to search

claude-code-skills

SkillWorks with Claude CodeGitHub

Expert-level Claude Code skills for real codebases, real products.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/notmanas--claude-code-skills/badge.svg)](/listings/notmanas--claude-code-skills)

HTML

<a href="/listings/notmanas--claude-code-skills"><img src="/api/listings/notmanas--claude-code-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Each skill is self-contained. Grab what you need.

# Pick a skill and install it
npx degit notmanas/claude-code-skills/skills/<skill-name> .claude/skills/<skill-name>

# Example: install the UX expert
npx degit notmanas/claude-code-skills/skills/ux-expert .claude/skills/ux-expert

# Example: install devil's advocate
npx degit notmanas/claude-code-skills/skills/devils-advocate .claude/skills/devils-advocate

No config. No dependencies. Just markdown files that Claude Code picks up automatically.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 112 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Claude Code Skills
  2. **I don't know what I don't know. So I built skills that do.**
  3. ---
  4. ## Why this exists
  5. I'm an engineer building a product solo. I can write code all day — but that's maybe 30% of what shipping a product actually takes. UX design, product strategy, questioning my own decisions, catching what AI missed — I don't have a team of specialists for any of it.
  6. So I started giving Claude actual knowledge bases instead of just asking it to "be an expert." Audit frameworks, questioning methodologies, design principles — the stuff specialists carry in their heads after years of work. Now every skill cites its reasoning, teaches me something, and produces output I can actually use.
  7. These skills are tested on a live product. They've caught critical issues I would've shipped blind.
  8. ---
  9. ## Install
  10. Each skill is self-contained. Grab what you need.
  11. ```bash
  12. # Pick a skill and install it
  13. npx degit notmanas/claude-code-skills/skills/<skill-name> .claude/skills/<skill-name>
  14. # Example: install the UX expert
  15. npx degit notmanas/claude-code-skills/skills/ux-expert .claude/skills/ux-expert
  16. # Example: install devil's advocate
  17. npx degit notmanas/claude-code-skills/skills/devils-advocate .claude/skills/devils-advocate
  18. ```
  19. No config. No dependencies. Just markdown files that Claude Code picks up automatically.
  20. ---
  21. ## Available Skills
  22. ### [ux-expert](skills/ux-expert/) — UX audits backed by real methodology
  23. Audits your pages across 8 dimensions (hierarchy, cognitive load, screen real estate, interaction cost...). Every finding cites the UX principle being violated. Produces implementation-ready redesign specs with wireframes.
  24. ```
  25. /ux-expert audit the dashboard
  26. ```
  27. Knowledge base: ~2,000 lines covering Gestalt principles, Shneiderman's mantra, cognitive load theory, component library decision guides.
  28. [Read more](skills/ux-expert/README.md)
  29. ---
  30. ### [devils-advocate](skills/devils-advocate/) — "Are you sure about that?"
  31. Challenges AI-generated plans, code, and decisions before you commit. Uses pre-mortem analysis, inversion thinking, and Socratic questioning to find what was missed — hidden assumptions, failure modes, and the optimistic shortcuts AI never questions.
  32. ```
  33. /devils-advocate review the auth flow
  34. ```
  35. Pairs with any other skill as a review layer:
  36. ```
  37. /ux-expert → design the page → /devils-advocate → challenge the design
  38. Claude Code → build the feature → /devils-advocate → find what was missed
  39. ```
  40. Knowledge base: ~1,100 lines covering questioning frameworks, 11 engineering blind spot categories, and AI-specific failure patterns.
  41. [Read more](skills/devils-advocate/README.md)
  42. ---
  43. ## What makes these different from "just prompting"
  44. **They teach you while they work.** Every finding comes with the reasoning behind it. You're not just getting a review — you're building intuition you didn't have before.
  45. **They're backed by real knowledge.** Each skill ships with curated reference files — methodology, not prompt tricks. Claude loads them on demand so they don't eat your context window.
  46. **They read your actual code.** Not your description of it. Findings reference specific files and line numbers.
  47. ---
  48. ## How skills work
  49. ```
  50. your-project/
  51. └── .claude/skills/
  52. └── <skill-name>/
  53. ├── SKILL.md # persona + process + principles
  54. └── references/ # domain knowledge, loaded on demand
  55. ```
  56. `SKILL.md` defines who Claude becomes when you invoke the skill. Reference files are the knowledge base. Each skill is self-contained — no shared dependencies.
  57. ---
  58. ## Who this is for
  59. Anyone building things with Claude! Solo devs, small teams, PMs shipping with Claude Code who need expertise they don't have and are done getting generic AI advice.
  60. ---
  61. ## Contributing
  62. Got a skill backed by real methodology? Not a prompt wrapper — something with actual domain knowledge, tested on a real project.
  63. PR it. Structure: `skills/your-skill/SKILL.md` + `skills/your-skill/references/`. Self-contained. No shared deps.
  64. ---
  65. ## License
  66. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.