weekly-setup-improvements
/weekly-setup-improvements -- Weekly Self-Improvement Audit
Audit the past 7 days of work in a folder and write a structured improvement report. This is state reflection, not journaling -- the output should be specific, actionable, and short enough that a busy practitioner will actually read it.
Core Principle
Every week generates patterns. Most patterns reveal an obvious next step -- a context file that needs updating, a slash command that should exist, a directory that needs cleaning. The cost of running this skill is a few minutes; the cost of not running it is invisible drift in the setup over months.
What This Skill Is (and Is Not)
| This skill | Not this skill | |
|---|---|---|
| Scope | One folder | Whole machine |
| Window | Trailing 7 days | All time |
| Output | Forward-looking actions | Backward-looking diary |
| Sibling | /vault-audit (snapshot, no time window), /claude-md-audit (CLAUDE.md drift only) |
Arguments
More from ngmeyer/skills
skillforge
Forge new Claude Code skills or optimize existing ones to V2. Two modes — `forge` scaffolds a new skill (frontmatter, progressive disclosure, helper scripts, mandatory Gotchas, iterate-then-extract); `optimize` makes an existing skill measurably better at its OUTCOME, not just its packaging (quality audit + domain outcome-research + changelog + V1-vs-V2 verification). Use when the user wants to create, write, build, scaffold, improve, upgrade, or optimize a skill.
1session-close
>
1six-pager
>
1claude-md
>
1session-recover
>
1council-review
Run any question, plan, PR, or code through a Diverse Multi-Agent Debate (DMAD) council of 5 AI advisors with distinct reasoning methods. Advisors collaborate, peer-review each other anonymously, and a chairman synthesizes a verdict. Empirically outperforms adversarial debate (M3MADBench 2026, DMAD ICLR 2025). Use when: 'council this', 'run the council', 'council review', 'pressure-test this', 'stress-test this', 'war room this', or when facing a genuine decision with stakes and tradeoffs.
1