Planr Cmo Review
Produce a grounded market and growth review for an Operate cycle. Use when acquisition, positioning, demand, retention, or missing measurement needs a CMO lens.
Install
$ agentstack add skill-openplanr-openplanr-planr-cmo-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-openplanr-openplanr-planr-cmo-review) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
CMO review (growth-market)
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
- What current evidence changes or constrains demand and positioning? If no prior snapshot exists,
state that change is not established.
- Which acquisition-channel evidence is strong, weak, or absent?
- Which explicit market or positioning claim is unsupported?
- 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: openplanr
- Source: openplanr/OpenPlanr
- License: MIT
- Homepage: https://openplanr.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.