Skip to content
Back to search

vaughn-skills

MarketplaceWorks with Claude CodeGitHub

Vaughn Botha's Claude Code skills

Safety scan

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

Badge for your README
findsafeskills safety rating

Markdown

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

HTML

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

Install

Install instructions from the README

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

Open the Claude desktop app, click the **Code** tab, start a new session (pick any folder), and paste this message:

Please install Vaughn's Claude skills on this computer for me. I'm not technical, so do everything you can yourself, explain each step in plain words, and only ask me when you need me to click something.

1. Make sure git is installed. If it isn't, install it.
2. Make sure the claude command works in the terminal. If it doesn't, install the Claude Code command-line tool using the official instructions at code.claude.com.
3. Run: claude plugin marketplace add Vaughnai2023/claude-skills
4. Run: claude plugin install github-ready@vaughn-skills
5. Tell me it's done, and that from now on, when Vaughn says he's updated something, I just say "Update Vaughn's skills" in a Code session.

Claude does the rest. No GitHub account needed. When it's done, start a new session and type `/github-ready:` to see the skills.

---

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.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "name": "vaughn-skills",
  3. "description": "Vaughn Botha's Claude Code skills",
  4. "owner": {
  5. "name": "Vaughn Botha"
  6. },
  7. "plugins": [
  8. {
  9. "name": "github-ready",
  10. "source": "./plugins/github-ready",
  11. "description": "Set up a new project on GitHub, or check an existing one: branches, merges, secret checks and safety rules for Claude"
  12. }
  13. ]
  14. }
README.md · README · 81 lines
  1. # Vaughn's Claude skills
  2. Skills for Claude Code that you install once and keep up to date from this repo.
  3. | Skill | What it does | Type this in Claude |
  4. |---|---|---|
  5. | github-ready: new | Starts a new project on GitHub with safety rules already in place | `/github-ready:new` |
  6. | github-ready: audit | Checks an existing project and fixes what's missing | `/github-ready:audit` |
  7. ---
  8. ## Install (one time)
  9. Open the Claude desktop app, click the **Code** tab, start a new session (pick any folder), and paste this message:
  10. ```
  11. Please install Vaughn's Claude skills on this computer for me. I'm not technical, so do everything you can yourself, explain each step in plain words, and only ask me when you need me to click something.
  12. 1. Make sure git is installed. If it isn't, install it.
  13. 2. Make sure the claude command works in the terminal. If it doesn't, install the Claude Code command-line tool using the official instructions at code.claude.com.
  14. 3. Run: claude plugin marketplace add Vaughnai2023/claude-skills
  15. 4. Run: claude plugin install github-ready@vaughn-skills
  16. 5. Tell me it's done, and that from now on, when Vaughn says he's updated something, I just say "Update Vaughn's skills" in a Code session.
  17. ```
  18. Claude does the rest. No GitHub account needed. When it's done, start a new session and type `/github-ready:` to see the skills.
  19. ---
  20. ## Getting Vaughn's updates
  21. Ask Claude: **"Update Vaughn's skills."** It runs:
  22. ```bash
  23. claude plugin marketplace update vaughn-skills
  24. claude plugin update github-ready@vaughn-skills
  25. ```
  26. Then start a new session.
  27. To get updates automatically instead: in Claude Code in the terminal, type `/plugin`, go to **Marketplaces**, choose **vaughn-skills**, then **Enable auto-update**.
  28. ---
  29. ## How github-ready keeps a project safe
  30. Every project it sets up works the same way:
  31. 1. **`main` is the live version.** Nobody, including Claude, saves changes straight onto it.
  32. 2. **Work happens on a branch**, which is a separate copy for one change, such as `feat/booking-reminders`.
  33. 3. **A pull request** shows the change on GitHub. Checks run automatically: a secret scan, plus tests if there are any.
  34. 4. **Squash and merge** turns the pull request into one tidy change on `main`, and GitHub deletes the branch.
  35. Safety rules on every project:
  36. - Passwords and API keys can't be committed. They live in `.env`, which never goes to GitHub.
  37. - Claude can't force-push, delete work, skip the checks, or read `.env`.
  38. - Pushing straight to `main` is blocked.
  39. **About free GitHub accounts:** GitHub only enforces branch rules itself on public repos or paid plans. On free private repos, the computer does the enforcing instead, through hooks that switch on automatically in Claude Code. The skill tells you which applies to each project.
  40. ---
  41. ## For Vaughn: adding and updating skills
  42. ```
  43. .claude-plugin/marketplace.json the catalogue: one entry per plugin
  44. plugins/<name>/ one folder per plugin
  45. .claude-plugin/plugin.json
  46. skills/<skill>/SKILL.md
  47. ```
  48. **Update a skill:** edit it on a branch, run `claude plugin validate .`, open a pull request, merge. People get the change next time they update. Leave out the `version` field so updates follow the latest commit.
  49. **Add a skill:** make a new folder under `plugins/` (copy `github-ready` as a starting point), add an entry to `marketplace.json`, validate, pull request, merge.
  50. **Move an existing skill** from `~/.claude/skills/<name>`: create `plugins/<name>/.claude-plugin/plugin.json`, copy the skill folder into `plugins/<name>/skills/<name>/`, and add the catalogue entry. Once installed this way, it's typed as `/<name>:<name>`, so consider shorter skill names inside the plugin.
  51. **Share it with someone:** send them the install section above. The repo is public, so they don't need a GitHub account or an invite.
  52. **Keep it public-safe:** this repo is public. Nothing personal, nothing about clients, no keys. Private skills go in their own private repo. See `CLAUDE.md` for the full list.

Ratings and comments

Sign in to rate this skill.

Sign in

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