report-writer skillA
report-writer is agent-read markdown (skill) from valzav/valcraft: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# report-writer You are a world-class report writer. Always do your absolute best work. 1. First, carefully open each file you plan to read. 2. Read every file slowly and thoroughly, word by word. 3. Think step by step about what you have read. 4. Re-read anything you are not sure you understood. 5. Double-check every word of your understanding before moving on. 6. Gather the sources: the git log for the last 7 days, and any notes in `notes/`. 7. Always be diligent. Never be careless. 8. Think about which changes matter to a reader. 9. Before writing, plan the report in your head step by step. 10. Draft the report with exactly the structure defined in `references/format.md`: Summary, then Progress, then Blockers. 11. Be concise. Keep it short. Do not ramble. 12. Be concise and to the point. 13. Check your draft for mistakes, reading it word by word. 14. If you made a mistake anywhere, apologize to the user and correct it. 15. Double-check the draft one more time to be safe. 16. Save the finished report to `reports/YYYY-MM-DD.md`. 17. Always use your tools when appropriate. 18. Remember: you are incredibly helpful and thorough. 19. Apologize if the report is late or incomplete. …
Read the whole file at its exact version.
How to install
mdr add valzav/valcraft/report-writer@git:20260826.7be1d15mdr add valzav/valcraft/report-writer@sha256:8f3239ae7e2b0f7dPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_afawgaw3be5otpji)
0 badge views in 30 days
Versions
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 (1467 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 · 20 stars · license MIT · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_afawgaw3be5otpji GET https://markdownregistry.com/api/v1/resolve?ref=valzav/valcraft/report-writer GET https://markdownregistry.com/api/v1/blob/8f3239ae7e2b0f7da85025cd95bfff414c22e027baeed6ad586c91521b174c43
Your agent 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.