vault-okr
Skill179 starsChanged 8 months agoMITView on GitHub
View, update, review, or create OKR cycles
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- elixir-expertSkill
- find-skillsSkill
- modern-cssSkill
- vault-auditSkill
- vault-checkinSkill
- vault-dashboardSkill
- vault-groomSkill
- vault-ingestSkill
- vault-meetingSkill
- vault-prepSkill
- vault-streamSkill
- vault-updateSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Add a weekly check-in section to the OKR entry content
- Distinctive: line 33
Ask for key result updates
- Distinctive: line 35
Ask for wins to note
- Distinctive: line 36
Update entries and check if milestones should change
- Very specific: line 41
Ask for cycle dates, objectives, key results per scope.
- Distinctive: line 43
Update the OKR hub entry to list the new cycle.
- Distinctive: line 49
Update OKR entries with retrospective section, mark as completed.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Manage Objectives and Key Results. Parse arguments to determine subcommand:
view (default)
vault_list(tags: ["okr"]) — read all active OKR entries.
Present a formatted summary with objectives, key results, current values, targets,
and status indicators (On Track >= 70%, At Risk 40-70%, Off Track < 40%, Completed = 100%).
update
For each selected OKR and key result:
- Show current value and target
ask_userfor new value- Calculate status
vault_update_entrywith new frontmatter values- Add a weekly check-in section to the OKR entry content
review
Display current status (same as view), then for each OKR:
- Ask for key result updates
- Ask for blockers
- Ask for wins to note
- Update entries and check if milestones should change
new
Determine next cycle number from existing OKRs.
Ask for cycle dates, objectives, key results per scope.
vault_create_entry(entry_type: "okr", tags: ["okr"], ...) for each scope.
Update the OKR hub entry to list the new cycle.
retro
Display final status, prompt for retrospective content per OKR (what worked, what didn't, what to carry forward). Update OKR entries with retrospective section, mark as completed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

