Skip to content
Agentmart
Submit a tool

document-review

Audits brand/ files for completeness, consistency, and freshness.

Skill by MoizIbnYousaf

IndexedMIT★ 32
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/moizibnyousaf-document-review

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Audits brand/ files for completeness, consistency, and freshness. Use when the agent or user wants to review brand files, audit marketing docs, check brand consistency, verify brand health, or assess what's missing from brand memory. Produces a structured audit report with per-file scores, cross-file contradiction detection, staleness flags, and recommended next skills to run. This is the quality gate for the brand memory system. Also use when someone says 'check my brand', 'brand audit', 'what's missing', 'is my brand ready', 'brand health', 'review my marketing docs', or before running any campaign to verify brand foundations are solid.

Use cases: documents, design, security, marketing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/document-review

What's inside

Skill name
document-review
Description
Audits brand/ files for completeness, consistency, and freshness. Use when the agent or user wants to review brand files, audit marketing docs, check brand consistency, verify brand health, or assess what's missing from brand memory. Produces a structured audit report with per-file scores, cross-file contradiction detection, staleness flags, and recommended next skills to run. This is the quality gate for the brand memory system. Also use when someone says 'check my brand', 'brand audit', 'what's missing', 'is my brand ready', 'brand health', 'review my marketing docs', or before running any campaign to verify brand foundations are solid.
License
MIT
Instructions
233 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • allowed-tools: must be a space-separated string

Files (1)

  • SKILL.md

SKILL.md (first lines)

# /document-review — Brand Document Audit

You audit the `brand/` directory for quality: completeness, consistency, and freshness. You report problems — you never fix them. Fixes belong to domain skills (e.g., `/audience-research` fixes `audience.md`).

For brand memory protocol, see /cmo [rules/brand-memory.md](../cmo/rules/brand-memory.md).

## On Activation

1. Verify `brand/` directory exists. If it does not exist, report Overall Health as **Not Started** and recommend `mktg init`. Skip all phases.
2. Read all 9 `brand/` files (or confirm which are missing).
3. Determine audit scope based on user request.
4. Run all four phases sequentially.

## Phase 0: Assess Scope

| Request | Scope |
|---------|-------|
| "review brand files" | Full brand/ audit (default) |
| "check audience.md" | Single-file deep review |
| "is my brand consistent?" | Consistency-only (Phase 2) |
| "what's stale?" | Freshness-only (Phase 3) |
| No specific request | Full brand/ audit |

For single-file reviews, still cross-reference against other brand files for consistency.

## Phase 1: Completeness Check

For each of the 10 brand files, assess status:

### Profile Files (7)

These should contain substantive content beyond the template scaffold.

| File | Key Sections | Owner Skill |
|------|-------------|-------------|
| `voice-profile.md` | Voice DNA (tone, personality, vocabulary), do/don't examples | `/brand-voice` |
| `positioning.md` | Core positioning (category, for, unlike, we), angles | `/positioning-angles` |
| `audience.md` | Primary audience (who, pain points, watering holes), personas | `/audience-research` |
| `competitors.md` | Named competitors with positioning, strengths, weaknesses | `/competitive-intel` |
| `keyword-plan.md` | Priority keywords table (keyword, intent, difficulty, priority) | `/keyword-research` |
| `creative-kit.md` | Brand colors, typography, visual style | `/creative` |
| `stack.md` | Available tools (email, social, video, search, media) | `mktg init` |

**Scoring:**

| Score | Meaning | Criteria |
|-------|---------|----------|
| **complete** | Ready for use | File exists, has substantive content beyond template, key sections populated |
| **partial** | Needs work | File exists but some key sections are empty or still contain template placeholders (`<!-- Generated by mktg init -->` without real content below) |
| **empty** | Template only | File exists but matches the `mktg init` template exactly (no customization) |
| **missing** | Not created | File does not exist |

**How to detect template-only content:**
- Look for lines like `- **Tone:**` with no value after the colon
- Look for empty table rows
- Look for `<!-- Generated by mktg init. Fill in or let /cmo build this. -->` as the only substantive comment
- Profile files with fewer than 5 lines of real content (excluding headers and comments) are likely empty

### Append-Only Files (2)

| File | Purpose | Owner |
|------|---------|-------|
| `assets.md` | Log of created assets | All skills (append) |
| `learnings.md` | What worked, what didn't, audience insights | All skills (append) |

**Scoring:**

| Score | Meaning | Criteria |
|-------|---------|----------|
| **complete** | Has entries | File exists with dated entries |
| **empty** | No entries | File exists but contains only the header/comment |
| **missing** | Not created | File does not exist |

Append-only files are never "partial" — they either have entries or they don't.

## Phase 2: Consistency Check

Cross-reference files for contradictions. Only check files that are `complete` or `partial` (skip `empty` and `missing`).

### Cross-References to Check

| Check | Files Involved | What to Look For |
|-------|---------------|-----------------|
| **Audience alignment** | `positioning.md` ↔ `audience.md` | Does positioning's "For:" match audience's primary persona? |
| **Voice-brand fit** | `voice-profile.md` ↔ `positioning.md` | Does the tone match the brand positioning? (e.g., playful voice + enterprise positioning = mismatch) |
| **Keyword-positioning alignment** | `keyword-plan.md` ↔ `positioning.md` | Do target keywords reflect the positioning angles? |
| **Competitor consistency** | `competitors.md` ↔ `positioning.md` | Are competitor names consistent across both files? |
| **Audience-keyword fit** | `audience.md` ↔ `keyword-plan.md` | Do keywords match the language/pain points of the target audience? |
| **Stack-skill alignment** | `stack.md` ↔ all profile files | Do other files reference tools or channels not listed in stack.md? |
| **Creative-voice alignment** | `creative-kit.md` ↔ `voice-profile.md` | Does visual style complement the voice? (e.g., minimalist design + maximalist voice = tension) |
| **Learnings integration** | `learnings.md` ↔ all profile files | Are learnings reflected in strategy? (e.g., learning says "short subject lines work" but voice profile favors long-form) |

### Contradiction Severity

| Severity | Meaning | Example |
|----------|---------|---------|
| **high** | Files directly contradict | Positioning targets "enterprise CTOs" but audience.md says "indie developers" |
| **medium** | Files are misaligned but not contradictory | Voice is "casual and fun" but positioning is "premium and exclusive" |
| **low** | Minor inconsistency | Different competitor names used (abbreviation vs full name) |

## Phase 3: Freshness Check

Flag files that may be outdated.

### Freshness Rules

- **Profile files**: Check file modification date. Flag as stale if older than 30 days.
- **Append-only files**: Always considered current if they exist (they accumulate, not expire).
- **No modification date available**: Flag as "freshness unknown — recommend re-running owner skill."

### Staleness Signals (Beyond Date)

- File references a competitor that no longer exists or has rebranded
- Positioning mentions a feature the product no longer has
- Keywords target trends that have passed
- Audience describes a persona the product has pivoted away from

Note these as "content staleness" separately from "date staleness."

From MoizIbnYousaf/marketing-cli, MIT.

More from MoizIbnYousaf/marketing-cli

Signals

Stars
32
Forks
5
Open issues
1
Last commit (this folder)
May 3, 2026 (5 months ago)
Last release
Aug 16, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from MoizIbnYousaf

Cite this page

document-review skill. Agent Mart. https://agentmart.dev/skills/moizibnyousaf-document-review (last updated 2026-10-24)