vr-status
Skill1 starsChanged 2 months agoMITView on GitHub
Report where the VR project stands right now — current phase, what's done, what's blocked, and the literal next action. Use when the user asks "where are we", "what's next", or starts a session cold.
In this repository37 other files it gives its agents.
- wsb-data-pipelineSkill
- docx-exportSkill
- harvard-mdxSkill
- humanise-docx-reportSkill
- make-pdfSkill
- bom-builderSkill
- ring-testSkill
- batch-draftSkill
- cold-emailSkill
- cv-intakeSkill
- cv-upgradeSkill
- find-contactSkill
- followupSkill
- humanize-emailSkill
- log-outreachSkill
- outreach-statusSkill
- target-researchSkill
- erc-statusSkill
- log-sessionSkill
- score-auditSkill
- submission-checkSkill
- sumo-statusSkill
- trial-runSkill
- academic-registerSkill
- aviation-data-sourcesSkill
- business-frameworksSkill
- consultancy-registerSkill
- excel-deliverablesSkill
- forecasting-methodsSkill
- operations-frameworksSkill
- secondary-data-sourcesSkill
- archive-indexSkill
- event-proposalSkill
- meeting-minutesSkill
- read-boxnoteSkill
- captureSkill
- new-scriptSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read .claude/PROJECT_NOTES.md — the phase tracker and "What to do next" section are the source of truth.
- Very specific: line 15
Do models/source/ or models/exports/ contain any captures?
- Distinctive: line 18
If the notes and reality disagree, say so explicitly — stale notes are worse than no notes.
- Very specific: line 37
If an open question from PROJECT_NOTES.md is now blocking (e.g.
≈ “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.
Files
/vr-status — Project Status Report
Give the user a fast, honest snapshot of the project. No fluff.
Steps
- Read
.claude/PROJECT_NOTES.md— the phase tracker and "What to do next" section are the source of truth. - Cross-check reality vs the notes:
- Does
unity/contain a Unity project yet? (Look forunity/Assets/andunity/ProjectSettings/.) - Do
models/source/ormodels/exports/contain any captures? - Does
docs/CAPTURE_LOG.mdhave real entries (not just the template)? - Any uncommitted git changes worth mentioning?
- Does
- If the notes and reality disagree, say so explicitly — stale notes are worse than no notes.
Output format
## Phase: <N — name> (<status>)
**Done recently:** <1-3 bullets>
**In flight:** <what's actually being worked on>
**Blocked on:** <anything waiting — hardware, decisions, API keys — or "nothing">
## Next action (do this literally next)
<one concrete step, e.g. "Install Unity Hub from unity.com/download">Rules
- One next action, not five. The plan already lists everything; this skill picks the next thing.
- Respect phase discipline: never suggest a Phase N+1 task while Phase N lacks its deliverable.
- If an open question from PROJECT_NOTES.md is now blocking (e.g. "which location?" blocks Phase 1 capture), surface it as the next action.
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.

