Audits the current project against the development standards defined in ~/.claude/CLAUDE.md.

MITAuto-check: notesAgent Workflows

Install Audit Standards

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill audit-standards -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace audit-standards --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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/productivity/claude-workflow-skills/skills/audit-standards .claude/skills/audit-standards && 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
audit-standards
GitHub stars
2.8k
Token cost
~1.8k tokens
SKILL.md length
700 words
Files
1
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Audits the current project against the development standards defined in ~/.claude/CLAUDE.md.

  • Works in 6 steps: Pre-flight check → Inventory the project → Audit each principle → …
  • The user says audit against settings
  • SKILL.md covers Step 0: Pre-flight check, Step 1: Inventory the project, Step 2: Audit each principle and Step 3: Generate GitHub issues, plus 2 more sections
  • Calls git and gh

What it does

Audit Standards is an agent skill from jeremylongshore/tons-of-skills-marketplace. Audits the current project against the development standards defined in ~/.claude/CLAUDE.md. Documents non-compliant findings as GitHub issues and writes a prioritised fix plan to the project CLAUDE.md. Use when the user says audit against settings, audit standards, check standards compliance, or audit this project.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Agent instruction files, Shell scripting and Git workflow. It works with GitHub, Bash and Git. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • The user says audit against settings
  • Audit standards
  • Check standards compliance
  • Audit this project

Example prompts

  • “Use the audit-standards skill to audit the current project against the development standards defined in ~/.claude/CLAUDE.md”
  • “/audit-standards”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Bash

Workflow steps

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

  1. Pre-flight check
  2. Inventory the project
  3. Audit each principle
  4. Generate GitHub issues
  5. Write prioritised fix plan to CLAUDE.md
  6. Report summary

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, 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

Audit Standards loads about 1.8k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 700 words of instructions outside code blocks.

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

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:43
    - Any `.env`, `.env.template`, `.gitignore` — secrets handling
  • NoteMentions a .env fileSKILL.md:108
    ls .env* 2>/dev/null
  • NoteMentions a .env fileSKILL.md:113
    - `.gitignore` exists and excludes `.env`, secrets, build artifacts, IDE files
  • NoteMentions a .env fileSKILL.md:115
    - No `.env` with real values present
  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Grep, Bash

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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 700 words, ~1,754 tokens.

Download SKILL.mdSave it as .claude/skills/audit-standards/SKILL.md (or your agent's skills folder).
name
audit-standards
description
Audits the current project against the development standards defined in ~/.claude/CLAUDE.md. Documents non-compliant findings as GitHub issues and writes a prioritised fix plan to the project CLAUDE.md. Use when the user says audit against settings, audit standards, check standards compliance, or audit this project.
allowed-tools
Read, Glob, Grep, Bash
disable-model-invocation
true

Audit Standards

Project: !basename $(git rev-parse --show-toplevel 2>/dev/null) 2>/dev/null || basename $PWD Branch: !git branch --show-current 2>/dev/null || echo "unknown"

Audits the current project against the personal development standards loaded from ~/.claude/CLAUDE.md. Generates actionable GitHub issues and a prioritised fix plan.

The development standards from the user's global ~/.claude/CLAUDE.md are already loaded into context. The key principles to audit against are:

  1. Codify, Don't Document — manual steps should be executable scripts
  2. Bash Script UX with pfb — terminal output uses pfb with correct visual hierarchy
  3. Markdown Standards — all markdown passes markdownlint with zero warnings
  4. Professional Documentation Tone — formal docs are objective, not personal
  5. Version Control Everything — correct files committed, secrets excluded
  6. Fail Fast, Pivot Early — (process principle, skip for static audit)
  7. Behavioral Integrity — (process principle, skip for static audit)

Step 0: Pre-flight check

bash
gh auth status 2>&1 || { echo "ERROR: gh is not authenticated. Run: gh auth login"; exit 1; }

Step 1: Inventory the project

bash
find . -not -path './.git/*' -type f | sort

Also read:

  • README.md — documentation tone and completeness
  • CLAUDE.md — project AI context file exists and is current
  • Any .env, .env.template, .gitignore — secrets handling
  • Any *.sh files — bash scripting standards
  • Any *.md files — markdown quality

Step 2: Audit each principle

Principle 1 — Codify, Don't Document
  • Does the README describe manual steps that should instead be scripts?
  • Do bash scripts use #!/usr/bin/env bash shebang?
  • Do scripts have Google-Style header docs (name, description, author, version, usage, dependencies)?
  • Do functions have @param, @return, @example doc comments?
  • Is author attribution derived from git config user.name/git config user.email?
  • Are scripts idempotent (safe to run multiple times)?

Run: grep -rn "#!/" --include="*.sh" . to find all scripts.

Principle 2 — Bash Script UX with pfb

For each .sh file:

  • Is pfb used for terminal output (not plain echo for status messages)?
  • Are emojis passed as a parameter, not embedded in the message string?
  • Are log levels (pfb info/success/warn/error) used for single-line status only?
  • Is visual hierarchy consistent (heading → subheading, not mixed)?

Run: grep -rn "pfb\|echo" --include="*.sh" . and compare usage patterns.

Principle 3 — Markdown Standards

Check for a .markdownlint.json at the repo root:

bash
cat .markdownlint.json 2>/dev/null || echo "MISSING"

Run markdownlint if available:

bash
markdownlint '**/*.md' 2>&1 | head -50

Check:

  • Blank lines around headings, lists, code blocks, tables
  • Code blocks specify a language (no bare triple-backtick fences)
  • Prose lines ≤ 120 characters
  • URLs wrapped in <> or link syntax
  • Consistent list numbering (1. 2. 3.)
  • YAML frontmatter description fields are single unbroken lines
Principle 4 — Professional Documentation Tone

Read README.md and any formal docs. Flag:

  • Second-person language ("you", "your") in formal technical docs (README intro, architecture sections)
  • Conversational phrasing in formal sections
  • User-specific references that should be generic

Note: READMEs and tutorials may use "you" in instructional sections — this is acceptable.

Show full SKILL.md (301 more words)Show less
Principle 5 — Version Control Everything
bash
cat .gitignore 2>/dev/null || echo "MISSING .gitignore"
ls .env* 2>/dev/null

Check:

  • .gitignore exists and excludes .env, secrets, build artifacts, IDE files
  • .env.template exists if the project requires environment configuration
  • No .env with real values present
  • AI context files (CLAUDE*.md, AGENTS*.md, GEMINI*.md) are gitignored and symlinked
AI context file check

Find all AI context files in the project (excluding .git):

bash
find . -not -path './.git/*' \( -name 'CLAUDE*.md' -o -name 'AGENTS*.md' -o -name 'GEMINI*.md' \) | sort

For each file found, verify two things:

  1. Gitignored — the pattern appears in .gitignore:

    bash
    git check-ignore -v <file>
  2. Symlink — the file is a symbolic link (pointing to the private ai-context repo), not a regular tracked file:

    bash
    [ -L "<file>" ] && echo "SYMLINK" || echo "REGULAR FILE — should be a symlink"

A finding is raised for any AI context file that is not gitignored OR is not a symlink. The expected pattern is: file is listed in .gitignore, stored in the private ai-context repo, and symlinked back into the project directory so local AI tooling finds it normally (see extract-ai-context.sh in that repo).

Step 3: Generate GitHub issues

First, fetch all open issues to avoid creating duplicates:

bash
gh issue list --state open --limit 100 --json title --jq '.[].title'

For each finding, check whether an open issue with a matching title already exists. If one does, skip it. Only create an issue if no existing open issue covers the same finding.

For each distinct finding with no existing open issue, create a GitHub issue:

bash
gh issue create \
  --title "<principle>: <brief description of violation>" \
  --body "$(cat <<'EOF'
## Principle

<which standard this relates to>

## Finding

<description of the non-compliance>

## Expected

<what the standard requires>

## Current state

<what was found in the project>

## Suggested fix

<concrete change to make>
EOF
)" \
  --label "enhancement"

Use --label "bug" for missing required files or broken standards; --label "enhancement" for improvements and style compliance.

Note each issue number as you go.

Step 4: Write prioritised fix plan to CLAUDE.md

Append or update a section in the project CLAUDE.md under the heading ## Standards Audit — <today's date>:

markdown
## Standards Audit — YYYY-MM-DD

Issues generated from `/audit-standards` review against ~/.claude/CLAUDE.md.
Suggested fix order:

### Group 1 — Correctness (fix first)

- #N: <title>
- #N: <title>

### Group 2 — Standards Compliance

- #N: <title>
- #N: <title>

### Group 3 — Quality Improvements

- #N: <title>
- #N: <title>

Order: missing required files first, then standards violations, then style improvements.

Step 5: Report summary

Output a brief summary:

  • Total issues created (with links)
  • Which principle had the most findings
  • Top-priority fix
  • Link to the CLAUDE.md section added

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

Files

Just SKILL.md in plugins/productivity/claude-workflow-skills/skills/audit-standards of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit cfae287

Compare with similar skills

Audit Standards 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.

Audit Standards compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audit Standards this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.8kAutomated safety check: NotesMIT
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
Setup Matt Pocock Skillsywwynm/EverythingDone1448 repos~1.7kAutomated safety check: PassGPL-3.0
Zed Configwcygan/dotfiles194—~930Automated safety check: PassNone
Setup Matt Pocock Skillsyamcodes/arkenv147—~1.8kAutomated safety check: PassMIT
Spin Upaspi6246/Claude-Code-Skills-for-Academics159—~1.9kAutomated safety check: PassNone

Similar skills

  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 9 days ago
    Agent WorkflowsAuto-check passed
  • Setup Matt Pocock Skills

    ywwynm/EverythingDone

    Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…

    144 GitHub starsUsed in 8 repos~1.7k tokens
    Agent WorkflowsAuto-check passed
  • Zed Config

    wcygan/dotfiles

    Zed editor configuration expert. An agent skill from wcygan/dotfiles.

    194 GitHub stars~930 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Sets up an Agent skills block in AGENTS.md/CLAUDE.md and .agent/docs/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…

    147 GitHub stars~1.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Spin Up

    aspi6246/Claude-Code-Skills-for-Academics

    Start-of-session orientation routine that briefs Claude on the current state of a project before work begins.

    159 GitHub stars~1.9k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Questions about Audit Standards

What does Audit Standards do?

Audits the current project against the development standards defined in ~/.claude/CLAUDE.md. Audit Standards is an agent skill from jeremylongshore/tons-of-skills-marketplace.md.

When should I use Audit Standards?

Audit Standards fits situations like: the user says audit against settings; audit standards; check standards compliance; audit this project.

How do I install Audit Standards in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill audit-standards -a claude-code`. Or copy the skill folder (plugins/productivity/claude-workflow-skills/skills/audit-standards in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/audit-standards in your project. Claude Code loads it when a task matches its description.

How do I install Audit Standards in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill audit-standards -a codex`. Or copy the skill folder (plugins/productivity/claude-workflow-skills/skills/audit-standards in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/audit-standards in your project. Codex loads it when a task matches its description.

Can I use Audit Standards 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 jeremylongshore/tons-of-skills-marketplace --skill audit-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audit-standards, .gemini/skills/audit-standards, .github/skills/audit-standards and .opencode/skills/audit-standards in your project.

What does Audit Standards need to run?

Going by SKILL.md and its folder, Audit Standards needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Read, Glob, Grep, Bash.

Does Audit Standards access the network?

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

Is Audit Standards safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Audit Standards use?

Audit Standards is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Audit Standards use?

About 1.8k tokens (SKILL.md is roughly 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 Audit Standards?

Skills that share tags, products or a category with Audit Standards: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Setup Matt Pocock Skills (ywwynm/EverythingDone, 144 stars), Zed Config (wcygan/dotfiles, 194 stars) and Setup Matt Pocock Skills (yamcodes/arkenv, 147 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audit Standards?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.