C✳CODEZ.WIN
🌐 English

Localized reading guide

competitive-briefPurpose, usage and source

Create a competitive analysis brief for one or more competitors or a feature area. Use when informing product strategy or feature prioritization, building sales battle cards, prepping board or investor materials, or deciding where to differentiate vs. achieve parity.

Source retrieved:

Source repository
anthropics/knowledge-work-plugins
SKILL.md
product-management/skills/competitive-brief/SKILL.md
Repository stars
34,049
Repository updated
2026-10-30
Categories
Business
Last collected

License: License file needs review

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

Create a competitive analysis brief for one or more competitors or a feature area. Use when informing product strategy or feature prioritization, building sales battle cards, prepping board or investor materials, or deciding where to differentiate vs. achieve parity.

How the upstream workflow works

Competitor Overview

For each competitor: Company summary: founding, size, funding/revenue if public, target market Product positioning: how they describe themselves, who they target Recent momentum: launches, funding, partnerships, customer wins

Upstream passage · L50 ↗

Competitive Brief

> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Create a competitive analysis brief for one or more competitors or a feature area.

Upstream passage · L7 ↗

1. Scope the Analysis

Ask the user: Competitor(s): Which specific competitor(s) to analyze? Or a feature area to compare across competitors?

Upstream passage · L21 ↗
Upstream passage · ↗
/competitive-brief $ARGUMENTS

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256
720916695f99a70e723be02d0123908c9c968ce56e1ffdeeb423014587017cd2
Back to the full Skill catalog