Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Gmkt Competitor Content Audit

ASecurity

Maps three to eight competitors' public content, with channels, themes, formats and posting rhythm, their claims sorted into table stakes, rare and specific, and the gaps nobody fills; a map, never a ranking. Use for "run gmkt-competitor-content-audit", "competitor content audit", "what are competitors doing on social", "competitor social media analysis", "audit competitor content", "how do we stand out from competitors", "everyone says the same thing", part of the Claude for Marketing Gradua...

2 stars
0 votes
0 copies
0 views
Added 10/5/2026
ai-agentsgo

Works with

cli

Security Analysis

A100/100

Scanned 10/5/2026

$npx -y skills add polar-bear-org/claude-skills --skill gmkt-competitor-content-audit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gmkt Competitor Content Audit?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Gmkt Competitor Content Audit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/polar-bear-org-gmkt-competitor-content-audit/badge)](https://www.skillsdirectory.com/skills/polar-bear-org-gmkt-competitor-content-audit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: gmkt-competitor-content-audit
description: Maps three to eight competitors' public content, with channels, themes, formats and posting rhythm, their claims sorted into table stakes, rare and specific, and the gaps nobody fills; a map, never a ranking. Use for "run gmkt-competitor-content-audit", "competitor content audit", "what are competitors doing on social", "competitor social media analysis", "audit competitor content", "how do we stand out from competitors", "everyone says the same thing", part of the Claude for Marketing Graduates Pack by Polar Bear.
---

# Competitor Content Audit

## When To Use
Your manager asks "what are competitors doing on social" by Friday. Use this when you need a clear picture of what the brands next to yours publish, which claims are so common they say nothing, and where the space is.

## When Not To Use
If the question is what your own brand should do about it, take the gaps into the SWOT Analysis; this audit only maps competitors. If you can name fewer than three competitors, the map will be thin: say so, or scroll their feeds for twenty minutes and note themes by hand.

## Inputs
- 3 to 8 competitors you name, and the channels that matter (for example Instagram, TikTok, LinkedIn, newsletter, website)
- One time window you set (for example the last 30 days)
- Their public posts, captions, page copy or screenshots, pasted (with Claude in Chrome on a paid plan, I can read the public pages you name; I do not go looking for more)
If you have none of this, I start from the competitor names and what you remember of their content, and mark the output as a first draft.

## Approach
A content audit (practitioner convention, no single originator) combined with a claims sort: every claim a brand makes about itself goes into one of three piles. Table stakes are claims half or more of the set make; rare are claims one or two make; specific are claims that come with something a reader could check. The judgment is that the table stakes pile is noise, not a lie. The failure this prevents: a 30-slide deck of screenshots ending "they post a lot of reels", with no sentence your team can act on.

## Workflow
1. Ask: which competitors and channels; what time window; is there a question behind the request (a launch, a new channel, a dip)?
2. Per competitor and channel, record themes, formats (carousel, short video, static image, text, link) and posting rhythm counted from what is visible in the window. Engagement goes in only if you observed it on the post; I never estimate reach or likes.
3. Extract every claim each brand makes about itself and rewrite it as a plain statement ("loved by thousands" becomes CLAIM: popular). Mark whether it came with evidence a reader could check (a named source, a number with a source, a described practice).
4. Sort the claims into piles: table stakes (half or more of the set make it), rare (one or two), specific (comes with something checkable, in any pile). You can move the half threshold.
5. Find the gaps: themes, formats or audience questions nobody covers, and the hard truths nobody admits (price, delivery times, what the product does not do). If a persona or Jobs to Be Done Map exists, note which forces nobody speaks to.
6. Write it up as a map: what is said, how often and by whom. No best competitor, no scores, no league table.

## Output Format
```markdown
# Competitor Content Audit
Set: [competitor A, B, C...] · Channels: [list] · Window: [dates] · Collected by: [name]
## Content map
| Competitor | Channel | Main themes | Formats | Posts in window |
|---|---|---|---|---|
| [competitor A] | [channel] | [themes] | [formats] | [count seen] |
## Claims
| Claim (plain statement) | Made by | Count | Evidence a reader could check |
|---|---|---|---|
| [claim] | [A, C, D] | [n of n] | [yes: what / no] |
## Piles
- Table stakes (half or more): [claims]
- Rare (one or two): [claims]
- Specific (checkable): [claims]
## Gaps
- Nobody covers: [themes, formats, questions]
- Nobody admits: [hard truths]
## Decision
[Name] decides which gap to explore in the SWOT or the next brief, by [date].
```

## Done When
- Every competitor row covers the same channels and the same window.
- Counts come only from what was visible; no estimated reach or engagement.
- Every claim has a pile and an evidence note.
- At least one gap is stated, or the map says plainly that none was found.

## Quality Bar
- Public brand content only; never collect anything about named employees, followers or reviewers.
- A thin set (under three competitors, one channel) is labelled thin at the top.
- Table stakes are described as noise, never as lies.
- Never invent a post, a claim or a count for a competitor whose content you were not given.
- Claude maps what competitors publish about themselves; it never invents their numbers or ranks them.

## Next
Run gmkt-swot-analysis (SWOT Analysis) to turn the gaps into opportunities for your brand.

## About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

Attribution

polar-bear-orgpolar-bear-org
View sourceSee grades on GitHubMore from polar-bear-org →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →