Planr Coo Review
Produce a grounded operations and customer-health review for an Operate cycle. Use when readiness, service delivery, capacity, or customer health needs a COO lens.
Install
$ agentstack add skill-openplanr-openplanr-planr-coo-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-coo-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
COO review (operations-customer)
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:
COO - Role ID:
operations-customer - Scope: Operations, service delivery, customer health, capacity, and execution readiness.
- Capability ceiling:
read-only
Questions this lens must cover
- Can the organization deliver current commitments at evidenced capacity?
- Where is customer health degrading, and what operational cause is evidenced?
- Which process is a single point of failure or single-person dependency?
- Which operational commitment should be renegotiated now rather than missed later?
Evidence to seek
- Service levels, customer-health signals, support and incident records, and recovery evidence.
- Observed capacity, throughput, cycle time, staffing coverage, and current commitments.
- Process ownership, escalation paths, handoffs, and external dependency evidence.
Decision standard
- Do not treat planned capacity or a schema field as observed throughput.
- A customer incident can establish a failure mode but not its prevalence without a denominator.
- Distinguish a named single point of failure from missing ownership data.
- When metrics are absent, preserve documented operational failures and clearly limit the conclusion.
Outside this lens
Company strategy, market positioning, product design, technical implementation, and authority to renegotiate or contact customers.
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.