Team Okrs
OKR tracker page — quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar. Use when the brief mentions "OKRs", "key results", "objectives", or "目标".
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Team Okrs when an AI agent needs a reusable SKILL.md workflow for this job: OKR tracker page — quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar. Use when the brief mentions "OKRs", "key results", "objectives", or "目标".
When not to use it
Skip Team Okrs when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/team-okrs # Save SKILL.md to ~/.claude/skills/team-okrs/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/team-okrs/SKILL.md. For a shared project, commit the folder at .claude/skills/team-okrs/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Team Okrs skill for this task: Read DESIGN.md. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Team OKRs Skill
Produce a single-screen OKR tracker.
## Workflow
1. Read DESIGN.md. 2. Layout: - Quarter banner: Q4 FY25, dates, overall progress chip. - Three objective cards. Each has: - Objective title + owner avatar + status pill (On track / At risk / Off track) - 3 key results, each a row with metric / current → target / progress bar - Right sidebar: at-a-glance KPIs, top movers, blockers callout. 3. Clear progress visualisation, calm palette, one accent.
## Output contract
``` <artifact identifier="okr-q4" type="text/html" title="OKRs Q4"> <!doctype html>...</artifact> ```
Intended uses
- Read DESIGN.md.
- Layout:
- Quarter banner: Q4 FY25, dates, overall progress chip.
- Three objective cards. Each has:
- Objective title + owner avatar + status pill (On track / At risk / Off track)
- 3 key results, each a row with metric / current → target / progress bar
- Right sidebar: at-a-glance KPIs, top movers, blockers callout.
- Clear progress visualisation, calm palette, one accent.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.