Okr Tracking
Draft and track OKRs — objectives with measurable key results, current values, and confidence/health. Use when the user says "write OKRs", "set objectives and key results", "track our OKRs", "quarterly goals", "are we on track for our KRs", or needs to define or check progress on measurable goals.
Install
$ agentstack add skill-janellecipriano-pm-skills-okr-tracking ✓ 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-janellecipriano-pm-skills-okr-tracking) 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
OKR Tracking
Help teams write OKRs that are ambitious and measurable, and track them honestly through the quarter.
When to use
- Drafting objectives and key results for a quarter/cycle.
- Reviewing/updating OKR progress and confidence.
Principles
- Objective = qualitative, inspiring, time-bound direction ("Become the default tool for X").
- Key Result = quantitative and verifiable — a number that moves, not a task ("Increase activation from 40%→60%"). If you can't measure it, it's not a KR.
- 1 objective : 2–4 key results. Avoid task-lists masquerading as KRs.
- KRs should be outcomes, not output/deliverables ("ship feature" is a task, not a KR).
- Set a baseline → target; stretch is healthy (≈70% attainment is often "good").
Process — drafting
- Write the objective — memorable, directional, for this cycle.
- Write 2–4 KRs, each with metric, baseline, target, and source of truth.
- Pressure-test: is each KR measurable, outcome-based, and influenceable by this team?
Process — tracking
- For each KR: current value, % to target, and a confidence (🟢 on track / 🟡 at risk / 🔴 off track).
- Note what's driving the number and the next action for at-risk KRs.
- Give the objective an overall health roll-up.
Output format
## Objective: {{O}} — Overall: 🟢/🟡/🔴
| KR | Baseline | Target | Current | % to target | Confidence | Notes / next |
| --- | --- | --- | --- | --- | --- | --- |Flag any KR that's really a task, and any objective with no measurable KR.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: janellecipriano
- Source: janellecipriano/pm-skills
- License: MIT
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.