monthly-docs-report
Generate a monthly documentation report from git history. Use this skill when the user asks to create a monthly docs report, monthly newsletter, or wants to summarize documentation changes for a specific month. Trigger when user mentions "monthly report", "docs newsletter", "documentation changes for [month]", or similar phrasing.
84
—
Does it follow best practices?
Impact
94%
1.54xAverage score across 2 eval scenarios
Passed
No known issues
Evaluation results
100%
32%March 2026 Documentation Newsletter
Monthly docs newsletter from git history
Correct filename
0%
100%
All five sections present
50%
100%
Summary Statistics — total commits
28%
100%
Summary Statistics — new pages count
100%
100%
Summary Statistics — config reference count
100%
100%
Summary Statistics — contributors count
42%
100%
Dependency commits excluded
60%
100%
New Pages section populated
100%
100%
Reference Updates section populated
100%
100%
Per-item bold title
100%
100%
Per-item PR number
100%
100%
Per-item contributor name
100%
100%
Per-item bullet descriptions
50%
100%
Factual language — no superlatives
20%
100%
Only March 2026 commits
100%
100%
88%
33%April 2026 Documentation Newsletter
Monthly docs newsletter style and attribution
No superlatives
0%
100%
No top-contributor ranking
100%
100%
Both Slack co-authors listed
100%
100%
Mixed PR in one section only
0%
0%
Typo fixes excluded
0%
100%
Per-item bold title
37%
100%
Per-item PR number
100%
100%
Per-item contributor after dash
37%
100%
Correct output filename
100%
100%
Summary Statistics section present
87%
100%
- Repository
- circleci/circleci-docs
- Commit
65ff472
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.