CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

daily-task-prep

Morning preparation. Calendar lookahead, meeting context loading, open threads from yesterday, active task review. Extends briefing with actionable prep.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/daily-task-prep/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

A tight, well-structured instruction-only skill: a clear four-phase sequence, a concrete output template, an exact command with fallback logic, and a failure-handling section that delegates general protocol to an external file. The only notable weaknesses are the redundant Contract section and the absence of explicit tool invocations or validation checkpoints in the phases.

DimensionReasoningScore

Conciseness

The body is lean — no explanations of concepts Claude already knows, no library overviews, no filler — matching 'efficient; minor instances of over-explanation that could be trimmed'. It is not 5 because the 'Contract' section largely restates the four phases that follow ('Calendar/meetings for today are loaded... Open threads from yesterday are surfaced...') and could be cut or merged; it is not 3 because there is no genuinely unnecessary explanation beyond that redundancy.

4 / 5

Actionability

Concrete guidance dominates: the exact command 'gbrain waiting --json' with its data-source caveat and pointer to skills/google-loops/SKILL.md, the named brain page 'ops/tasks', a full output-format template, and explicit fallback behavior. This matches 'mostly executable guidance... with minor gaps'. It is not 5 because phases 1, 3, and 4 never name the actual tool invocations (which of search/get_timeline/list_pages to call for calendar loading or attendee context), leaving those steps as direction rather than executable instruction.

4 / 5

Workflow Clarity

Four clearly numbered, sequenced phases with conditional branching ('When google sources exist... Otherwise, search brain...') and a dedicated 'When it fails' section with recovery procedures (run the named sync, then retry; report degraded search instead of claiming 'no prior context') — matching 'clear sequence with most checkpoints present; minor validation gaps'. It is not 5 because the steps themselves contain no explicit validation checkpoints (e.g., confirming every meeting has attendee context before compiling the briefing); the destructive/batch cap does not apply since the skill is read-only (mutating: false).

4 / 5

Progressive Disclosure

The body is ~48 lines, under the 50-line threshold, with no bundle files (references/, scripts/, assets/ are absent) and no need for them — well-organized sections alone qualify for 5 per the scoring notes. It still practices good disclosure: general error handling is delegated one level deep via the clearly signaled link '[agent operator protocol](../conventions/agent-operator-protocol.md)' and the 'skills/google-loops/SKILL.md' pointer, keeping only skill-specific details inline. It is not 4 because there are no organization gaps — every section earns its place and both external references are explicit markdown/inline-path signals rather than buried.

5 / 5

Total

17

/

20

Passed

Description

58%Weight 40%Scale 1-5

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 compact, third-person description that names four concrete capabilities but omits any explicit 'when to use' guidance, leaving it reliant on the separate triggers field for invocation. Trigger-term coverage inside the description itself is moderate, missing several natural phrasings users would say. Distinctiveness is good with only minor overlap risk against a sibling briefing skill.

Suggestions

Add an explicit when-clause to the description, e.g. 'Use when the user asks for morning prep, a start-of-day briefing, or what's on their plate today' — this directly raises completeness from 3.

Fold natural trigger phrasings and synonyms into the description itself ('morning prep', 'daily briefing', 'start my day') instead of relying solely on the separate triggers array, improving trigger_term_quality.

Convert noun-phrase capabilities into verb-led third-person actions ('Surfaces open threads from yesterday', 'Loads attendee brain context per meeting') to sharpen specificity toward 5.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Calendar lookahead, meeting context loading, open threads from yesterday, active task review' — matching the anchor for several specific actions with minor gaps. It falls short of 5 because the actions are terse noun phrases with no operational detail and 'Extends briefing with actionable prep' is vague padding; it exceeds 3 because four distinct capabilities are named, not just the domain.

4 / 5

Completeness

The 'what' is clear (calendar lookahead, thread surfacing, task review, actionable prep briefing), but the description contains no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the guidelines ('when' is only weakly implied by 'Morning preparation'). It is not 4 because the when-condition must be explicit; the frontmatter's separate triggers array is outside the description field being evaluated.

3 / 5

Trigger Term Quality

Terms like 'Morning preparation', 'open threads', and 'active task review' are relevant but 'Calendar lookahead' is jargon-ish, and common natural variations ('morning prep', 'daily briefing', 'brief me for today', 'start my day') are absent from the description text itself — matching 'some relevant keywords but missing common variations or synonyms'. It is not 4 because several natural user phrases are missing; not 2 because the keywords present are on-topic rather than generic.

3 / 5

Distinctiveness Conflict Risk

The morning-prep niche (attendee brain context, yesterday's threads, P0/P1 tasks) is fairly distinct, matching 'mostly distinct; minor overlap risk with closely related skills'. It is not 5 because 'Extends briefing' explicitly signals a sibling briefing skill and generic phrases like 'active task review' could overlap a task-management skill; it is not 3 because the specific brain/meeting-context framing is clearly not generic.

4 / 5

Total

14

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

skills/daily-task-prep/SKILL.md

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.