agentleFS
VeeiyVeeiy/vantage-os/skills/midday-pulse/SKILL.md

midday-pulse

Skill0 starsChanged 5 months agoMITView on GitHub

the operator's midday check-in. Use when the operator says "midday pulse", "where am I", "check in", "status check", or when a session starts between 11am and 5pm. Verifies progress on today's top 3, surfaces anything off-track, captures new decisions added since morning.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Maximum 1 page of output: If you need more, you're doing the wrong skill - use venture-triage instead.

    line 46
  2. Distinctive:

    No re-planning the day: If the operator wants to re-plan, that's its own conversation.

    line 47

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

Midday Pulse

Quick check-in. Shorter than morning brief. the operator is mid-day, probably tired (post-night-shift) or in the middle of school work, gym, or rental-fleet ops.

Read first

  1. ~/Vault/Vantage-OS/top-3.md
  2. ~/Vault/Vantage-OS/decisions.md (filter to items added today)
  3. ~/Vault/Vantage-OS/hair-product-state.md
  4. Tessie MCP if a rental-fleet trip is in progress

Ask the operator these three questions

  1. Of the 3 priorities, how many shipped? (0/3, 1/3, 2/3, 3/3, or skip the question if he obviously has)
  2. What changed since morning? (new info, blockers, decisions you need to log)
  3. Energy check. (going hard, coasting, fried) - if fried, propose a 30-min shutdown instead of more work.

Output

# Midday Pulse - [DATE]

## Progress
- ✓ [Shipped item]
- ⏳ [In progress - what's left]
- ✗ [Stalled - why]

## New since morning
- [New decision logged]
- [New info changing priorities]

## Adjusted afternoon plan
- [1-2 items max, not more]

## Flag
- [Any urgent thing - decision deadline today, rental-fleet issue, etc.]

Rules

  1. Maximum 1 page of output. If you need more, you're doing the wrong skill - use venture-triage instead.
  2. No re-planning the day. If the operator wants to re-plan, that's its own conversation.
  3. If 0/3 shipped by midday on a non-shift day, ask why honestly. Not in a guilty way. Diagnose: was the priority wrong, the estimate wrong, or was there a real interruption?
  4. If a rental-fleet trip is in progress, surface current odometer and mileage allowance check (via Tessie mileage-monitor skill).

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.