CtrlK
BlogDocsLog inGet started
Tessl Logo

monthly

Monthly review and planning. Roll up weekly reviews, check quarterly milestones, set next month's focus. Use at end of month or start of new month.

62

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./vault-template/.claude/skills/monthly/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A well-structured, actionable review process with concrete file targets and a full output template, but it is over-long for a single file, lacks validation checkpoints around the goal-file write, and does not push the large output template into a reference.

Suggestions

Add an explicit verification step after writing Goals/2. Monthly Goals.md (e.g., re-read to confirm it saved, or ask the user to confirm before overwriting the existing plan).

Move the ~75-line output format template into references/output-template.md and link to it from the body so SKILL.md stays a lean overview.

Tighten the "Usage / Or ask" block and the pseudocode TaskCreate/TaskUpdate section, which duplicate the description and use placeholder IDs like [phase-1-id] instead of concrete calls.

DimensionReasoningScore

Conciseness

The body is mostly efficient procedural guidance with no concept over-explanation, but the ~75-line output template and the "Usage / Or ask" examples duplicate the description and could be tightened.

2 / 3

Actionability

Concrete file paths (Goals/2. Monthly Goals.md, Projects/*/CLAUDE.md), a sequenced 3-phase process, and a copy-paste-ready output template give Claude specific, actionable guidance; the TaskCreate blocks are illustrative but do not undermine the overall actionable core.

3 / 3

Workflow Clarity

The phases are clearly sequenced with time budgets and task dependencies, but writing the next month's plan to Goals/2. Monthly Goals.md is an overwrite with no validation or verification checkpoint, capping clarity per the destructive/batch-operations rule.

2 / 3

Progressive Disclosure

The single ~200-line file is well-sectioned, but no references/ files are used and the large inline output template is content that could be split out, so it is not a lean overview with one-level-deep references.

2 / 3

Total

9

/

12

Passed

Description

85%

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

A concise, third-person description that clearly states three concrete actions and an explicit temporal trigger, with a distinct monthly-cadence niche. Trigger-term coverage is good but leans on a temporal cue rather than the varied user utterances that live in the body.

DimensionReasoningScore

Specificity

"Roll up weekly reviews, check quarterly milestones, set next month's focus" lists three concrete, distinct actions rather than vague language.

3 / 3

Completeness

It states what ("Roll up weekly reviews, check quarterly milestones, set next month's focus") and gives an explicit when ("Use at end of month or start of new month"), answering both questions.

3 / 3

Trigger Term Quality

"Monthly review", "planning", and "end of month / start of new month" are natural, but the explicit trigger is a temporal cue and the most common user phrasings ("plan next month", "how did this month go") appear only in the body, so utterance coverage in the description itself is incomplete.

2 / 3

Distinctiveness Conflict Risk

The monthly cadence plus quarterly-milestone check is a clear niche with distinct temporal triggers, unlikely to fire for the related /weekly or /daily skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
ballred/obsidian-claude-pkm
Reviewed

Table of Contents

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.