flight-deck SKILL.md skillA
flight-deck from phuryn/product-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phuryn/product-engineering/flight-deck@git:20261108.4d8bb2bPins git:20261108.4d8bb2b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phuryn/product-engineering
- Path
agent-harness/skills/flight-deck/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261108.4d8bb2b, committed Nov 8, 2026
- First version recorded
- Nov 6, 2026
- Size
- 9,691 bytes
- Repository stars
- 643
- License
- MIT
'What's the status', 'where were we', a progress report or status deck; long work that must survive compaction: multi-hour runs, background jobs, waiting on a decision.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Flight Deck — surviving your own context window
**Write state down where it cannot be summarized.** In a long session, tool output scrolls away and context becomes a plausible narrative with operational details sanded off. The work keeps running while your model of it goes stale. Then you re-run a paid job, report a number from memory, or forget that something is blocked.
**The flight deck is `STATUS.md`, `LOG.md` and the owner's page.** When the Artifact tool exists, build the page in the first pass as an artifact with a database (`capabilities: {db: {}}`). Use `assets/owner-page.html`, following `references/owner-page.md`; use `OWNER.md` only when the tool does not exist. A test run, or one with nothing for the owner to decide yet, still builds the page. It carries status too, and a test exercises it. A scheduled pass with no chat never builds or publishes a page; it checks the one its prompt names.
## The two files (per area, not per repo)
**Rewrite `STATUS.md` in place to describe only what is true now.** Never append to it, because a growing status file leaves the reader unsure which line is still true. Use these sections where they earn their place:
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_dmpkvcpd4knwxifc/f7ce091ca26b4a4b20311bc03d415f67b25e97278c9d17f04242e6d6b7bb9bf6.json
Then /plugin install flight-deck@markdownregistry-dmpkvcpd4knwxifc in Claude Code. It installs git:20261108.4d8bb2b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add phuryn/product-engineering/flight-deck@sha256:f7ce091ca26b4a4bThe line at the top of this page pins the label git:20261108.4d8bb2b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_dmpkvcpd4knwxifc)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in phuryn/product-engineering/flight-deck since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of flight-deck from somewhere else? Ask it: where did my flight-deck come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Nov 6, 2026 and Nov 8, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261108.4d8bb2b latest | 2026-11-08 | 4d8bb2b | 9,691 B | A | view · diff |
| git:20261108.6aba512 | 2026-11-08 | 6aba512 | 9,650 B | A | view · diff |
| git:20261107.d3d1887 | 2026-11-07 | d3d1887 | 11,198 B | A | view · diff |
| git:20261107.c256b2c | 2026-11-07 | c256b2c | 11,186 B | A | view · diff |
| git:20261106.aafdf69 | 2026-11-06 | aafdf69 | 11,039 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/flight-deck/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9691 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
phuryn/product-engineering · 643 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dmpkvcpd4knwxifc GET https://markdownregistry.com/api/v1/resolve?ref=phuryn/product-engineering/flight-deck GET https://markdownregistry.com/api/v1/blob/f7ce091ca26b4a4b20311bc03d415f67b25e97278c9d17f04242e6d6b7bb9bf6
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.