Skip to content

aiskillstore/marketplace / skills/aaron-he-zhu/content-reviewer

content-reviewer

Verified

Use when the user asks to "review this influencer content" or "check if this post meets brand guidelines"; runs a typed C3 ART asset gate, checks disclosure and claim-integrity vetoes, and writes constructive revision feedback. Not for drafting the brief — use brief-generator; not for partnership terms — use contract-helper.

FileKindSize
SKILL.mdskill md7.8 KB
references/auditor-runtime.mdmarkdown10.4 KB
references/quality-review-aids.mdmarkdown2.1 KB
references/review-templates.mdmarkdown11.5 KB
skill-report.jsonconfig45.1 KB

references/quality-review-aids.md

View on GitHub
# Quality Review Aids — content-reviewer

Extra inputs for the **Quality Assessment** (step 5) and **Compliance / Platform-Specific** (step 4) sections. These do not change the ART veto set.

## ART quality penalty: AI-slop / humanizer signals (SOFT, non-veto)

When you score the **Creative Quality** category — specifically Authenticity and Native-feel — run the content through the slop checklist in [humanizer-slop.md](../../../../references/humanizer-slop.md). Hits map to the C³ **ART** quality dimension as a **soft penalty**, not a veto:

- Each cluster of slop signals (formulaic phrasing, hollow transitions, robotic cadence, banned filler words) docks the Creative Quality / Authenticity score.
- A high slop count routes the decision toward **REVISIONS REQUIRED**, never an automatic Reject.
- **The only ART vetoes remain T1 (FTC Disclosure) and T2 (Claim Integrity).** Slop never escalates to a veto and never forces a Reject on its own.

Record any penalty in the Creative Quality notes with the specific signals found, so the creator feedback is concrete.

## Multi-persona review

For higher-stakes or ambiguous submissions, run the content past the persona set in [expert-panel.md](../../../../references/expert-panel.md). Each persona reviews from one lens (e.g. brand, compliance, audience, platform-native), then reconcile their notes into the single gate decision. Use this when a solo pass feels under-confident, not for every routine submission.

## Per-platform format & disclosure norms

Before filling the **Platform-Specific Requirements** and **Technical Specifications** tables, load the matching platform note for current format limits and disclosure conventions:

- [platforms/tiktok.md](../../../../references/platforms/tiktok.md)
- [platforms/youtube.md](../../../../references/platforms/youtube.md)
- [platforms/x.md](../../../../references/platforms/x.md)
- [platforms/linkedin.md](../../../../references/platforms/linkedin.md)
- [platforms/reddit.md](../../../../references/platforms/reddit.md)

Platform norms inform the checks; the FTC disclosure veto (T1) still applies regardless of platform.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall