agentleFS
pass-agentpass-agent/loomkin/.agents/skills/vault-okr/SKILL.md

vault-okr

Skill179 starsChanged 8 months agoMITView on GitHub

View, update, review, or create OKR cycles

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
  1. Distinctive:

    Add a weekly check-in section to the OKR entry content

    line 28
  2. Distinctive:

    Ask for key result updates

    line 33
  3. Distinctive:

    Ask for wins to note

    line 35
  4. Distinctive:

    Update entries and check if milestones should change

    line 36
  5. Very specific:

    Ask for cycle dates, objectives, key results per scope.

    line 41
  6. Distinctive:

    Update the OKR hub entry to list the new cycle.

    line 43
  7. Distinctive:

    Update OKR entries with retrospective section, mark as completed.

    line 49

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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_user for new value
  • Calculate status
  • vault_update_entry with 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.