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

vault-checkin

Skill179 starsChanged 8 months agoMITView on GitHub

Log a daily work check-in — records what was accomplished and syncs to task board

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Look for indicators: "@brett", "@brandon", name mentions, or context clues.

    line 16
  2. Very specific:

    If unclear, use ask_user to confirm.

    line 17
  3. Very specific:

    If a checkin already exists for this person today, use vault_update_entry to append.

    line 32
  4. Distinctive:

    If a match has high confidence (similarity > 0.5), offer to mark complete

    line 38
  5. Very specific:

    If uncertain, use ask_user: "Is '{work item}' the same as '{kanban task}'?"

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Log what the user worked on today.

Identify Who

Look for indicators: "@brett", "@brandon", name mentions, or context clues. If unclear, use ask_user to confirm.

Parse Input

Extract:

  • Work items: Things accomplished or worked on
  • Blockers: Anything preventing progress (optional)
  • Notes: Additional context or thoughts (optional)

Create Check-in

vault_create_entry(entry_type: "checkin", entry_date: "{today}", author: "{person}", ...)

Content should include work items as a bulleted list, blockers section, and notes section.

If a checkin already exists for this person today, use vault_update_entry to append.

Match to Kanban

For each work item that sounds like a completion:

  1. vault_kanban(action: "search", search_term: "{work_item}") to find matching tasks
  2. If a match has high confidence (similarity > 0.5), offer to mark complete
  3. If uncertain, use ask_user: "Is '{work item}' the same as '{kanban task}'?"
  4. Complete confirmed matches: vault_kanban(action: "complete", task_id: "...")

Refresh

vault_dashboard(dashboard_type: "activity") to update the dashboard.

Report: checkin file created, work items recorded, kanban matches found/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.