How do I install the Whereami skill?

Run npx skillmds@latest add dylanpulver/whereami in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Whereami safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Whereami?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Whereami free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Whereami?

dylanpulver (@dylanpulver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Whereami by dylanpulver — Agent Skill

Name: Whereami
Author: dylanpulver

Whereami

Answer 'where are we at and whats next' from a durable per-repo state ledger. Use for 'where are we at', 'whats next', 'tldr of where we stand', 'where did we leave off', 'take stock', resuming after a gap; update the ledger when work ships.

dylanpulver 6864c61 2.0 KB Updated Sep 17, 2026

File contents

whereami

"Where are we at / whats next / tldr" is one of the most-repeated prompts in any long-running project, and answers degrade after every compaction. Fix: a per-repo ledger file that outlives sessions, plus a read protocol that checks reality (git/gh) rather than trusting chat memory.

The ledger: `.claude/state.md` (per repo)

# State — <repo>
Updated: YYYY-MM-DD (session gist)

## In flight
- <workstream>: <one-line status> — next: <action> (blocked on: <who/what>, since <date>)

## Done recently
- YYYY-MM-DD <thing shipped/merged/decided>

## Sent
- YYYY-MM-DD <recipient/channel>: <one-line gist>

## Waiting on
- <who> owes <what> since <date>

## Parked / open questions
- <item>

Read mode (default)

Read .claude/state.md (if missing, offer to bootstrap it from git log + open PRs + this session).
Verify against reality before answering: git log --oneline -15, gh pr list, uncommitted changes. If ledger and reality disagree, reality wins — and fix the ledger.
Answer as TLDR ELI12: what shipped, what's in flight, what's blocked on whom, the single next action. Short — this is re-orientation, not a report.

Update mode (`update`, or proactively at the end of a substantial work session)

Rewrite the affected sections with what happened this session. Convert relative dates to absolute. Keep the file under ~60 lines — this is a dashboard, not a journal; prune "Done recently" past 2 weeks.

Why this also fixes parallel-session collisions

Two chats working the same repo both read/write the same ledger, so "consider this batch is already underway" no longer needs hand-pasting between chats. When starting a batch, note it under "In flight" immediately so sibling sessions see it.

---name: whereamidescription: Answer 'where are we at and whats next' from a durable per-repo state ledger. Use for 'where are we at', 'whats next', 'tldr of where we stand', 'where did we leave off', 'take stock', resuming after a gap; update the ledger when work ships.---# whereami"Where are we at / whats next / tldr" is one of the most-repeated prompts in any long-runningproject, and answers degrade after every compaction. Fix: a per-repo ledger file that outlives sessions, plus a read protocolthat checks reality (git/gh) rather than trusting chat memory.## The ledger: `.claude/state.md` (per repo)```markdown# State — <repo>Updated: YYYY-MM-DD (session gist)## In flight- <workstream>: <one-line status> — next: <action> (blocked on: <who/what>, since <date>)## Done recently- YYYY-MM-DD <thing shipped/merged/decided>## Sent- YYYY-MM-DD <recipient/channel>: <one-line gist>## Waiting on- <who> owes <what> since <date>## Parked / open questions- <item>```## Read mode (default)1. Read `.claude/state.md` (if missing, offer to bootstrap it from git log + open PRs + this session).2. **Verify against reality before answering:** `git log --oneline -15`, `gh pr list`, uncommitted changes. If ledger and reality disagree, reality wins — and fix the ledger.3. Answer as TLDR ELI12: what shipped, what's in flight, what's blocked on whom, the single next action. Short — this is re-orientation, not a report.## Update mode (`update`, or proactively at the end of a substantial work session)Rewrite the affected sections with what happened this session. Convert relative dates to absolute.Keep the file under ~60 lines — this is a dashboard, not a journal; prune "Done recently" past 2 weeks.## Why this also fixes parallel-session collisionsTwo chats working the same repo both read/write the same ledger, so "consider this batch isalready underway" no longer needs hand-pasting between chats. When starting a batch, note itunder "In flight" immediately so sibling sessions see it.

Frequently asked questions