log-review SKILL.md skillA
log-review from byjunyoung/claude-product-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add byjunyoung/claude-product-skills/log-review@git:20261019.7908359Pins git:20261019.7908359 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- byjunyoung/claude-product-skills
- Path
plugins/pm/skills/log-review/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261019.7908359, committed Oct 19, 2026
- First version recorded
- Aug 28, 2026
- Size
- 8,340 bytes
- Repository stars
- 5
- License
- a license file GitHub does not identify
Turns a period of daily logs into accomplishment statements for a self-review, promotion case or CV. Triggers - "/pm:log-review", "turn last month's logs into highlights", "what did I accomplish this quarter", "성과 정리해줘", "이번 분기 뭐 했는지 정리", "이력서용으로 뽑아줘".
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
# log-review — a period of logs into accomplishment statements
**Part of a plugin.** The scripts this skill runs ship beside it under `${CLAUDE_PLUGIN_ROOT}`. If that path does not resolve, this file was installed on its own — stop and say the plugin itself is needed (`claude plugin install pm@byjunyoung`), rather than improvising what the scripts do.
Reads the daily files `/pm:log` wrote over a period and produces the thing those files cannot be used as directly: a short list of what you accomplished, phrased so it survives being pasted into a self-review or a CV. It works from what is on disk. It does not go back to the tracker, and it does not go to chat — if something is not in the logs, it did not get captured, and the honest answer is that it is missing.
**The judgement is yours, not the skill's.** A daily log knows that a status changed; it does not know whether that mattered, how much of it was your work, or what it can be measured by. Those three things are asked, never assumed. A period with no answers produces no statements, which is a correct outcome.
## Principles
…Read the whole file at its exact version.
How to install
mdr add byjunyoung/claude-product-skills/log-review@sha256:6bfd2febc722d484The line at the top of this page pins the label git:20261019.7908359, 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_42x2apsakeg7yjw6)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Aug 28, 2026 and Oct 19, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.7908359 latest | 2026-10-19 | 7908359 | 8,340 B | A | view · diff |
| git:20261019.5bdcdc0 | 2026-10-19 | 5bdcdc0 | 8,348 B | A | view · diff |
| git:20261018.958da1e | 2026-10-18 | 958da1e | 8,348 B | A | view · diff |
| git:20260902.e34cec9 | 2026-09-02 | e34cec9 | 8,379 B | A | view · diff |
| git:20260828.1134c3c | 2026-08-28 | 1134c3c | 8,085 B | A | view · diff |
| git:20260828.e2d0145 | 2026-08-28 | e2d0145 | 7,621 B | A | view · diff |
| git:20260828.278b10d | 2026-08-28 | 278b10d | 6,903 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 (8340 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
byjunyoung/claude-product-skills · 5 stars · license a license file GitHub does not identify · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_42x2apsakeg7yjw6 GET https://markdownregistry.com/api/v1/resolve?ref=byjunyoung/claude-product-skills/log-review GET https://markdownregistry.com/api/v1/blob/6bfd2febc722d4849a28ba44cc84931fdb32612822b538b674867d8cdc377379
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.
More from byjunyoung/claude-product-skills
Every file in byjunyoung/claude-product-skills