CtrlK
BlogDocsLog inGet started
Tessl Logo

daily-review

Conduct an end-of-day review to capture progress and set up tomorrow. Use when the user asks for a daily review, end of day wrap-up, EOD note, what they did today, or wants to reflect on the day and plan tomorrow.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A clean, well-structured instruction skill that gives Claude a clear sequenced review process and a concrete copy-paste output template without padding in concepts Claude already knows. The main weakness is minor conciseness loss from duplicating the description and a moderately long inline template.

Suggestions

Remove the opening line that duplicates the YAML description, or replace it with a one-line scoping note that adds new information.

Consider whether the full output template could be trimmed to only the essential sections, or moved to a reference file if it grows further.

DimensionReasoningScore

Conciseness

The body opens by repeating the frontmatter description verbatim ("Conduct an end-of-day review to capture progress and set up tomorrow.") and the inline output template makes the body somewhat long for a single-purpose skill. It is mostly efficient with no concept explanations Claude would already know, but a small amount of redundancy and length could be tightened, matching the level-2 anchor rather than the fully lean level-3 anchor.

2 / 3

Actionability

The process lists concrete actions ("Find all notes modified today", "Move completed project tasks to archive", "Link related discoveries") plus a copy-paste-ready markdown output template with explicit sections. As an instruction-only skill the absence of code is not penalized because the guidance is concrete and specific, reaching the level-3 anchor.

3 / 3

Workflow Clarity

The four numbered phases (Today's Activity, Progress Assessment, Capture Insights, Tomorrow's Setup) form a clear, well-sequenced structure. This is a non-destructive reflective task, so the absence of validation/feedback checkpoints does not cap the score per the simple-skills guideline, and the sequence is unambiguous.

3 / 3

Progressive Disclosure

The skill is single-purpose and self-contained with no bundle files, organized into clearly labeled sections (Review Process, Output Format, Additional Actions) and no nested or multi-level references. For a self-contained single-task skill this matches the level-3 well-organized-sections anchor.

3 / 3

Total

11

/

12

Passed

Description

90%

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 strong description that clearly states what the skill does and provides multiple natural trigger phrases for when to use it, with a distinct EOD niche. The only weaker dimension is specificity, where the stated capabilities are slightly high-level rather than comprehensively enumerated.

Suggestions

Add one or two more concrete capabilities to the "what" portion (e.g., "summarizes notes touched today and surfaces open loops") to push specificity from level 2 to level 3.

DimensionReasoningScore

Specificity

It names the domain and two actions ("capture progress and set up tomorrow") but does not enumerate a comprehensive set of concrete capabilities, matching the level-2 anchor ("Names domain and some actions, but not comprehensive") rather than the level-3 anchor requiring multiple specific concrete actions. It is well above the vague level-1 anchor.

2 / 3

Completeness

It explicitly answers both what ("Conduct an end-of-day review to capture progress and set up tomorrow") and when (an explicit "Use when the user asks for a daily review..." clause), matching the level-3 anchor for both what and when with explicit triggers.

3 / 3

Trigger Term Quality

The "Use when" clause lists several natural phrases a user would actually say ("daily review", "end of day wrap-up", "EOD note", "what they did today", "reflect on the day and plan tomorrow"), giving good coverage matching the level-3 anchor.

3 / 3

Distinctiveness Conflict Risk

The end-of-day/EOD review niche has distinct, specific triggers ("EOD note", "end of day wrap-up", "what they did today") that are unlikely to fire for unrelated skills, matching the level-3 clear-niche anchor.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
heyitsnoah/claudesidian
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.