One-command GitHub repository health audit. An agent skill from thatrebeccarae/claude-marketing.

MITAuto-check: notesMarketing & SEO

Install Repo Health

skills CLI
$ npx skills add thatrebeccarae/claude-marketing --skill repo-health -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thatrebeccarae/claude-marketing repo-health --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/repo-health .claude/skills/repo-health && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
repo-health
GitHub stars
161
Token cost
~2.4k tokens
SKILL.md length
906 words
Files
4
Skills in repo
55
Repo updated
First seen
Licence
MIT

At a glance

One-command GitHub repository health audit. An agent skill from thatrebeccarae/claude-marketing.

  • Works in 8 steps: Validate Repo Path → Detect Public/Private → File Presence Checks → …
  • Marketing & SEO work in your project
  • SKILL.md covers Install, When to Use, How to Use and Procedure, plus 2 more sections
  • Calls gh, git and claude

What it does

Repo Health is an agent skill from thatrebeccarae/claude-marketing. One-command GitHub repository health audit. Checks for missing standard files, GitHub configuration, branch protection, documentation quality, and code hygiene. Produces a scored health report with prioritized fix recommendations.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `EXAMPLES.md` and `REFERENCE.md`).

It sits in Marketing & SEO. It works with GitHub. The repository describes itself as: A full marketing department for Claude Code. Skill packs for Klaviyo, Shopify, GA4, Looker Studio, paid media, and more. Audit, optimize, and report using natural language. The licence is MIT.

When your agent uses it

  • Marketing & SEO work in your project

Example prompts

  • “/repo-health”

Requirements

  • Python 3
  • Node.js

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Validate Repo Path
  2. Detect Public/Private
  3. File Presence Checks
  4. GitHub Configuration Checks
  5. Documentation Quality
  6. Code Hygiene
  7. Score and Report
  8. Fix Mode (--fix)

What it can do on your machine

Read from SKILL.md and the folder at commit a8a63ec. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git
    • claude
    • npm
    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, git, npm and pip, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Repo Health loads about 2.4k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 906 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:139
    - Any `.env`, `.env.*`, `credentials.*`, or `secrets.*` files tracked in git = FAIL
  • NoteMentions a .env fileSKILL.md:211
    [PASS] No tracked .env files

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from thatrebeccarae/claude-marketing at commit a8a63ec, republished under its MIT licence (© thatrebeccarae). 906 words, ~2,419 tokens.

Download SKILL.mdSave it as .claude/skills/repo-health/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
repo-health
description
One-command GitHub repository health audit. Checks for missing standard files, GitHub configuration, branch protection, documentation quality, and code hygiene. Produces a scored health report with prioritized fix recommendations.
license
MIT
origin
custom
author
Rebecca Rae Barton
author_url
https://github.com/thatrebeccarae
metadata.version
1.0.0
metadata.category
devops
metadata.domain
github
metadata.updated
2026-03-19
metadata.tested
2026-03-19
metadata.tested_with
Claude Code v2.1

Repo Health

One-command health audit for GitHub repositories. Produces a scored report with prioritized fix recommendations.

Install

bash
claude skill add --from https://github.com/thatrebeccarae/claude-marketing/skills/repo-health

When to Use

  • Setting up a new repo and want to make sure nothing is missing
  • Periodic health checks on active repositories
  • Before open-sourcing a private repo (what needs to be added?)
  • Onboarding onto an unfamiliar repo to assess its state
  • Pre-release hygiene sweep

How to Use

/repo-health [repo-path]        # Full audit with scored report
/repo-health [repo-path] --fix  # Audit + generate missing files

Default repo-path is the current working directory if omitted.


Procedure

Execute each step in order. Do not skip steps.

Step 1: Validate Repo Path
  1. If repo-path is provided, resolve to absolute path. If omitted, use current working directory.
  2. Confirm the path exists and is a directory.
  3. Confirm it contains a .git directory (is a git repo).

If validation fails:

Error: {repo-path} is not a git repository.
Provide a path to a git repo or run from within one.

STOP.

Step 2: Detect Public/Private

Determine repo visibility:

  1. Check for .public-repo marker file at repo root -> public
  2. Check if "public" appears in the remote URL -> public
  3. Run gh repo view --json isPrivate -q '.isPrivate' if gh is available -> use result
  4. If none of the above resolve it -> ask the user

Store as repo_visibility (public or private). Public repos are held to a stricter standard in scoring.

Step 3: File Presence Checks

Check for each standard file. Track result as PRESENT or MISSING.

FileRequired (Public)Required (Private)
LICENSEYesNo
README.mdYesYes
.gitignoreYesYes
SECURITY.mdYesNo
CONTRIBUTING.mdYesNo
CODEOWNERSRecommendedNo
.editorconfigRecommendedRecommended
.github/pull_request_template.md or .github/PULL_REQUEST_TEMPLATE.mdRecommendedNo
.github/ISSUE_TEMPLATE/ directory (or .github/ISSUE_TEMPLATE.md)RecommendedNo
CHANGELOG.mdRecommendedNo
CODE_OF_CONDUCT.mdRecommended (public)No
Step 4: GitHub Configuration Checks

Use gh CLI to query repo metadata. If gh is not available, skip this category and note it in the report.

bash
gh repo view --json description,repositoryTopics,hasWikiEnabled,defaultBranchRef,homepageUrl

Check each item. Track as PASS or FAIL.

CheckCriteria
Description setdescription is non-empty
Topics setrepositoryTopics has at least 3 topics
Homepage URLhomepageUrl is set (if project has a site)
Default branch namedefaultBranchRef.name is main (not master)
Branch protectiongh api repos/{owner}/{repo}/branches/main/protection returns 200 (public repos only)
Social previewgh api repos/{owner}/{repo} and check for custom Open Graph image (informational only)
Step 5: Documentation Quality

README checks:

  1. README.md exists (from Step 3)
  2. README length: < 50 lines = WARN (too short), > 500 lines = INFO (consider splitting)
  3. Has a project description in the first 5 lines (H1 or bold text)
  4. Has install/setup instructions (scan for "install", "getting started", "setup", "usage")
  5. Has a license reference (scan for "license", "LICENSE")
  6. If the /github-readme skill is available, note that a deeper README audit can be run via /github:readme audit

CHANGELOG checks:

  1. CHANGELOG.md exists (from Step 3)
  2. If present: follows Keep a Changelog format (scan for ## [ version headers)
  3. Most recent entry is within the last 90 days (WARN if stale)
Step 6: Code Hygiene

Stale branches:

bash
git branch -r --merged main | grep -v main | grep -v HEAD
git for-each-ref --sort=committerdate --format='%(refname:short) %(committerdate:relative)' refs/remotes/
  • Flag branches with no commits in > 90 days as stale
  • Count total stale branches

Tracked secrets/env files:

bash
git ls-files | grep -E '\.env$|\.env\.|credentials|secrets'
  • Any .env, .env.*, credentials.*, or secrets.* files tracked in git = FAIL

Large binary files:

bash
git ls-files | while read f; do
  size=$(wc -c < "$f" 2>/dev/null)
  [ "$size" -gt 5242880 ] && echo "$f ($size bytes)"
done
  • Files > 5MB tracked in git without Git LFS = WARN
  • Check for .gitattributes with LFS patterns if large binaries exist

Dependency freshness (if applicable):

  • If package.json exists: check for package-lock.json presence
  • If requirements.txt exists: check if pinned (versions specified)
  • Do NOT run install commands or modify anything
Step 7: Score and Report
Show full SKILL.md (360 more words)Show less
Scoring Categories
CategoryWeightWhat It Covers
Standard Files30%LICENSE, SECURITY.md, CONTRIBUTING.md, CODEOWNERS, .gitignore, .editorconfig, templates
GitHub Config15%Description, topics, branch protection, default branch
Documentation25%README quality, CHANGELOG presence and freshness
Code Hygiene20%Stale branches, tracked secrets, large binaries
Community10%CODE_OF_CONDUCT, issue templates, PR templates, CONTRIBUTING.md
Per-Category Scoring

Each category scores 0-100 based on checks passed within it. See REFERENCE.md for the full rubric.

Letter Grade
ScoreGrade
90-100A
80-89B
70-79C
60-69D
0-59F
Report Format
=== Repo Health Report: {repo-name} ===
Visibility: {public | private}
Overall Score: {score}/100 (Grade: {letter})

--- Standard Files (30%) --- Score: {n}/100
  [PASS] .gitignore
  [PASS] LICENSE (MIT)
  [MISS] SECURITY.md
  [MISS] CONTRIBUTING.md
  [PASS] CODEOWNERS
  ...

--- GitHub Config (15%) --- Score: {n}/100
  [PASS] Description: "One-command repo health audit..."
  [FAIL] Topics: none set
  [PASS] Default branch: main
  [FAIL] Branch protection: not enabled
  ...

--- Documentation (25%) --- Score: {n}/100
  [PASS] README.md (142 lines)
  [WARN] No install/setup instructions found in README
  [MISS] CHANGELOG.md
  ...

--- Code Hygiene (20%) --- Score: {n}/100
  [PASS] No tracked .env files
  [WARN] 3 stale branches (>90 days)
  [PASS] No large binary files tracked
  ...

--- Community (10%) --- Score: {n}/100
  [MISS] CODE_OF_CONDUCT.md
  [MISS] Issue templates
  [PASS] PR template
  ...

=== Prioritized Fixes ===
1. [HIGH] Add SECURITY.md — required for public repos. See template in REFERENCE.md.
2. [HIGH] Enable branch protection on main — prevents force pushes and requires reviews.
3. [HIGH] Add repository topics — improves discoverability. Suggest: {topic1}, {topic2}, {topic3}.
4. [MED]  Add CONTRIBUTING.md — guides external contributors.
5. [MED]  Add CHANGELOG.md — tracks releases for users.
6. [LOW]  Clean up 3 stale branches.
7. [LOW]  Add CODE_OF_CONDUCT.md — signals welcoming community.

Priority levels:

  • HIGH: Security, legal (LICENSE/SECURITY.md), or protection issues
  • MED: Documentation and community gaps that affect usability
  • LOW: Cleanup and nice-to-haves
Step 8: Fix Mode (--fix)

If --fix flag was passed:

  1. Present the list of MISS and FAIL items that can be auto-generated
  2. Ask the user to confirm which files to create (show numbered list, accept comma-separated selection or "all")
  3. For each confirmed file, generate it using sensible defaults:
    • SECURITY.md: Standard vulnerability reporting template
    • CONTRIBUTING.md: Fork/branch/PR workflow with code style notes
    • CODE_OF_CONDUCT.md: Contributor Covenant v2.1
    • .editorconfig: Sensible defaults for the detected tech stack
    • CODEOWNERS: Prompt user for owner patterns
    • Issue/PR templates: YAML form-based templates (see REFERENCE.md)
  4. Do NOT overwrite existing files
  5. Run infra/PII scrub on all generated content before writing

Key Principles

  • Read-only by default. The audit never modifies files unless --fix is explicitly passed.
  • Public repos are held to a higher standard. Private repos skip community and some config checks.
  • Prioritize actionable output. Every finding includes a specific fix recommendation.
  • No false urgency. Recommended items are scored lower than required items. The report distinguishes between must-fix and nice-to-have.
  • Respect existing work. Fix mode never overwrites. It only creates missing files.
  • Infra/PII awareness. All generated files pass through the standard PII scrub before writing.

Anti-Patterns -- Do NOT

  • Modify any files during a standard audit (no --fix flag)
  • Run install commands (npm install, pip install, etc.)
  • Push changes or create commits -- the user decides when to commit
  • Fabricate repository metadata -- use what gh and git report
  • Rate repos you do not have local access to -- this is a local audit tool
  • Skip the PII scrub when generating files in fix mode

© thatrebeccarae, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in skills/repo-health of thatrebeccarae/claude-marketing.

  • SKILL.md
  • EXAMPLES.md
  • LICENSE
  • REFERENCE.md

Open the folder on GitHubat commit a8a63ec

Compare with similar skills

Repo Health next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Repo Health compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Repo Health this skillthatrebeccarae/claude-marketing161—~2.4kAutomated safety check: NotesMIT
Nemoclaw Maintainer Normalize Title TagsNVIDIA/NemoClaw23k—~693Automated safety check: PassApache-2.0
GitHub Lead GenDucksss/codex-profiles180—~1kAutomated safety check: PassMIT
GitHub Lead QualificationDucksss/codex-profiles180—~1.2kAutomated safety check: PassMIT
Founder Led ContentAIDevGTM/gtm-cofounder310—~998Automated safety check: PassMIT
Sync Client Libsgoogleads/google-ads-api-developer-assistant100—~537Automated safety check: PassApache-2.0

Similar skills

  • Remove bracketed NemoClaw tags from GitHub issue and PR titles.

    23k GitHub stars~693 tokensUpdated today
    Marketing & SEOAuto-check passed
  • GitHub Lead Gen

    Ducksss/codex-profiles

    A skill your agent uses when running GitHub lead generation for codex-profiles.

    180 GitHub stars~1k tokensUpdated today
    Marketing & SEOAuto-check passed
  • GitHub Lead Qualification

    Ducksss/codex-profiles

    A skill your agent uses when qualifying outreach-tracker GitHub lead candidates for codex-profiles after lead generation and before any closing draft.

    180 GitHub stars~1.2k tokensUpdated today
    Marketing & SEOAuto-check passed
  • Founder Led Content

    AIDevGTM/gtm-cofounder

    Build authority by teaching the problem space, not announcing features.

    310 GitHub stars~998 tokensUpdated 6 days ago
    Marketing & SEOAuto-check passed
  • Sync Client Libs

    googleads/google-ads-api-developer-assistant

    Discovers Google Ads client libraries under clientlibs, verifies installed versions against GitHub latest releases, and automatically updates outdated codebases.

    100 GitHub stars~537 tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Gingiris Opensource

    Gingiris/gingiris-opensource

    🇺🇸 Open Source Marketing Playbook — How to get 10k+ GitHub stars.

    257 GitHub stars~1.4k tokensUpdated 5 mo ago
    Marketing & SEOAuto-check passed

More from thatrebeccarae/claude-marketing

All 55 skills in this repo
  • Google Analytics

    thatrebeccarae/claude-marketing

    Analyze Google Analytics data, review website performance metrics, identify traffic patterns, and suggest data-driven improvements.

    161 GitHub starsUsed in 3 repos~1.3k tokens
    Auto-check: notes
  • Content Creator

    thatrebeccarae/claude-marketing

    Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning.

    161 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Klaviyo Analyst

    thatrebeccarae/claude-marketing

    Klaviyo marketing operations and analyst expertise. An agent skill from thatrebeccarae/claude-marketing.

    161 GitHub stars~5k tokensUpdated 4 mo ago
    Auto-check: notes
  • Klaviyo Developer

    thatrebeccarae/claude-marketing

    Klaviyo API and developer integration expertise. An agent skill from thatrebeccarae/claude-marketing.

    161 GitHub stars~4.9k tokensUpdated 4 mo ago
    Auto-check: notes
  • Looker Studio

    thatrebeccarae/claude-marketing

    Looker Studio (formerly Google Data Studio) expertise. An agent skill from thatrebeccarae/claude-marketing.

    161 GitHub stars~3.6k tokensUpdated 4 mo ago
    Auto-check: notes
  • Shopify

    thatrebeccarae/claude-marketing

    Shopify e-commerce platform marketing expertise. An agent skill from thatrebeccarae/claude-marketing.

    161 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check: notes

Works with

Categories

Questions about Repo Health

What does Repo Health do?

One-command GitHub repository health audit. An agent skill from thatrebeccarae/claude-marketing. Repo Health is an agent skill from thatrebeccarae/claude-marketing. One-command GitHub repository health audit.

When should I use Repo Health?

Repo Health fits situations like: marketing & SEO work in your project.

How do I install Repo Health in Claude Code?

Run `npx skills add thatrebeccarae/claude-marketing --skill repo-health -a claude-code`. Or copy the skill folder (skills/repo-health in thatrebeccarae/claude-marketing) into .claude/skills/repo-health in your project. Claude Code loads it when a task matches its description.

How do I install Repo Health in Codex?

Run `npx skills add thatrebeccarae/claude-marketing --skill repo-health -a codex`. Or copy the skill folder (skills/repo-health in thatrebeccarae/claude-marketing) into .agents/skills/repo-health in your project. Codex loads it when a task matches its description.

Can I use Repo Health in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thatrebeccarae/claude-marketing --skill repo-health -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/repo-health, .gemini/skills/repo-health, .github/skills/repo-health and .opencode/skills/repo-health in your project.

What does Repo Health need to run?

Going by SKILL.md and its folder, Repo Health needs the command-line tools its instructions call (gh, git, claude, npm and pip). Our summary lists: Python 3; Node.js.

Does Repo Health access the network?

SKILL.md contains no URLs. Its commands use gh, git, npm and pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Repo Health safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Repo Health use?

Repo Health is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Repo Health use?

About 2.4k tokens (SKILL.md is roughly 9.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Repo Health?

Skills that share tags, products or a category with Repo Health: Nemoclaw Maintainer Normalize Title Tags (NVIDIA/NemoClaw, 23k stars), GitHub Lead Gen (Ducksss/codex-profiles, 180 stars), GitHub Lead Qualification (Ducksss/codex-profiles, 180 stars) and Founder Led Content (AIDevGTM/gtm-cofounder, 310 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Repo Health?

thatrebeccarae (a GitHub user) maintains it in thatrebeccarae/claude-marketing, which has 161 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on May 14, 2026.

Source: thatrebeccarae/claude-marketing on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.