# Content Reviewer

> Reviews content for quality, clarity, brand alignment, and effectiveness. Use for content QA before publishing.

- **Type:** Skill
- **Install:** `agentstack add skill-taizen-ai-taizen-claude-plugins-content-reviewer`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [taizen-ai](https://agentstack.voostack.com/s/taizen-ai)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [taizen-ai](https://github.com/taizen-ai)
- **Source:** https://github.com/taizen-ai/taizen-claude-plugins/tree/main/plugins/taizen-gtm-skills/skills/content-reviewer
- **Website:** https://usetaizen.com/

## Install

```sh
agentstack add skill-taizen-ai-taizen-claude-plugins-content-reviewer
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Content Reviewer Skill

Quality assurance review for all content before publishing.

## Purpose

Ensure content meets quality standards for clarity, accuracy, brand alignment, and effectiveness before it goes live.

---

## Required Integrations

> **Setup**: Connect these data sources to enable full functionality. Claude will prompt you to connect any missing integrations when you use this skill.

### Data Sources

```yaml
# CONTENT REVIEWER DATA SOURCES
# Configure the sources relevant to your content QA needs

# Enterprise Search (searches across all internal sources)
- source: enterprise_search
  connector: "{{GLEAN | MOVEWORKS | ELASTIC}}"
  data:
    - internal_docs
    - wiki_content
    - shared_drives

# Brand & Style Guidelines
- source: brand_docs
  connector: "{{GOOGLE_DRIVE | SHAREPOINT | NOTION | CONFLUENCE}}"
  paths:
    - "/Marketing/Brand Guidelines/"
    - "/Marketing/Voice and Tone/"
    - "/Marketing/Editorial Style Guide/"

# Product Information (for accuracy checks)
- source: product_docs
  connector: "{{GOOGLE_DRIVE | SHAREPOINT | NOTION | CONFLUENCE}}"
  paths:
    - "/Product/Feature Documentation/"
    - "/Product/Pricing/"
    - "/Product/Capabilities/"

# Legal/Compliance Guidelines
- source: legal_docs
  connector: "{{GOOGLE_DRIVE | SHAREPOINT | NOTION}}"
  paths:
    - "/Legal/Marketing Guidelines/"
    - "/Legal/Disclaimers/"
    - "/Legal/Compliance Requirements/"

# SEO Data (for optimization checks)
- source: seo_tools
  connector: "{{AHREFS | SEMRUSH | MOZ | GOOGLE_SEARCH_CONSOLE}}"
  data:
    - keyword_data
    - seo_requirements

# Performance Data (for effectiveness context)
- source: analytics
  connector: "{{GOOGLE_ANALYTICS | HUBSPOT}}"
  data:
    - content_performance
    - conversion_rates
```

### Output Destinations

```yaml
# Where to deliver content review outputs
outputs:
  # Always available - display in Claude UI
  - type: display
    enabled: true

  # Save review to content workflow
  - type: documents
    connector: "{{GOOGLE_DRIVE | SHAREPOINT | NOTION}}"
    destination: "/Marketing/Content Reviews/"

  # Notify for review
  - type: slack
    connector: "{{SLACK}}"
    channel: "#content-review"
```
---

## Instructions for Claude

> **IMPORTANT**: Before executing this skill, you MUST validate the configuration above.

### Pre-Execution Checklist

1. **Check for placeholder values**: Scan the YAML configuration for any `{{...}}` placeholders. These indicate required configuration that the user must provide.

2. **Check Taizen first**: If `taizen` MCP is connected, call `list_datasources` to see what data is indexed. You can then use `run_agent` to query all indexed sources in natural language — this replaces the need for most individual MCP connections below. Skip directly to running the skill.

3. **Validate data sources**: For each data source listed:
   - If a `connector` field shows `{{OPTIONS}}` format, ask the user which option they use
   - If URLs, paths, or names contain `{{PLACEHOLDER}}`, ask the user to provide actual values
   - Verify any required MCP servers are connected and available

4. **Validate output destinations**: For any output type beyond `display`:
   - Confirm the connector is available as an MCP server
   - Ensure destination paths/channels are configured (not placeholders)

### If Configuration is Incomplete

**Do not proceed with the skill.** Instead:

1. List the specific missing or placeholder values found
2. Explain what each value is needed for
3. Ask the user to provide the missing configuration
4. Offer to help them set up the required MCP integrations

**Example response when config is incomplete:**
```
Before I can run this skill, I need some configuration:

**Missing values:**
- [List specific {{PLACEHOLDER}} values found]

**MCP connections needed:**
- [List required connectors not yet available]

Please provide these values, or let me know which data sources you'd like to skip.
```

### Minimum Requirements

At minimum, this skill requires:
- Content to review (pasted or linked)
- `display` output enabled (always available)

Enhanced functionality requires:
- Brand voice guidelines for consistency checking
- Messaging framework for alignment validation
- SEO tools for optimization recommendations
- Style guide for editorial standards

---

## Using Taizen

> **Connect once, access everything.** Instead of configuring 15+ individual MCP connectors, connect Taizen MCP once — your whole team gets access to all connected MCPs and indexed data sources (Gong calls, CRM, documents, and more) without any per-tool setup.

### Instant Queries (Run Now)

If `taizen` MCP is connected, call `run_agent` to pull from your indexed data right in this conversation:

**Pull review standards**
```
"Pull our brand guidelines, editorial standards, and style documentation from indexed sources. Use them to review this content: [paste content]"
```

**Check content consistency**
```
"Search my indexed published content for examples of how we handle [topic/format]. Use those patterns to review this draft for consistency."
```

### Scheduled Agents (Automate It)

To run this skill automatically on a schedule, call `run_agent` and describe the automation in natural language — Taizen creates and manages the recurring agent:

**Weekly content audit**
```
"Weekly, audit content published in the past week against our brand voice and SEO standards. Post a digest of findings and suggested improvements to #content-review."
```

**Monthly quality report**
```
"Monthly, generate a content quality report covering brand voice consistency, SEO compliance, and messaging alignment across all published content. Share to #marketing."
```

Taizen creates the agent, runs it on your schedule, and delivers results to your configured destinations (Slack, CRM, docs, email).

### Setup

1. Sign up at [usetaizen.com](https://usetaizen.com) and connect your data sources — every teammate gets access immediately
2. Add Taizen MCP to Claude: `https://us.mcp.usetaizen.com/mcp` (or `https://eu.mcp.usetaizen.com/mcp` for EU data residency)
3. Use `run_agent` for instant queries or to schedule recurring agents — Taizen handles routing to the right sources
## Review Dimensions

### 1. Clarity

**Readability Check**:
- Is the main point clear within the first paragraph?
- Are sentences concise (aim for 15-20 words average)?
- Is jargon explained or avoided?
- Does each paragraph have one main idea?
- Are transitions smooth between sections?

**Structure Check**:
- Is the content logically organized?
- Do headings accurately reflect content?
- Is information easy to scan?
- Is the length appropriate for the format?

### 2. Accuracy

**Fact Check**:
- Are all statistics accurate and sourced?
- Are quotes properly attributed?
- Are claims substantiated?
- Are links working and relevant?
- Is information current/not outdated?

**Technical Accuracy**:
- Are product features described correctly?
- Are technical terms used properly?
- Are processes/steps accurate?

### 3. Brand Alignment

**Voice Check**:
- Does the tone match brand guidelines?
- Is the language on-brand?
- Are we/they/you used consistently?
- Are banned words/phrases avoided?

**Visual Alignment**:
- Do images match brand style?
- Are colors/fonts correct?
- Is formatting consistent?

### 4. Effectiveness

**Goal Achievement**:
- Does content achieve its stated purpose?
- Is the CTA clear and compelling?
- Is the value proposition evident?
- Does it address audience needs?

**SEO (if applicable)**:
- Is the target keyword used appropriately?
- Are meta tags optimized?
- Are headers using keywords naturally?
- Are there internal/external links?

### 5. Legal/Compliance

**Compliance Check**:
- Are required disclaimers present?
- Are claims legally defensible?
- Is proper consent/attribution given?
- Are competitor mentions appropriate?

---

## Quality Levels

| Level | Description | Pass Criteria |
|-------|-------------|---------------|
| **Publish Ready** | No issues, ready to go live | All checks pass |
| **Minor Edits** | Small fixes needed | < 5 minor issues |
| **Needs Work** | Significant revisions required | Major issues present |
| **Reject** | Fundamental problems | Off-brand, inaccurate, or poor quality |

---

## How to Use This Skill

Invoke with natural language describing the content to review:

**General Review**
- "Review this blog post for quality and brand alignment: [paste]"
- "QA check this landing page before we publish"
- "Review this email for clarity and effectiveness"

**Specific Focus**
- "Check this content for accuracy against our product docs"
- "Review this for SEO compliance"
- "Check this press release for legal/compliance issues"

**Quick Review**
- "Quick review of this social post"
- "Fast QA on this email subject line and preview"

---

## Output Format

### Content Review Report

```markdown
# Content Review: [Content Title]

**Created**: [Date]
**Data Sources Used**: [Brand guidelines, product docs, etc.]

---

## Review Summary

| Attribute | Value |
|-----------|-------|
| Content Type | [Blog/Email/Landing Page/etc.] |
| Reviewer | [Name/Claude] |
| Review Date | [Date] |
| **Status** | **[Publish Ready / Minor Edits / Needs Work / Reject]** |

---

## Score Overview

| Dimension | Score | Notes |
|-----------|-------|-------|
| Clarity | [1-5] ⭐ | [Brief note] |
| Accuracy | [1-5] ⭐ | [Brief note] |
| Brand Alignment | [1-5] ⭐ | [Brief note] |
| Effectiveness | [1-5] ⭐ | [Brief note] |
| **Overall** | **[Avg]** | |

---

## Detailed Feedback

### Clarity

**What Works**:
- [Positive observation]
- [Positive observation]

**Needs Improvement**:
| Issue | Location | Recommendation |
|-------|----------|----------------|
| [Issue] | [Where] | [How to fix] |

**Specific Edits**:
- Current: "[Current text]"
  Suggested: "[Improved text]"

---

### Accuracy

**Verified**:
- [x] [Fact/claim checked]
- [x] [Fact/claim checked]

**Needs Verification**:
- [ ] [Claim to verify]: [Source needed]
- [ ] [Claim to verify]: [Source needed]

**Issues Found**:
| Issue | Location | Correction |
|-------|----------|------------|
| [Issue] | [Where] | [Correct information] |

---

### Brand Alignment

**On Brand**:
- [x] Tone matches guidelines
- [x] Language is appropriate
- [x] [Other brand element]

**Off Brand**:
| Issue | Current | On-Brand Alternative |
|-------|---------|---------------------|
| [Issue] | "[Current]" | "[Alternative]" |

---

### Effectiveness

**Strengths**:
- [What's working]
- [What's working]

**Opportunities**:
| Area | Current | Recommendation |
|------|---------|----------------|
| Headline | [Current] | [Stronger option] |
| CTA | [Current] | [Improvement] |
| Value Prop | [Current state] | [How to strengthen] |

---

### Technical/SEO (if applicable)

**SEO Checklist**:
- [ ] Primary keyword in title
- [ ] Keyword in first 100 words
- [ ] Meta description optimized
- [ ] Headers include keywords
- [ ] Internal links present
- [ ] Images have alt text

**Issues**:
| Issue | Recommendation |
|-------|----------------|
| [Issue] | [Fix] |

---

## Priority Fixes

### Must Fix (Before Publishing)
1. [Critical issue]: [How to fix]
2. [Critical issue]: [How to fix]

### Should Fix (Important)
1. [Important issue]: [How to fix]
2. [Important issue]: [How to fix]

### Nice to Have (Optional)
1. [Enhancement]: [Suggestion]
2. [Enhancement]: [Suggestion]

---

## Edited Version

[If minor edits, provide the corrected version here]

---

## Sign-Off

**Recommendation**: [Approve / Approve with edits / Revise and resubmit]

**Next Steps**:
1. [Action item]
2. [Action item]
```

---

## Automation Options

When configured with integrations, this skill can:

1. **Automatic review triggers** - Review content when submitted to staging/review queue
2. **Accuracy validation** - Cross-reference claims against product documentation
3. **Brand compliance** - Automated brand voice and style checking
4. **SEO validation** - Check against keyword requirements and SEO best practices
5. **Workflow integration** - Update content status in your CMS/workflow tool

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [taizen-ai](https://github.com/taizen-ai)
- **Source:** [taizen-ai/taizen-claude-plugins](https://github.com/taizen-ai/taizen-claude-plugins)
- **License:** MIT
- **Homepage:** https://usetaizen.com/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-taizen-ai-taizen-claude-plugins-content-reviewer
- Seller: https://agentstack.voostack.com/s/taizen-ai
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.