Skip to content
Back to search

claude-code-skills

SkillWorks with Claude CodeGitHub

Eleven reusable skills for Claude Code.

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/yassine2med--claude-code-skills/badge.svg)](/listings/yassine2med--claude-code-skills)

HTML

<a href="/listings/yassine2med--claude-code-skills"><img src="/api/listings/yassine2med--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.

git clone https://github.com/yassine2med/claude-code-skills
cd claude-code-skills

Copy the skills you want into your Claude Code skills folder:

| For | Copy to | |---|---| | Every project on your machine | `~/.claude/skills/` | | One project only | `<project>/.claude/skills/` |

Example for all skills on Linux or macOS: `cp -r skills/* ~/.claude/skills/`. On Windows PowerShell: `Copy-Item skills\* $env:USERPROFILE\.claude\skills -Recurse`.

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 · 95 lines
  1. <p align="center"><img src="docs/banner.svg" alt="claude-code-skills" width="100%"></p>
  2. # claude-code-skills
  3. [![CI](https://github.com/yassine2med/claude-code-skills/actions/workflows/ci.yml/badge.svg)](https://github.com/yassine2med/claude-code-skills/actions/workflows/ci.yml) ![Python](https://img.shields.io/badge/python-3.10%2B-3776ab) ![License](https://img.shields.io/badge/license-MIT-8fb08a)
  4. Eleven reusable skills for Claude Code. Each one is a short playbook that Claude loads by itself when your words match its description, so you never type a command. They come from a personal assistant setup used every day for a job search, client websites and facility operations, rewritten to be generic and free of private details.
  5. ![Screenshot](docs/screenshot.png)
  6. ## What it is for
  7. A skill is a folder with one `SKILL.md` file. It tells Claude how to do one kind of task the same careful way every time: what to check first, what order to work in, what never to do, and what "done" means. This repo gives you a ready set you can copy, edit and make your own, plus two small tools: a validator that keeps every skill well formed, and a banner maker for GitHub READMEs.
  8. ## The skills
  9. | Skill | Use it when | What it does |
  10. |---|---|---|
  11. | `root-cause-fix` | Something fails, or the same step failed twice | Find the cause before any change, fix the cause, prove it, log the lesson |
  12. | `company-research` | "Who are they", "is this legit" | Five sourced lines in about five tool calls, plus scam red flags |
  13. | `interview-prep` | A time is proposed, "prepare me" | Calendar, reminders, a brief, STAR answers, practice with feedback, thank-you |
  14. | `recruiter-reply` | A recruiter emails you | A short, warm draft for each message type, sent only after your yes |
  15. | `certification-study` | "Quiz me", "what do I study" | Twenty-minute sessions, five exam-style questions, a logged score |
  16. | `site-ship` | "Change this and put it online" | Update, test, real-browser check, security scan, then deploy with proof |
  17. | `explainer-video` | "Make a video on X" | Script, local voice, Manim animation, a stills check, delivery |
  18. | `approval-gate` | Anything that sends, posts, deletes or pays | Show the exact action, wait for a yes, act once, verify, log |
  19. | `readme-polish` | "Make my repo look good" | Description, topics, banner, badges, real screenshot, honest README |
  20. | `plain-english` | "Keep it simple" | Short sentences, result first, tables and diagrams for structure |
  21. | `token-lean` | Long sessions, cost or limit worries | Search first, read little, filter output, save notes before ending |
  22. ## Install
  23. ```
  24. git clone https://github.com/yassine2med/claude-code-skills
  25. cd claude-code-skills
  26. ```
  27. Copy the skills you want into your Claude Code skills folder:
  28. | For | Copy to |
  29. |---|---|
  30. | Every project on your machine | `~/.claude/skills/` |
  31. | One project only | `<project>/.claude/skills/` |
  32. Example for all skills on Linux or macOS: `cp -r skills/* ~/.claude/skills/`. On Windows PowerShell: `Copy-Item skills\* $env:USERPROFILE\.claude\skills -Recurse`.
  33. ## How to use
  34. | I want to | Command |
  35. |---|---|
  36. | Check that every skill is well formed | `python scripts/validate_skills.py` |
  37. | Check a different skills folder | `python scripts/validate_skills.py path/to/skills` |
  38. | Make a README banner | `python scripts/make_banner.py my-repo "What it does in one line" --category "Dev tools" --tags python cli --out docs/banner.svg` |
  39. | Run the tests | `python -m pytest -q` |
  40. `validate_skills.py` exits with 0 when all skills pass, 1 when a skill has a problem, and 2 when the folder is missing. It checks the front matter, that the name matches the folder, the description length, a "Done means" section, and that no skill holds an email address, a phone number or an em dash.
  41. ## How a skill is built
  42. ```
  43. skills/
  44. root-cause-fix/
  45. SKILL.md front matter (name, description) + the playbook
  46. ```
  47. 1. The `description` line is what Claude reads to decide whether the skill fits. Write it as "Use when ...".
  48. 2. The body is numbered steps. Each skill ends with a "Done means" line, so Claude knows when to stop and what proof to show.
  49. 3. Rules that must never bend sit under a "Never" heading.
  50. 4. Skills call each other by name. `recruiter-reply` hands off to `approval-gate` and `interview-prep`. `site-ship` hands off to `root-cause-fix` when a build fails.
  51. ## Make them yours
  52. Skills work best with your own facts. Add them in the skill, not in the prompt: your target roles, your tools, your deploy command, your voice. Keep private details out of anything you publish.
  53. ## More skills worth a look
  54. Other people publish good skill collections. These are links, not copies; each repo keeps its own license.
  55. | Repo | What it is |
  56. |---|---|
  57. | [anthropics/skills](https://github.com/anthropics/skills) | The official public skills from Anthropic |
  58. | [alirezarezvani/claude-skills](https://github.com/alirezarezvani/claude-skills) | A large community collection of skills, agents and plugins (MIT) |
  59. | [danyuchn/asd-ste100-skill](https://github.com/danyuchn/asd-ste100-skill) | Simplified Technical English rules as a skill (MIT); the idea behind `plain-english` |
  60. | [virgiliojr94/book-to-skill](https://github.com/virgiliojr94/book-to-skill) | Turns a technical book PDF into a skill (MIT) |
  61. ## Limits
  62. - The skills are instructions, not code. Claude follows them, but you still review what it does, especially anything that sends or deletes.
  63. - Some steps name common tools (Playwright, Manim, `gh`). Swap in the tools you have.
  64. - `explainer-video` needs Manim and a local text-to-speech engine installed by you.
  65. - The banner maker draws one design. It uses a monospace font stack, so the look changes slightly between systems.
  66. ## License
  67. MIT. See `LICENSE`.

Ratings and comments

Sign in to rate this skill.

Sign in

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