Agent skill
month-review
Monthly review and next-month planning for Obsidian monthly planning files and quarterly OKR notes. Analyze one month’s progress, map it into each quarterly objective, and update the objective-first monthly review area plus the month overview block without duplicating month headings. Use when the user asks for “月度复盘”“月总结”“下月计划”“OKR 回顾”“OKR 对齐”“month review” or similar month-level review/planning tasks.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/month-review
SKILL.md
Month Review
Use this skill to summarize one month from Plan/每日规划 and write the result into the matching quarterly OKR note under Plan/年度规划.
Read references/okr-month-review-patterns.md before editing. It captures the observed 2026 quarterly OKR structure, objective mapping, month-summary layout, and update rules.
Workflow
- Resolve the target month. Default to the current month. Honor an explicit month from the user.
- Locate the files needed:
- Read the monthly planning file(s) for the target month. Since a month’s tasks may appear across two adjacent month files, read both if the target month contains a week that spans months:
bash
obsidian read path="Plan/每日规划/{YYYY}/Q{Q}/{YYYY.MM}.md" - Locate and read the matching quarterly OKR file. Map the target month to its quarter first: months 1-3 →
第一季度, 4-6 →第二季度, 7-9 →第三季度, 10-12 →第四季度. Useobsidian search query="{YYYY} 第"if the exact filename is uncertain, then read it:bashobsidian read path="Plan/年度规划/{YYYY} OKR/{YYYY} 第{一|二|三|四}季度.md"
- Read the monthly planning file(s) for the target month. Since a month’s tasks may appear across two adjacent month files, read both if the target month contains a week that spans months:
- Analyze month progress using the counting rules in the reference file. Prefer parent-task counts when parent tasks own child checkboxes. Use nested checkbox progress as supporting detail instead of double-counting.
- Map the month’s outputs and misses into the quarterly objectives using the reference mapping. Reuse the current quarter’s O1-O4 headings exactly as written.
- Update in place in the quarterly OKR file:
- If appending a new month section under an objective, use
obsidian append path="..." content="..." silent. - If patching an existing month placeholder or summary block, use the Edit tool directly on the vault file.
- Do not create duplicate per-objective month headings or duplicate month-summary headings.
- If appending a new month section under an objective, use
- If the target month is still in progress, say
统计截至 {Today}in chat output and in the file where needed. - Keep insight concise. Prefer one short summary paragraph plus 1-3 next-month actions for each objective over raw task narration.
Output
- In chat, report work/personal progress, 3-6 milestones, 1-3 key patterns, and next-month focus by objective.
- In file, preserve the local OKR wording and section names already used in the quarterly note.
Guardrails
- If Obsidian is not running, fall back to reading vault files directly with the Read tool.
- Write to the quarterly OKR file, not to
2026 全年规划.md. - Treat the objective-first monthly review area as the primary write target when it exists.
- Support objective headings that are not exact bare
## O1:...strings, such as emoji-prefixed headings. - Ignore malformed checklist lines and explanatory bullets without checkboxes.
- If the quarterly OKR file is missing one of the expected objective sections, note the risk and update the existing structure as far as possible without inventing a new OKR taxonomy.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?