eng-status-rollup SKILL.md skillA
eng-status-rollup from skillmedev/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add skillmedev/skills/eng-status-rollup@git:20261005.bea4ea5Pins git:20261005.bea4ea5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- skillmedev/skills
- Path
skills/eng-status-rollup/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261005.bea4ea5, committed Oct 5, 2026
- First version recorded
- Jul 5, 2026
- Size
- 6,771 bytes
- Repository stars
- 19
- License
- MIT
Rolls up engineering team status into an exec-ready written update with exactly three sections - progress in outcomes, risks with likelihood and mitigation, and asks with owners and deadlines - scannable in under 90 seconds. Use when someone asks "write my weekly eng update", "summarize team status for leadership", "turn these standup notes into an exec update", or is prepping for a leadership sync. Do NOT use for updates to external or cross-functional stakeholders on a project - use…
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
# Eng Status Rollup
Execs do not need a feature list. They need three answers: are we on track, what might go wrong, and what do you need from us? A rollup that buries those answers under activity logs trains leadership to skim it - and then the one week the update contains a real red flag, nobody reads it. Everything in this skill defends the 90-second scan.
## Operating procedure
### Step 1: gather inputs
- The raw material: standup notes, sprint board, incident log, whatever exists for the period since the last update.
- The last rollup sent, so claims stay consistent - a risk that silently disappears without a resolution line destroys credibility faster than the risk itself would have.
- The audience (direct exec, VP group, company-wide) and the milestone or date the team is publicly committed to.
- Anything the manager knows but hasn't written down; ask directly "what are you worried about this week?" - the real risk is usually in the answer, not the ticket system.
If a claim is unverified ("I think the migration is on schedule"), label it as unconfirmed rather than rounding up to green.
### Step 2: write Progress - outcomes, max 4 bullets
…Read the whole file at its exact version.
How to install
mdr add skillmedev/skills/eng-status-rollup@sha256:49ab70a4adbd41e1The line at the top of this page pins the label git:20261005.bea4ea5, 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_5y7v57ts34buguz6)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 5, 2026 and Oct 5, 2026, about one every 46 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.bea4ea5 latest | 2026-10-05 | bea4ea5 | 6,771 B | A | view · diff |
| git:20260705.a28c4ce | 2026-07-05 | a28c4ce | 6,732 B | A | view · diff |
| git:20260705.acb5571 | 2026-07-05 | acb5571 | 6,794 B | A | view |
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 (6771 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
skillmedev/skills · 19 stars · license MIT · pushed 2026-10-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5y7v57ts34buguz6 GET https://markdownregistry.com/api/v1/resolve?ref=skillmedev/skills/eng-status-rollup GET https://markdownregistry.com/api/v1/blob/49ab70a4adbd41e12d4a02d31ed660ff37ed36d39eaa7a12eb3d26e23a341b05
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.