daily-task-prep

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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.

The content is a tight, well-structured instruction skill: sequenced phases, one concrete CLI command, a defined output template, and explicit anti-patterns. Remaining gains are minor — merging the redundant Contract section and naming the exact tool calls for calendar and timeline loading.

Dimension	Reasoning	Score
Conciseness	The body is lean — short phases, a compact output template, and no concept explanations Claude already knows. Not a 5 because the 'Contract' section (e.g., 'Calendar/meetings for today are loaded with brain context per attendee') largely duplicates the Phases and could be trimmed.	4 / 5
Actionability	Includes a concrete command ('gbrain waiting --json'), a specific data path ('Load ops/tasks from brain'), and a copy-paste-ready output template. Not a 5 because phases 1 and 4 rely on prose direction ('load attendee brain pages, recent timeline', 'Compile prep briefing') without naming the specific tool invocations.	4 / 5
Workflow Clarity	Four clearly sequenced numbered phases with a defined output contract and anti-patterns; the skill is read-only (mutating: false), so the destructive/batch validation cap does not apply. Not a 5 because there are no validation/edge-case checkpoints (e.g., what to do when there are no meetings or no google sources).	4 / 5
Progressive Disclosure	The body is under 50 lines, needs no external references (no references/, scripts/, or assets/ bundle exists), and is organized into well-labeled sections (Contract, Phases, Output Format, Anti-Patterns). The single cross-skill pointer to 'skills/google-loops/SKILL.md' is clearly signaled and one level deep, matching the simple-skill scoring note.	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.

The description is concise, specific, and third-person, clearly stating four concrete capabilities. Its main weakness is the complete absence of explicit 'when to use' guidance and natural trigger phrases, leaving a reader unsure when this skill applies versus related briefing skills.

Suggestions

Append a 'Use when...' clause to the description, e.g. 'Use when the user asks for morning prep, day prep, or what's on their plate today' — this lifts completeness and trigger-term quality together.

Add natural synonym phrases users would actually say (e.g., 'prepare for today', 'today's agenda', 'catch me up on open threads') so trigger matching works from the description text alone.

Clarify 'Extends briefing with actionable prep' by naming the relationship to the sibling briefing skill, reducing conflict risk between the two.

Dimension	Reasoning	Score
Specificity	Names the domain ('Morning preparation') and several concrete actions — 'Calendar lookahead, meeting context loading, open threads from yesterday, active task review' — in third person. Not a 5 because 'Extends briefing with actionable prep' is vague and the actions are terse noun phrases with minor coverage gaps (e.g., what 'meeting context loading' entails).	4 / 5
Completeness	The 'what' is clear (four concrete prep activities), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, capping completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete, not vague.	3 / 5
Trigger Term Quality	Relevant keywords are present ('Morning', 'Calendar', 'meetings', 'open threads', 'tasks', 'prep') but the description contains no natural trigger phrases or synonym variations users would say. It fits anchor 3 ('some relevant keywords but missing common variations') rather than 4, which expects good natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	The morning-prep niche (calendar + yesterday's threads + task priorities) is fairly distinct, though 'Extends briefing' signals overlap with a closely related briefing skill. Minor overlap risk with that sibling skill, not the high-conflict breadth of anchor 3 or below.	4 / 5
	Total	14 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: garrytan/gbrain
Path: skills/daily-task-prep/SKILL.md
Commit: e78f1c3

Reviewed: 5 days 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.