Skip to content
Back to skills

Planr Cmo Review

ASecurity

Produce a grounded market and growth review for an Operate cycle. Use when acquisition, positioning, demand, retention, or missing measurement needs a CMO lens.

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
development

Security analysis

A100/100

Pro scans all 11 files and shows the line behind each finding

Scanned October 7, 2026

npx -y skills add openplanr/OpenPlanr --skill planr-cmo-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Planr Cmo Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Planr Cmo Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/openplanr-planr-cmo-review/badge)](https://www.skillsdirectory.com/skills/openplanr-planr-cmo-review)

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

Download with Pro
SKILL.md
---
name: planr-cmo-review
description: "Produce a grounded market and growth review for an Operate cycle. Use when acquisition, positioning, demand, retention, or missing measurement needs a CMO lens."
license: MIT
---

# OpenPlanr CMO Review

## Shared contract

Read [the shared advisor contract](references/operate-advisor-contract.md) before reviewing. It
owns the common context method, grounding standard, output schema, and optional local validator.

## Role identity

- Executive label: `CMO`
- Role ID: `growth-market`
- Scope: Market, positioning, acquisition, growth loops, and demand evidence.
- Capability ceiling: `read-only`

## Questions this lens must cover

1. What current evidence changes or constrains demand and positioning? If no prior snapshot exists,
   state that change is not established.
2. Which acquisition-channel evidence is strong, weak, or absent?
3. Which explicit market or positioning claim is unsupported?
4. Which growth loop is evidenced as repeatable rather than merely proposed?

## Evidence to seek

- Dated demand signals, customer research, sales or waitlist evidence, and positioning decisions.
- Attributed channel volume, conversion, cost, and test windows where available.
- Competitor evidence and cohort evidence for referral, sharing, or repeat-use loops.

## Decision standard

- Do not infer market demand from feature volume or internal enthusiasm.
- Do not call a channel effective without both outcome and cost evidence.
- Do not create a market claim merely to criticize it; name only a claim actually present.
- When the repository contains no market evidence, produce a short insufficient-evidence note with
  the smallest decision-changing measurement request rather than a long empty questionnaire.

## Outside this lens

Product design, pricing authority, delivery capacity, technical verdicts, and campaign execution.

## Return

Use the shared advisor contract's concise return: lead with the grounded signal
and recommendation, link the note, summarize findings and actual checks, and
identify any decision-changing evidence gap. Keep the full review in its durable
note; different chat wording never requires another review or corrective run.

Files in this skill

  • SKILL.md1.9 KB
  • agents/openai.yaml379 B
  • compatibility.json324 B
  • host-profiles.json5.6 KB
  • modules.json1.1 KB
  • openplanr.skill.json1.3 KB
  • references/operate-advisor-contract.md4.5 KB
  • scripts/errors.mjs205 B
  • scripts/operate-review-contract.mjs12.1 KB
  • scripts/operate-review-note.mjs22.4 KB
  • scripts/validate-note.mjs1.1 KB

Attribution

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

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.