review-artifact-comments SKILL.md skillA
review-artifact-comments from yonatangross/orchestkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yonatangross/orchestkit/review-artifact-comments@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yonatangross/orchestkit
- Path
plugins/ork/skills/review-artifact-comments/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 26, 2026
- Size
- 3,023 bytes
- Repository stars
- 299
- License
- MIT
Works through the review comments written into a task artifact (plan or research under .ork/tasks/TASK/): lists the open ones, asks how to proceed, then replies, resolves or hands off to iterate-plan or iterate-research, and approves the artifact once nothing is open. Use when a reviewer has commented on an artifact file or asks to address, resolve or approve its comments.
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
# review-artifact-comments
Comments live inside the artifact, in the block at its end (format: the create-plan skill's
`references/artifact-layout.md`). A reviewer adds one with the script or types it into the block by
hand; both are read the same way. Nothing here deletes a comment.
## Steps
1. **Pick the artifact.** Use the file given. Otherwise list the task directory and ask which one:
```bash
node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" status --task-dir .ork/tasks/<task>
```
2. **Read the artifact in full, then its open comments:**
```bash
node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" list --file <artifact> --open
```
3. **Ask how to proceed** unless the user already said (AskUserQuestion), for example:
- revise the artifact from the comments (hand off to `/ork:iterate-plan` or `/ork:iterate-research`)
- revise and resolve the comments it settles
- investigate the comments and reply with findings, no revision
4. **Work one comment at a time.** Check the claim in the code before answering. Reply with what you
found or changed:
```bash
…Read the whole file at its exact version.
How to install
mdr add yonatangross/orchestkit/review-artifact-comments@sha256:a2b14674468827a1The line at the top of this page pins the label v1.0.0, 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_pqoqv6od77x3l2yc)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 26, 2026.
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 (3023 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
yonatangross/orchestkit · 299 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pqoqv6od77x3l2yc GET https://markdownregistry.com/api/v1/resolve?ref=yonatangross/orchestkit/review-artifact-comments GET https://markdownregistry.com/api/v1/blob/a2b14674468827a1cc05cdfade6547cba63db66d3e7792d47096a346d2d99e2c
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.