CtrlK
BlogDocsLog inGet started
Tessl Logo

review

Smart review router. Detects context (morning, Sunday, end of month) and launches the appropriate review workflow. Use anytime for the right review at the right time.

50

Quality

56%

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/review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

The body presents a clear, well-prioritized detection workflow with concrete bash commands for most steps, but it is held back by an unimplemented staleness check and a monolithic single-file structure with some repetition across the routing/edge-case sections.

Suggestions

Make the Staleness check actionable: replace the comment-only "Read weekly review file for last date" with an actual command/snippet that computes days-since-last-review, mirroring the concrete style of steps 1–3.

De-duplicate the Routing Behavior, Delegation, and Edge Cases sections, which restate the same override/delegation rules, to tighten token use.

Consider splitting the detection logic into a referenced script or file and keeping SKILL.md as an overview, to add genuine progressive-disclosure structure.

DimensionReasoningScore

Conciseness

The body is mostly lean and uses concrete bash snippets rather than explaining concepts Claude knows, but the Routing Behavior, Delegation, and Edge Cases sections repeat the same delegation/override points and could be tightened.

2 / 3

Actionability

Detection steps 1–3 give executable commands (date +%H, +%u, +%d with a real days-in-month calc) and explicit thresholds, but step 4 (Staleness) is only comments/pseudocode ("Read weekly review file for last date") with no actual implementation, leaving key details missing.

2 / 3

Workflow Clarity

The detection cascade is clearly sequenced with explicit priority ordering (monthly > weekly > time-of-day), stated override behavior, a staleness pre-check, and an enumerated Edge Cases section, giving an unambiguous routing workflow.

3 / 3

Progressive Disclosure

The content is well-sectioned and self-contained with no nested references, but everything lives inline in a single ~115-line file with no progressive disclosure structure (e.g., the detection logic could be split out) and no referenced detail files.

2 / 3

Total

9

/

12

Passed

Description

50%

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 conveys a clear purpose (context-aware review routing) with a few concrete signals, but its trigger guidance is generic and it omits the natural terms (daily/weekly/monthly review) users would most likely say. It is solid but not comprehensive on any dimension.

Suggestions

Replace the generic "Use anytime for the right review at the right time" with explicit trigger conditions, e.g. "Use when the user asks for a review or says 'daily/weekly/monthly review', or wants the right review for the current time of day, day of week, or end of month."

Add the natural trigger terms users would say — "daily review", "weekly review", "monthly review", "review my day/week" — to improve trigger-term coverage.

Sharpen the action list from the abstract "launches the appropriate review workflow" to concrete outcomes like "routes to /daily, /weekly, or /monthly based on detected context".

DimensionReasoningScore

Specificity

Quotes "Detects context (morning, Sunday, end of month) and launches the appropriate review workflow" name the domain and some concrete signals, but the actions ("detects", "launches") are few and "launches the appropriate review workflow" is abstract rather than a comprehensive list of concrete actions.

2 / 3

Completeness

It states what the skill does, and includes a "Use anytime for the right review at the right time" clause, but that trigger guidance is generic ("anytime") rather than an explicit, specific when-condition, capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Terms like "morning", "Sunday", "end of month", and "review" are relevant, but common variations a user would actually say ("daily review", "weekly review", "monthly review") are missing.

2 / 3

Distinctiveness Conflict Risk

The time-based review-routing niche is somewhat specific, but the generic "Use anytime" trigger and broad "review" framing could still overlap with general review requests or sibling review skills.

2 / 3

Total

8

/

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.