report-writer SKILL.md skillA
report-writer from valzav/valcraft is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add valzav/valcraft/report-writer@git:20260826.7be1d15Pins git:20260826.7be1d15 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- valzav/valcraft
- Path
plugins/valcraft/skills/valcraft-hone/evals/files/report-writer/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260826.7be1d15, committed Aug 26, 2026
- Size
- 2,560 bytes
- Repository stars
- 22
- License
- MIT
Write a weekly progress report from the repository's recent activity. Use when the user asks for a progress report, a weekly report, or a status write-up.
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
# report-writer You are a world-class report writer for Claude 3.5. Follow every step exactly. 1. Take a deep breath and prepare to work carefully. 2. Open the repository in your mind and plan which files to read. 3. Carefully open the first file you plan to read. 4. Read the file slowly, word by word. 5. Think step by step about what you just read. 6. If anything was unclear, re-read the file from the beginning. 7. Double-check that you understood every word before moving on. 8. Repeat steps 3 through 7 for each remaining file. 9. Gather the git log for the last 7 days. 10. Read the git log carefully, entry by entry. 11. Think about each entry step by step. 12. Gather any notes in `notes/`. 13. Read each note carefully and completely. 14. Never skim. Never skip. Never rush. 15. Think about which changes matter to a reader. 16. Make a mental list of the important changes. 17. Verify your mental list against the git log one more time. 18. Plan the report in your head step by step before writing. 19. Remember to always be diligent and thorough. 20. Draft the Summary section: two or three sentences on what shipped. 21. Read your Summary draft back word by word. …
Read the whole file at its exact version.
How to install
mdr add valzav/valcraft/report-writer@sha256:4725100c913d91d5The line at the top of this page pins the label git:20260826.7be1d15, 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_oxcbm3oawllwn2te)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 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 (2560 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
valzav/valcraft · 22 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oxcbm3oawllwn2te GET https://markdownregistry.com/api/v1/resolve?ref=valzav/valcraft/report-writer GET https://markdownregistry.com/api/v1/blob/4725100c913d91d51dadcc87c4cde64e961cae251f159ed7b54a927e91af3afa
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.