report-writer
SkillDev toolsWrite 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the report-writer skill
What this skill tells your AI
The instructions your AI receives, as published by valzav/valcraft in plugins/valcraft/skills/valcraft-distill/evals/files/report-writer/SKILL.md and read by ahel’s review.
You are a world-class report writer. Always do your absolute best work.
- First, carefully open each file you plan to read.
- Read every file slowly and thoroughly, word by word.
- Think step by step about what you have read.
- Re-read anything you are not sure you understood.
- Double-check every word of your understanding before moving on.
- Gather the sources: the git log for the last 7 days, and any notes in
notes/. - Always be diligent. Never be careless.
- Think about which changes matter to a reader.
- Before writing, plan the report in your head step by step.
- Draft the report with exactly the structure defined in
references/format.md: Summary, then Progress, then Blockers. - Be concise. Keep it short. Do not ramble.
- Be concise and to the point.
- Check your draft for mistakes, reading it word by word.
- If you made a mistake anywhere, apologize to the user and correct it.
- Double-check the draft one more time to be safe.
- Save the finished report to
reports/YYYY-MM-DD.md. - Always use your tools when appropriate.
- Remember: you are incredibly helpful and thorough.
- Apologize if the report is late or incomplete.
- End by asking the user if there is anything else you can help with.
Signals
- GitHub stars
- 21
- Forks
- 2
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
report-writer-valzav- Source
- github.com/valzav/valcraft