Agent skill

Audit Content

by onvoyage-ai in onvoyage-ai/gtm-engineer-skills

Verifies truthfulness, accuracy, and link integrity of content before publishing.

MITAuto-check passedMarketing & SEO

Install Audit Content

skills CLI
$ npx skills add onvoyage-ai/gtm-engineer-skills --skill audit-content -a claude-code

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

GitHub CLI
$ gh skill install onvoyage-ai/gtm-engineer-skills audit-content --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/onvoyage-ai/gtm-engineer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/audit-content .claude/skills/audit-content && 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-content
GitHub stars
1.3k
Token cost
~1.9k tokens
SKILL.md length
934 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Verifies truthfulness, accuracy, and link integrity of content before publishing.

  • Works in 6 steps: Load context → Extract all verifiable claims → Verify external URLs → …
  • Tasks that involve Statistics
  • SKILL.md covers When To Use This Skill, Workflow, Output Format and Rules, plus 1 more section
  • Reaches pcma.org

What it does

Audit Content is an agent skill from onvoyage-ai/gtm-engineer-skills. Verifies truthfulness, accuracy, and link integrity of content before publishing. Catches fabricated statistics, dead URLs, misattributed sources, and company claims that contradict the brand DNA.

Its SKILL.md is about 1.9k 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 Marketing & SEO, covering Statistics and AI search optimization. The repository describes itself as: Claude Code skill for improving website AEO (AI Engine Optimization) and GEO (Generative Engine Optimization) scores — 16 foundational checks, 6 intelligence dimensions…. The licence is MIT.

When your agent uses it

  • Tasks that involve Statistics
  • Tasks that involve AI search optimization

Example prompts

  • “Use the audit-content skill to verify truthfulness, accuracy, and link integrity of content before publishing”
  • “/audit-content”

Workflow steps

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

  1. Load context
  2. Extract all verifiable claims
  3. Verify external URLs
  4. Verify statistics and research citations
  5. Verify company claims
  6. Check for internal consistency

What it can do on your machine

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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • pcma.org

    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 Content loads about 1.9k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 934 words of instructions outside code blocks.

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

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 onvoyage-ai/gtm-engineer-skills at commit 3777930, republished under its MIT licence (© onvoyage-ai). 934 words, ~1,906 tokens.

Download SKILL.mdSave it as .claude/skills/audit-content/SKILL.md (or your agent's skills folder).
name
audit-content
description
Verifies truthfulness, accuracy, and link integrity of content before publishing. Catches fabricated statistics, dead URLs, misattributed sources, and company claims that contradict the brand DNA.

Audit Content

You are a content auditor. Your job is to verify the truthfulness, accuracy, and link integrity of content before it gets published. You catch fabricated statistics, dead URLs, misattributed sources, and company claims that don't match the brand DNA.

When To Use This Skill

Use after writing content and before publishing. Run it on:

  • Individual articles
  • Batches of articles in a content folder
  • Any content that cites external sources, statistics, or company claims

Workflow

Step 1: Load context

Read the article(s) to audit. Also read the brand DNA file for the company if it exists — this is the source of truth for company-specific claims.

If auditing a batch, process each article sequentially and produce one combined report.

Step 2: Extract all verifiable claims

Scan the article and extract every claim that can be checked. Categorize each one:

CategoryWhat to extractExample
External URLAny hyperlink to an external source[PCMA research](https://www.pcma.org/...)
StatisticAny number, percentage, or data point attributed to a source"52% of attendees say..."
Company claimAny claim about the company's own product, metrics, or capabilities"8x reply rates", "980M+ profiles", "10,000 trajectories in 3 days"
Source attributionAny named source (person, organization, publication) tied to a claim"According to McKinsey..."
Research citationAny reference to a paper, study, or report"Aggarwal et al., KDD 2024"
Step 3: Verify external URLs

For every external URL in the article:

  1. Fetch the URL using web fetch to check if it resolves (200 OK)
  2. If the URL resolves, scan the page content to confirm the cited claim actually appears on that page
  3. Record the result:
    • PASS — URL resolves and the cited claim is supported by the page content
    • BROKEN — URL returns 404, 403, 500, or does not resolve
    • MISMATCH — URL resolves but the page does not support the specific claim attributed to it
    • UNVERIFIABLE — URL resolves but the content is behind a paywall, login wall, or the page is too dynamic to confirm

Do not skip URLs. Check every single one. This is the most important step.

Step 4: Verify statistics and research citations

For every statistic or research citation:

  1. If it has a URL, the URL check in Step 3 covers it
  2. If it has no URL but names a source, web search for the specific claim + source name to verify it exists
  3. If a statistic appears without any source attribution, flag it as UNSOURCED
  4. Check for common fabrication patterns:
    • Round numbers that sound made up ("exactly 47% improvement")
    • Statistics attributed to well-known sources but with no findable original (common LLM hallucination)
    • Numbers that don't match the original source (e.g., article says 52%, source says 48%)
    • Future-dated research that doesn't exist yet
Step 5: Verify company claims

Cross-reference every company-specific claim against the brand DNA file:

  1. Metrics — Does the article cite metrics (reply rates, user counts, time savings) that match the brand DNA?
  2. Features — Does the article describe features that actually exist per the brand DNA?
  3. Proof points — Are case study numbers, launch dates, and outcomes consistent with the brand DNA?
  4. Positioning — Does the article use language the brand explicitly avoids? (Check brand voice section)
  5. Competitor claims — Are competitor descriptions accurate and fair?

Flag any claim that:

  • Appears in the article but not in the brand DNA (could be fabricated by the writing agent)
  • Contradicts the brand DNA
  • Exaggerates or inflates a number from the brand DNA
  • Uses terminology the brand explicitly avoids
Show full SKILL.md (356 more words)Show less
Step 6: Check for internal consistency

Within the article itself:

  • Does the same statistic appear with different numbers in different sections?
  • Are dates consistent (e.g., "founded in 2024" in one place, "founded in 2023" in another)?
  • Do internal links point to URLs that match the content architecture?

Output Format

Produce an audit report as a markdown file saved alongside the audited content.

File naming
  • Single article: [article-slug]_audit.md
  • Batch audit: content_audit_[date].md

Save in the same directory as the content being audited.

Report structure
markdown
# Content Audit Report

> Audited: [date]
> Articles checked: [count]
> Brand DNA: [path to brand_dna.md used]

## Summary

| Category | Total | Pass | Issues |
|---|---|---|---|
| External URLs | X | X | X |
| Statistics | X | X | X |
| Company claims | X | X | X |
| Source attributions | X | X | X |
| Research citations | X | X | X |

**Overall: [X issues found across Y claims checked]**

## Issues

### Critical (must fix before publishing)

These will damage credibility if published as-is.

| # | Article | Claim | Category | Issue | Suggested Fix |
|---|---|---|---|---|---|
| 1 | [article] | "[exact claim text]" | BROKEN URL | URL returns 404 | Find updated URL or remove citation |

### Warnings (should fix)

These are not necessarily wrong but need attention.

| # | Article | Claim | Category | Issue | Suggested Fix |
|---|---|---|---|---|---|
| 1 | [article] | "[exact claim text]" | UNVERIFIABLE | Paywall blocks confirmation | Add note "cited from [source], paywalled" or find alternative source |

### Passed

All other claims that checked out. List count per article, not individual items.

| Article | URLs OK | Stats OK | Company Claims OK | Total Checked |
|---|---|---|---|---|
| [article] | X/Y | X/Y | X/Y | X |

Rules

  1. Check every URL. No exceptions, no sampling. If an article has 15 links, check all 15.
  2. Never assume a statistic is correct because it sounds plausible. Verify it.
  3. The brand DNA is the source of truth for company claims. If a claim isn't in the brand DNA and can't be verified externally, flag it.
  4. Be specific in suggested fixes. Don't just say "fix this" — say "replace with [X]" or "remove this citation and use [alternative source]."
  5. Don't rewrite the article. Your job is to audit and report, not to edit. The user or writing skill handles fixes.
  6. Flag hallucination patterns explicitly. If a URL looks like it was generated by an LLM (plausible-looking but nonexistent), say so.
  7. Distinguish between "wrong" and "unverifiable." A paywalled source is not the same as a fabricated one.
  8. Check arXiv papers by ID. ArXiv URLs follow a pattern (arxiv.org/abs/YYMM.NNNNN). Fetch the abstract page to confirm the paper exists and the cited claim matches.
  9. Time-bound your checks. If a source is dated (e.g., "2025 report"), confirm the report actually exists for that year. LLMs commonly hallucinate future-dated publications.
  10. Run this skill before any content goes live. It's cheaper to catch a fabricated stat now than to lose credibility after publishing.

What This Skill Does NOT Do

  • It does not check SEO quality (use improve-aeo-geo for that)
  • It does not check writing quality or style
  • It does not rewrite or fix content — it only reports issues
  • It does not evaluate whether the content strategy is good
  • It does not check for plagiarism (though obvious copy-paste from sources should be flagged)

© onvoyage-ai, 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 audit-content of onvoyage-ai/gtm-engineer-skills.

Open the folder on GitHubat commit 3777930

Compare with similar skills

Audit Content 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 Content compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audit Content this skillonvoyage-ai/gtm-engineer-skills1.3k—~1.9kAutomated safety check: PassMIT
Blog OutlineAgriciDaniel/claude-blog2.3k1 repos~1.5kAutomated safety check: PassMIT
Blog RewriteAgriciDaniel/claude-blog2.3k—~4.6kAutomated safety check: PassMIT
Blog BriefAgriciDaniel/claude-blog2.3k—~3.2kAutomated safety check: PassMIT
Blog BriefAgriciDaniel/claude-blog2.3k—~3.3kAutomated safety check: PassMIT
Blog RewriteAgriciDaniel/claude-blog2.3k—~4.8kAutomated safety check: PassMIT

Similar skills

  • Blog Outline

    AgriciDaniel/claude-blog

    SERP-informed outline generation with H2/H3 heading hierarchy, competitive content gap analysis, section-by-section word count targets, chart and image placement markers, optional FAQ question…

    2.3k GitHub starsUsed in 1 repo~1.5k tokens
    Marketing & SEOAuto-check passed
  • Blog Rewrite

    AgriciDaniel/claude-blog

    Rewrite and optimize existing blog posts for Google SEO (May 2026 Core Update, E-E-A-T) and AI citation visibility as one SEO discipline.

    2.3k GitHub stars~4.6k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Blog Brief

    AgriciDaniel/claude-blog

    Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…

    2.3k GitHub stars~3.2k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Blog Brief

    AgriciDaniel/claude-blog

    Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…

    2.3k GitHub stars~3.3k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Blog Rewrite

    AgriciDaniel/claude-blog

    Rewrite and optimize existing blog posts for Google SEO (May 2026 Core Update, March 2026 core/spam context, June 2026 spam context, E-E-A-T) and AI citation visibility as one SEO discipline.

    2.3k GitHub stars~4.8k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Blog Write

    AgriciDaniel/claude-blog

    Write new blog articles from scratch optimized for Google rankings and AI citations.

    2.3k GitHub stars~5.6k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed

More from onvoyage-ai/gtm-engineer-skills

All 12 skills in this repo
  • Audit Website Aeo

    onvoyage-ai/gtm-engineer-skills

    Audits a live website for AI-engine discoverability (AEO/GEO).

    1.3k GitHub stars~2.9k tokensUpdated 4 mo ago
    Auto-check passed
  • Research Brand

    onvoyage-ai/gtm-engineer-skills

    Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging.

    1.3k GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Research Keywords

    onvoyage-ai/gtm-engineer-skills

    Finds high-value SEO and GEO keywords using web search, AI analysis, and optionally paid tools like Ahrefs or Semrush.

    1.3k GitHub stars~4k tokensUpdated 4 mo ago
    Auto-check passed
  • Build Backlinks

    onvoyage-ai/gtm-engineer-skills

    Finds free backlink and brand mention opportunities across Hacker News, Quora, GitHub, directories, and niche communities.

    1.3k GitHub stars~2.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Build Resource Pages

    onvoyage-ai/gtm-engineer-skills

    Takes existing content markdown files and builds production-final resource center pages on client websites using their existing tech stack and design system.

    1.3k GitHub stars~3.6k tokensUpdated 4 mo ago
    Auto-check passed
  • Create Geo Charts

    onvoyage-ai/gtm-engineer-skills

    Creates data visualizations (charts, graphs, tables) optimized for AI engine parsing and citation.

    1.3k GitHub stars~4.3k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Audit Content

What does Audit Content do?

Verifies truthfulness, accuracy, and link integrity of content before publishing. Audit Content is an agent skill from onvoyage-ai/gtm-engineer-skills. Verifies truthfulness, accuracy, and link integrity of content before publishing.

When should I use Audit Content?

Audit Content fits situations like: tasks that involve Statistics; tasks that involve AI search optimization.

How do I install Audit Content in Claude Code?

Run `npx skills add onvoyage-ai/gtm-engineer-skills --skill audit-content -a claude-code`. Or copy the skill folder (audit-content in onvoyage-ai/gtm-engineer-skills) into .claude/skills/audit-content in your project. Claude Code loads it when a task matches its description.

How do I install Audit Content in Codex?

Run `npx skills add onvoyage-ai/gtm-engineer-skills --skill audit-content -a codex`. Or copy the skill folder (audit-content in onvoyage-ai/gtm-engineer-skills) into .agents/skills/audit-content in your project. Codex loads it when a task matches its description.

Can I use Audit Content 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 onvoyage-ai/gtm-engineer-skills --skill audit-content -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-content, .gemini/skills/audit-content, .github/skills/audit-content and .opencode/skills/audit-content in your project.

What does Audit Content need to run?

SKILL.md names no scripts, command-line tools or credentials: Audit Content is instructions for the agent only.

Does Audit Content access the network?

SKILL.md names 1 domain. In commands or code: pcma.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Audit Content 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 Content use?

Audit Content 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 Content use?

About 1.9k tokens (SKILL.md is roughly 7.6k 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 Content?

Skills that share tags, products or a category with Audit Content: Blog Outline (AgriciDaniel/claude-blog, 2.3k stars), Blog Rewrite (AgriciDaniel/claude-blog, 2.3k stars), Blog Brief (AgriciDaniel/claude-blog, 2.3k stars) and Blog Brief (AgriciDaniel/claude-blog, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audit Content?

onvoyage-ai (a GitHub organization) maintains it in onvoyage-ai/gtm-engineer-skills, which has 1,320 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on June 7, 2026.

Source: onvoyage-ai/gtm-engineer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.