review SKILL.md skillA
review from silykat/silykat is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add silykat/silykat/review@git:20261014.c638277Pins git:20261014.c638277 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- silykat/silykat
- Path
adapters/claude-code/plugin/skills/review/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261014.c638277, committed Oct 14, 2026
- First version recorded
- Sep 27, 2026
- Size
- 9,684 bytes
- Repository stars
- 3
- License
- MIT
Address the user's silykat comments, i.e. the code review threads they left in VS Code with the silykat extension. Read the threads with `slk`, change the code, and reply in each thread. Use when the user asks you to handle, address, fix or answer their review comments, says their review is ready, or when a silykat channel message says they published comments. Also use it when the user asks to see the history of their review comments (resolved, deleted, every repository of the project), or to…
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
# Address the silykat comments The user reviews your code in VS Code and leaves comments in threads, like on a GitHub pull request. You answer in those threads with the `slk` command (it is on your PATH). Each reply shows up live in their editor. Asked for the **history** of the comments rather than to handle them? Skip to section 5 and run `slk review history` yourself. Asked to **archive**, **export** or **clean up** old comments? See section 6. ## 1. See what is waiting **Started by a silykat channel message** (`<channel source="…silykat…" store="<folder>" threads="<ids>">`): the user just published comments in that folder, and expects you to handle them without being asked. Add `--root <folder>` to every `slk` command below, and list only the threads of the message (`slk review list --root <folder> --thread <id> --thread <id>…`): the other threads waiting in that folder may be for another session. When you were busy with another task, finish or pause it at a sensible point first, then handle the comments, then go back to it. Run `slk review status`. If no thread waits for you, tell the user and stop. …
Read the whole file at its exact version.
How to install
mdr add silykat/silykat/review@sha256:0f0e35febeaeeb1dThe line at the top of this page pins the label git:20261014.c638277, 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_4vkwexknojd5m4so)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 27, 2026 and Oct 14, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.c638277 latest | 2026-10-14 | c638277 | 9,684 B | A | view · diff |
| git:20261012.3637cd5 | 2026-10-12 | 3637cd5 | 9,525 B | A | view · diff |
| git:20260927.7fbd93d | 2026-09-27 | 7fbd93d | 5,832 B | A | view · diff |
| git:20260927.cdfc339 | 2026-09-27 | cdfc339 | 5,687 B | A | view · diff |
| git:20260927.9418848 | 2026-09-27 | 9418848 | 5,089 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 (9684 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
silykat/silykat · 3 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4vkwexknojd5m4so GET https://markdownregistry.com/api/v1/resolve?ref=silykat/silykat/review GET https://markdownregistry.com/api/v1/blob/0f0e35febeaeeb1d185d5bb64f8ee61acd31d1ccba69cdb839d9d0dfaed67136
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.