New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Audit Whitepapers

by FlorianBruniaux in FlorianBruniaux/claude-code-ultimate-guide

Audits version freshness, French and English parity and metadata of whitepapers and recap cards in the claude-code-ultimate-guide repo, with optional fix suggestions.

CC-BY-SA-4.0Auto-check passedDocuments & Office

Install Audit Whitepapers

skills CLI
$ npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill source-command-audit-whitepapers -a claude-code

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

GitHub CLI
$ gh skill install FlorianBruniaux/claude-code-ultimate-guide source-command-audit-whitepapers --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/FlorianBruniaux/claude-code-ultimate-guide.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/source-command-audit-whitepapers .claude/skills/source-command-audit-whitepapers && 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
source-command-audit-whitepapers
GitHub stars
6.1k
Token cost
~3.8k tokens
SKILL.md length
1,251 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
CC-BY-SA-4.0

At a glance

Audits version freshness, French and English parity and metadata of whitepapers and recap cards in the claude-code-ultimate-guide repo, with optional fix suggestions.

  • Works in 7 steps: Discovery → Version Gap Analysis (40 points per file) → Content Staleness Check (20 points per… → …
  • Checking whether whitepapers and recap cards match the current guide version
  • SKILL.md covers Command Template, Arguments, Usage and Phase 1: Discovery, plus 9 more sections
  • Calls git

What it does

This migrated command, `/audit-whitepapers`, runs a freshness and quality audit over the repo's whitepapers and recap cards in French and English. It reads the `VERSION` file as the target guide version, scans the `.qmd` files under the whitepapers and recap-cards folders, and sorts each into main whitepaper, cheatsheet, partner whitepaper, recap card or bundle, with partner and bundle files left out of scoring.

For each scored file it parses the YAML frontmatter, including title, version, whitepaper version, guide version, card number, category, difficulty and series, then scores it against the current guide version, checks that French and English counterparts match and validates metadata consistency. Flags select scope and detail: `--fix` generates prioritized update suggestions and frontmatter patches without modifying files, `--verbose` shows passing criteria too, and `--cards-only` or `--wp-only` limit the audit.

When your agent uses it

  • Checking whether whitepapers and recap cards match the current guide version
  • Finding French and English documents that have drifted apart
  • Reviewing frontmatter and metadata consistency across recap cards

Example prompts

  • “Run /audit-whitepapers and show me only the failures.”
  • “Audit the recap cards only and suggest frontmatter patches with --fix.”
  • “Run a verbose audit of the main whitepapers against the current VERSION.”

Requirements

  • The claude-code-ultimate-guide repository layout, with a VERSION file and whitepapers in .qmd files

Workflow steps

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

  1. Discovery
  2. Version Gap Analysis (40 points per file)
  3. Content Staleness Check (20 points per file)
  4. FR/EN Parity Check (20 points per file)
  5. Metadata Quality (20 points per file)
  6. Scoring and Grading
  7. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 585c203. 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:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, 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 Whitepapers loads about 3.8k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 1,251 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~3.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 passed

The automated check found no risky patterns in SKILL.md.

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 FlorianBruniaux/claude-code-ultimate-guide at commit 585c203, republished under its CC-BY-SA-4.0 licence (© FlorianBruniaux). 1,251 words, ~3,848 tokens.

Download SKILL.mdSave it as .claude/skills/source-command-audit-whitepapers/SKILL.md (or your agent's skills folder).
name
source-command-audit-whitepapers
description
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards

source-command-audit-whitepapers

Use this skill when the user asks to run the migrated source command audit-whitepapers.

Command Template

Audit Whitepapers & Recap Cards

Comprehensive freshness and quality audit for all whitepapers (FR + EN) and recap cards (FR + EN). Scores each document against the current guide version, checks FR/EN parity, and validates metadata consistency.

Arguments

  • --fix - Generate update suggestions and frontmatter patches (does not modify files)
  • --verbose - Show all criteria including passing ones, not just failures
  • --cards-only - Audit only recap cards (skip main whitepapers)
  • --wp-only - Audit only main whitepapers (skip recap cards)

Usage

bash
/audit-whitepapers                  # Full audit, failures only
/audit-whitepapers --fix            # Audit + prioritized update suggestions
/audit-whitepapers --verbose        # Full details for all criteria
/audit-whitepapers --cards-only     # Recap cards only
/audit-whitepapers --wp-only        # Whitepapers only

Phase 1: Discovery

Objective: Locate and inventory all auditable documents.

Steps

  1. Read current guide version: Read the VERSION file at the project root. This is the target version all documents should be synced against.

  2. Scan directories for .qmd files:

    whitepapers/fr/         (main whitepapers FR)
whitepapers/en/         (main whitepapers EN)
whitepapers/recap-cards/fr/    (recap cards FR)
whitepapers/recap-cards/en/    (recap cards EN)

  3. Classify each file:

    • Main whitepaper: files matching [0-9][0-9]-*.qmd in whitepapers/fr/ or whitepapers/en/
    • Cheatsheet: files matching *cheatsheet*.qmd (tracked separately, not scored)
    • Custom whitepaper: files matching *-whitepaper.qmd or *-cheatsheet.qmd from external partners (strangebee, purchasely, devwithai) -- excluded from scoring, listed separately
    • Recap card: all .qmd files in recap-cards/fr/ or recap-cards/en/
    • Bundle/include: fiches-recap-serie.qmd, files in fiches/ subdirectory -- excluded (they are composed documents)

  4. Parse YAML frontmatter for each included file (read between first --- and second ---). Extract:

    • title, subtitle, author, date
    • version (guide version tracked in main WPs and recap cards)
    • wp-version (whitepaper own semver, main WPs only)
    • guide-version (explicit guide version field used in recap cards)
    • card-number, category, difficulty (recap cards only)
    • series (main WPs only)

  5. Display discovery summary:

    Guide version: {VERSION}
Found: {N} main whitepapers ({FR}/{EN} FR/EN), {N} recap cards ({FR}/{EN} FR/EN)
Excluded: {N} custom files (strangebee, purchasely, devwithai), {N} bundle files

Phase 2: Version Gap Analysis (40 points per file)

Objective: Score how current each document is relative to the guide.

Semver comparison logic

Parse version strings as MAJOR.MINOR.PATCH. The staleness metric is minor_gap = current_minor - file_minor (using the same MAJOR). If MAJOR differs, treat as critical.

For main whitepapers, the guide version field is version. For recap cards, the guide version field is guide-version (fall back to version if absent).

Scoring table
CriterionPointsDetection
Guide version current (0-1 minor behind)15minor_gap <= 1
Guide version recent (2-3 minor behind)10minor_gap 2-3 (partial credit, replaces the 15)
Guide version old (4-10 minor behind)5minor_gap 4-10 (partial credit)
wp-version field present and valid semver5Field exists AND matches \d+\.\d+\.\d+ (WP only)
wp-version consistent with FR/EN pair10Same wp-version value in the counterpart file (WP only)
guide-version consistent with FR/EN pair10Same guide-version (or version) in the counterpart (cards)

Freshness labels:

  • 0-1 minor behind: Fresh
  • 2-3 minor behind: Stale
  • 4-10 minor behind: Very Stale
  • 11+ minor behind: Critical

Note: The 15, 10, 5 pts for guide version are mutually exclusive (award only the highest applicable tier).

Phase 3: Content Staleness Check (20 points per file)

Objective: Detect whether the guide sections a whitepaper covers have changed since it was last updated.

Whitepaper-to-guide mapping (embedded)
WP#FR filename prefixEN filename prefixGuide sections
0000-introduction00-series-introductionguide/ultimate-guide.md Ch.1-2
0101-prompts01-effective-promptsCh.2 prompting sections
0202-personnalisation02-customizationCh.3 Memory, Ch.4 Agents, Ch.5 Skills
0303-securite03-securityCh.7 Hooks, security sections
0404-architecture04-architectureCh.2 internals, architecture sections
0505-equipe05-teamCh.3 team config, Ch.9 CI/CD
0606-privacy06-privacyCh.2 data/privacy sections
0707-guide-reference07-reference-guideCh.10 Reference
0808-agent-teams08-agent-teamsCh.9 agent teams
0909-apprendre09-learningguide/roles/learning-with-ai.md
1010-budget10-ai-budgetBusiness/ROI content
Steps
  1. For each main whitepaper, extract the date field. If the date is not in YYYY-MM-DD format, parse it (e.g., "2026-02-12" or "March 2026").
  2. Run git log --since="{date}" --oneline -- guide/ultimate-guide.md guide/roles/ guide/core/ to count commits that touched guide content since the whitepaper's date.
  3. Score:
CriterionPointsDetection
No guide commits since wp date10git log returns 0 commits
Few commits since wp date (1-5)71-5 commits (partial)
Moderate commits (6-15)46-15 commits (partial)
Many commits (>15)0More than 15 commits
Mapping defined for this WP5WP number is in the mapping table above
Git history accessible5git log command executes without error

Recap cards: Skip detailed git analysis. Award a flat staleness score based on minor_gap:

  • 0-1 behind: 20 pts
  • 2-3 behind: 15 pts
  • 4-10 behind: 8 pts
  • 11+ behind: 0 pts

Phase 4: FR/EN Parity Check (20 points per file)

Objective: Every document should have a complete, version-consistent counterpart in the other language.

Pairing strategy

Main whitepapers: Match on the two-digit numeric prefix (e.g., 00, 03, 10). FR and EN filenames differ but the prefix is consistent.

Recap cards: Match on identical filename (both language directories use the same filenames).

Show full SKILL.md (510 more words)Show less
Scoring table
CriterionPointsDetection
Counterpart file exists in other language10File with matching prefix (WP) or identical name (cards) found
wp-version matches between pairs5Same wp-version value (WP only)
guide version matches between pairs5Same version/guide-version value

Score both the FR and EN files of a pair identically on parity (if the pair is complete, both get 20; if one is missing, the existing file scores 0 on parity).

Phase 5: Metadata Quality (20 points per file)

Objective: Validate frontmatter completeness, field formats, and consistency across files of the same type.

Main whitepapers (20 points max)
CriterionPointsDetection
Required fields present6Has all of: title, subtitle, author, date, version, wp-version, series
version follows semver pattern3Matches \d+\.\d+\.\d+
wp-version follows semver pattern3Matches \d+\.\d+\.\d+
date is parseable and not in the future3Valid date, not after today
series value is consistent2Equals "Codex Ultimate Guide"
No missing wp-version (not left empty or absent)3Field has a non-empty value
Recap cards (20 points max)
CriterionPointsDetection
Required fields present5Has all of: title, subtitle, card-number, category, difficulty, guide-version, author, version, date
card-number matches filename prefix4e.g., C01 in card-number matches c01- in filename
category valid for language4FR: one of "Technique", "Methodologie", "Conception"; EN: one of "Technical", "Methodology", "Design" (flag "Conceptual" as inconsistent in EN)
difficulty is valid value3One of: "beginner", "intermediate", "advanced"
guide-version and version fields match each other4Both fields exist and have the same value within the same file

Known issue to detect automatically: EN C-series cards use two different category values ("Conceptual" on c01-c05, "Design" on c06+). Flag this inconsistency explicitly in the Metadata Issues section of the report.

Phase 6: Scoring and Grading

Score formula (per file)
Total = Version Gap (40) + Content Staleness (20) + FR/EN Parity (20) + Metadata Quality (20)
Score = (Total / 100) * 100  [as a percentage]
Grade scale
GradeScoreStatus
A90-100Fresh, fully synced
B80-89Good (production threshold)
C70-79Needs update soon
D60-69Stale, should prioritize
F<60Critical: likely outdated content
Overall health score
Weighted Health = (Sum of WP scores * 2 + Sum of card scores * 1) / (WP count * 2 + card count * 1)

Whitepapers are weighted 2x because they are 20-80 pages each vs. 2-page recap cards. A stale whitepaper carries more risk.

Phase 7: Report

Output the following Markdown report. Use <details> blocks for individual file breakdowns to keep the top level scannable.

markdown
# Whitepaper & Recap Card Audit

**Date**: {today}
**Guide Version**: {VERSION}
**Overall Health**: {score}% ({grade})
**Files Audited**: {total} ({wp_count} whitepapers, {card_count} recap cards)

---

## Version Status Dashboard

| Status | Whitepapers | Recap Cards | Total |
|--------|-------------|-------------|-------|
| Fresh (0-1 minor behind)   | N | N | N |
| Stale (2-3 minor behind)   | N | N | N |
| Very Stale (4-10 behind)   | N | N | N |
| Critical (11+ behind)      | N | N | N |

**Versions currently in use**:
- Main WP 00-09: {version} ({gap} minor versions behind)
- Main WP 10: {version} ({gap} minor versions behind)
- Recap cards: {guide-version} ({gap} minor versions behind)

---

## Whitepaper Scores

| WP# | Title | version | Gap | wp-version | Parity | Score | Grade |
|-----|-------|---------|-----|------------|--------|-------|-------|
| 00  | ...   | ...     | -N  | ...        | OK/gap | N%    | X     |
...

<details>
<summary>Individual criteria breakdown (WP 00)</summary>

| Phase | Criterion | Result | Points |
|-------|-----------|--------|--------|
| Version Gap | Guide version current | Critical (-11) | 0/15 |
| Version Gap | wp-version valid semver | OK | 5/5 |
| ... | ... | ... | ... |
| **Total** | | | **N/100** |
</details>

---

## Recap Card Scores

| Series | Cards | Avg guide-version | Avg Gap | Avg Score | Grade |
|--------|-------|-------------------|---------|-----------|-------|
| T (Technical)    | 22 | ... | -N | N% | X |
| M (Methodology)  | 22 | ... | -N | N% | X |
| C (Conceptual)   | 13 | ... | -N | N% | X |

<details>
<summary>Individual card scores</summary>

| Card | Category | guide-version | Gap | Parity | Metadata | Score | Grade |
|------|----------|---------------|-----|--------|----------|-------|-------|
...
</details>

---

## FR/EN Parity Report

### Whitepapers
| WP# | FR | EN | wp-version Match | version Match |
|-----|----|----|------------------|---------------|
...

### Recap Cards
- **FR count**: {N} | **EN count**: {N}
- **Missing FR**: [list or "None"]
- **Missing EN**: [list or "None"]
- **Version mismatches**: [list or "None"]

---

## Metadata Issues

### Known: EN Recap Card Category Inconsistency
EN C-series cards use two different values for the "Conceptual/Design" category:
- "Conceptual": c01, c02, c03, c04, c05
- "Design": c06, c07, c08, ...
Recommendation: standardize to "Design" to match guide terminology.
Affected files: whitepapers/recap-cards/en/c01-*.qmd through c05-*.qmd (change "Conceptual" to "Design")

### Other issues
[List any missing fields, bad formats, date issues...]

---

## Prioritized Action Items

### Critical (Grade F, 11+ versions behind)
[List specific whitepapers with filename paths]

### High (Grade D-F, 2+ versions behind)
[List specific files]

### Medium (Metadata quality, category fixes)
[List specific issues]

### Low (Polish, date alignment)
[List specific issues]

---

## Next Steps

1. Run `/update-whitepapers --since {oldest_version}` to update all stale WPs
2. Fix EN category inconsistency (5 files: c01 through c05, change "Conceptual" to "Design")
3. Re-run `/audit-whitepapers` after updates to track progress
4. Target: 80%+ health (Grade B) across all files

Fix Mode (--fix)

When --fix is passed, append a Fix Suggestions section after the report. This section provides concrete patches but does NOT modify any files.

Frontmatter version patches

For each file with a stale guide version, output:

yaml
# File: whitepapers/fr/00-introduction-serie.qmd
# Change:
version: "3.27.6"  ->  version: "{current_VERSION}"
date: 2026-02-12   ->  date: {today}
Category fix patches (EN recap cards)
Files to update (category: "Conceptual" -> "Design"):
- whitepapers/recap-cards/en/c01-trust-calibration.qmd
- whitepapers/recap-cards/en/c02-*.qmd
- whitepapers/recap-cards/en/c03-*.qmd
- whitepapers/recap-cards/en/c04-*.qmd
- whitepapers/recap-cards/en/c05-*.qmd
Update command checklist

Based on the stale WPs detected, output the /update-whitepapers commands to run in order:

Suggested update sequence:
1. /update-whitepapers --since {oldest_stale_version} --wp 00,01,02,03,04,05,06,07,08,09
2. /update-whitepapers --since {oldest_stale_version} --wp 10
3. Review and bump wp-version for each updated WP (patch = content corrections, minor = new sections)
4. Bump guide-version in all recap cards to {current_VERSION}
5. Re-run /audit-whitepapers to verify

Verbose Mode (--verbose)

When --verbose is passed, expand all <details> blocks by default and show the complete per-file criteria table (all criteria, not just failures) for every audited file.

Exclusions Reference

The following files are excluded from scoring (listed in discovery summary only):

PatternReason
strangebee-*.qmd, purchasely-*.qmd, devwithai-*.qmdClient/partner custom files, separate lifecycle
fiches-recap-serie.qmd, fiches/*.qmdBundle/include files, no independent versioning
*_quarto.yml, references.bibBuild config, not content
cheatsheet.qmdListed separately in discovery, not scored in main audit

© FlorianBruniaux, CC-BY-SA-4.0. 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 .agents/skills/source-command-audit-whitepapers of FlorianBruniaux/claude-code-ultimate-guide.

Open the folder on GitHubat commit 585c203

Compare with similar skills

Audit Whitepapers 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 Whitepapers compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audit Whitepapers this skillFlorianBruniaux/claude-code-ultimate-guide6.1k—~3.8kAutomated safety check: PassCC-BY-SA-4.0
Aholo Viewer Docsmanycoretech/aholo-viewer1.1k—~341Automated safety check: PassMIT
Sync Jaaws-samples/sample-amazon-bedrock-agentcore-onboarding133—~1.5kAutomated safety check: PassMIT-0
Dx Devops Test Failures Analyzeforcedotcom/sf-skills1.1k—~1.4kAutomated safety check: PassApache-2.0
Technical Analystjeremylongshore/tons-of-skills-marketplace2.8k—~2.2kAutomated safety check: PassMIT
Moonbit Docs Maintainermoonbitlang/moonbit-docs2.4k—~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Aholo Viewer Docs

    manycoretech/aholo-viewer

    Guides writing and maintaining Aholo Viewer documentation: README, AGENTS.md, architecture notes, bilingual manual pages and AI collaboration guides.

    1.1k GitHub stars~341 tokensUpdated today
    Writing & ContentAuto-check passed

  • Sync Ja

    aws-samples/sample-amazon-bedrock-agentcore-onboarding

    Official

    Sync Japanese README translations with English source. An agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding.

    133 GitHub stars~1.5k tokensUpdated 7 days ago
    Writing & ContentAuto-check passed

  • Dx Devops Test Failures Analyze

    forcedotcom/sf-skills

    Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix direction, and prioritized improvement…

    1.1k GitHub stars~1.4k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Technical Analyst

    jeremylongshore/tons-of-skills-marketplace

    Technical analysis translator for Product Managers. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Moonbit Docs Maintainer

    moonbitlang/moonbit-docs

    A skill your agent uses when maintaining the moonbitlang/moonbit-docs repository, including Sphinx docs under next/, MoonBit examples under next/sources/, error-code documentation, gettext…

    2.4k GitHub stars~1.1k tokensUpdated 17 days ago
    DevelopmentAuto-check passed

  • Dsh Web Documentation

    zhu1090093659/dsh-web

    A skill your agent uses when adding or editing dsh-web README files, docs, AGENTS.md instructions, user-facing configuration text, or bilingual documentation pairs.

    8.5k GitHub stars~479 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from FlorianBruniaux/claude-code-ultimate-guide

All 14 skills in this repo

  • Changelog Social Recap

    FlorianBruniaux/claude-code-ultimate-guide

    Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.

    6.1k GitHub stars~1.8k tokensUpdated yesterday
    Auto-check: notes

  • Codex Skill Self-Assessment

    FlorianBruniaux/claude-code-ultimate-guide

    Runs an interactive quiz in a quick or comprehensive mode, scores your skill level by topic and generates a personalized learning path with practice projects.

    6.1k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

  • Whitepaper Bare Section Prose Filler

    FlorianBruniaux/claude-code-ultimate-guide

    Adds two to four sentences of intro prose before each bare heading in the French and English whitepapers, splitting the work across nine parallel agents.

    6.1k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Methodology Advisor

    FlorianBruniaux/claude-code-ultimate-guide

    Reads a codebase silently, asks only what it cannot infer, and recommends one AI-assisted development methodology stack with a contextual quick start.

    6.1k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Guide and Landing Sync Check

    FlorianBruniaux/claude-code-ultimate-guide

    Check guide/landing synchronization status

    6.1k GitHub stars~692 tokensUpdated yesterday
    Auto-check passed

  • Track Online Mentions

    FlorianBruniaux/claude-code-ultimate-guide

    Searches the web for new mentions of the Claude Code Ultimate Guide or its author's public projects, checks them against YAML trackers and reports or adds the new ones.

    6.1k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Audit Whitepapers

What does Audit Whitepapers do?

Audits version freshness, French and English parity and metadata of whitepapers and recap cards in the claude-code-ultimate-guide repo, with optional fix suggestions. This migrated command, `/audit-whitepapers`, runs a freshness and quality audit over the repo's whitepapers and recap cards in French and English.qmd` files under the whitepapers and recap-cards folders, and sorts each into main whitepaper, cheatsheet, partner whitepaper, recap card or bundle, with partner and bundle files left out of scoring.

When should I use Audit Whitepapers?

Audit Whitepapers fits situations like: checking whether whitepapers and recap cards match the current guide version; finding French and English documents that have drifted apart; reviewing frontmatter and metadata consistency across recap cards.

How do I install Audit Whitepapers in Claude Code?

Run `npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill source-command-audit-whitepapers -a claude-code`. Or copy the skill folder (.agents/skills/source-command-audit-whitepapers in FlorianBruniaux/claude-code-ultimate-guide) into .claude/skills/source-command-audit-whitepapers in your project. Claude Code loads it when a task matches its description.

How do I install Audit Whitepapers in Codex?

Run `npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill source-command-audit-whitepapers -a codex`. Or copy the skill folder (.agents/skills/source-command-audit-whitepapers in FlorianBruniaux/claude-code-ultimate-guide) into .agents/skills/source-command-audit-whitepapers in your project. Codex loads it when a task matches its description.

Can I use Audit Whitepapers 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 FlorianBruniaux/claude-code-ultimate-guide --skill source-command-audit-whitepapers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/source-command-audit-whitepapers, .gemini/skills/source-command-audit-whitepapers, .github/skills/source-command-audit-whitepapers and .opencode/skills/source-command-audit-whitepapers in your project.

What does Audit Whitepapers need to run?

Going by SKILL.md and its folder, Audit Whitepapers needs the command-line tools its instructions call (git). Our summary lists: The claude-code-ultimate-guide repository layout, with a VERSION file and whitepapers in .qmd files.

Does Audit Whitepapers access the network?

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

Is Audit Whitepapers safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Audit Whitepapers use?

Audit Whitepapers is published under the CC-BY-SA-4.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Audit Whitepapers use?

About 3.8k tokens (SKILL.md is roughly 15k 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 Whitepapers?

Skills that share tags, products or a category with Audit Whitepapers: Aholo Viewer Docs (manycoretech/aholo-viewer, 1.1k stars), Sync Ja (aws-samples/sample-amazon-bedrock-agentcore-onboarding, 133 stars), Dx Devops Test Failures Analyze (forcedotcom/sf-skills, 1.1k stars) and Technical Analyst (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audit Whitepapers?

FlorianBruniaux (a GitHub user) maintains it in FlorianBruniaux/claude-code-ultimate-guide, which has 6,126 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.

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