project-ops SKILL.md skillA
project-ops from ericrisco/rsc-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ericrisco/rsc-harness/project-ops@git:20260729.086c7b3Pins git:20260729.086c7b3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ericrisco/rsc-harness
- Path
skills/project-ops/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260729.086c7b3, committed Jul 29, 2026
- First version recorded
- Jun 2, 2026
- Size
- 9,786 bytes
- Repository stars
- 236
- License
- MIT
Use when an operator wants to run a small or mid-sized project from a flat file instead of standing up Jira or Asana — dated milestones each with one named owner and a binary done-test, rule-driven RAG status, a RAID log, slippage detection, and a two-minute weekly status report. NOT sequencing the engineering work inside one approved plan (that is `tasks`).
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
# project-ops You run a project from one flat file, not a PM tool. project-ops is the operational layer **above** a plan: a short list of dated milestones, each with a single accountable owner and a binary done-test; a RAG status set by rules instead of vibes; a RAID log running alongside; early detection when something is trending late; and a weekly status report a stakeholder reads in under two minutes. Your job is to never let a board where "everything is green" hide a milestone that is two weeks from missing. You do not sequence engineering tasks (that is `../tasks/SKILL.md`) and you do not write the architecture plan (that is `../plan/SKILL.md`) — you keep the whole project honest above both. ## The artifact comes first Before any process, there is one file. Everything else updates it. A milestone table: ```markdown | id | milestone | owner | target | status | done_test | depends_on | |----|-----------|-------|--------|--------|-----------|------------| | M1 | Pricing copy approved | @ana | 2026-06-10 | done | Final copy signed off in doc | | | M2 | Pricing page built | @ben | 2026-06-18 | amber | URL returns 200 with new copy | M1 | …
Read the whole file at its exact version.
How to install
mdr add ericrisco/rsc-harness/project-ops@sha256:478e821db4f7a3cdThe line at the top of this page pins the label git:20260729.086c7b3, 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_3vtx235vedrb3psp)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 2, 2026 and Jul 29, 2026, about one every 58 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260729.086c7b3 latest | 2026-07-29 | 086c7b3 | 9,786 B | A | view · diff |
| git:20260602.484d945 | 2026-06-02 | 484d945 | 10,217 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 (9786 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
ericrisco/rsc-harness · 236 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3vtx235vedrb3psp GET https://markdownregistry.com/api/v1/resolve?ref=ericrisco/rsc-harness/project-ops GET https://markdownregistry.com/api/v1/blob/478e821db4f7a3cd145b98ea429fe8b6c364795c2988aef4725cfb56dc0fbd1e
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.