weekly

Facilitate weekly review process with reflection, goal alignment, and planning. Create review notes, analyze past week, plan next week. Use on Sundays or whenever doing weekly planning.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear phased workflow enforced by task dependencies, but it is over-padded with redundant sections and lacks both validation checkpoints for its destructive housekeeping steps and external reference files to keep the overview lean.

Suggestions

Add explicit validation/confirmation checkpoints before destructive batch operations — e.g., confirm with the user before archiving notes older than 30 days, and verify the archive succeeded before deleting originals.

Trim redundancy: merge 'Interactive Prompts' into 'Review Process Steps' and condense or remove the 'Best Practices' section, which restates常识 Claude already applies.

Move the full review-note template, agent-team workflow, and vault health check into separate reference files (e.g., references/review-template.md, references/agent-team.md) referenced one level deep from the overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-organized, but padded with redundant material — the 'Interactive Prompts' section restates the 'Review Process Steps', and 'Best Practices' (Consistent Timing, Preparation, Follow-through) adds context that assumes Claude needs hand-holding Claude already has.	2 / 3
Actionability	Provides copy-paste-ready, concrete guidance: explicit TaskCreate/TaskUpdate commands with dependencies, a full weekly-review note template, and a project-progress table format — fully executable rather than described.	3 / 3
Workflow Clarity	The 3-phase sequence is clear and enforced via TaskUpdate blockedBy dependencies, but batch/destructive operations ('Auto-Archive' notes older than 30 days, 'Archive completed items', 'Commit changes to Git') lack explicit validation checkpoints, which caps workflow clarity at 2 per the batch-operations guideline.	2 / 3
Progressive Disclosure	It is a single ~260-line monolithic SKILL.md with no bundle files; content such as the review-note template, agent-team workflow, and vault health check could be split into one-level-deep references, so it is structured but not optimally separated.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, specific, third-person, and provides explicit 'Use on...' trigger guidance covering both what the skill does and when to use it. It is a strong, well-formed skill description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create review notes', 'analyze past week', 'plan next week', alongside 'reflection, goal alignment, and planning' — matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers both what ('Facilitate weekly review process... Create review notes, analyze past week, plan next week') and when ('Use on Sundays or whenever doing weekly planning'), in third-person voice.	3 / 3
Trigger Term Quality	Uses natural terms a user would say ('weekly review', 'weekly planning', 'Sundays') with good coverage; not merely jargon, comfortably above the single-keyword anchor.	3 / 3
Distinctiveness Conflict Risk	Clear weekly-review/planning niche with distinct triggers ('Sundays', 'weekly planning'), unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: ballred/obsidian-claude-pkm
Path: vault-template/.claude/skills/weekly/SKILL.md
Commit: ef1e4da

Reviewed: about 1 hour ago

Table of Contents

Discovery Implementation Validation

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.