daily-task-prep

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

Quality

80%

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

Quality

Content

86%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 body is a tight, well-structured instruction-only skill with a concrete output template and one real command. Its weakness is that several workflow phases give high-level direction rather than tool-specific executable steps.

Suggestions

Make Phases 1, 3, and 4 as concrete as Phase 2 by naming the specific tool calls or query syntax (e.g. which `get_timeline`/`list_pages` invocation loads attendee context).

Add a brief validation cue for Phase 2 (e.g. confirm `gbrain waiting --json` returned rows before flagging threads) so the sequence has an explicit checkpoint.

Clarify in Phase 3 how P0/P1 priority is determined from `ops/tasks` so the ordering step is reproducible.

Dimension	Reasoning	Score
Conciseness	The ~40-line body is lean with no padding or explanation of concepts Claude already knows; every section (Contract, Phases, Output Format, Anti-Patterns) earns its place.	5 / 5
Actionability	Provides one concrete command (`gbrain waiting --json`), specific paths (`ops/tasks`), and a copy-ready output template, but Phases 1, 3, and 4 stay high-level ("load attendee brain pages", "Surface P0 and P1 items") without tool-specific syntax.	4 / 5
Workflow Clarity	Four phases are clearly numbered and sequenced, with branching logic in Phase 2 ("When google sources exist... Otherwise..."); no explicit validation checkpoints, but the skill is read-only (mutating: false) so the destructive-cap does not apply.	4 / 5
Progressive Disclosure	Under 50 lines with well-organized sections and one clearly signaled one-level-deep reference (`skills/google-loops/SKILL.md`); no bundle files exist, so the well-organized inline structure satisfies the simple-skill exception.	5 / 5
	Total	18 / 20 Passed

Description

75%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 clearly states what the skill does with several concrete actions and supplies strong natural triggers via the `triggers` field. The main gap is that the "when" guidance lives in a separate field rather than the description prose, and "Extends briefing" introduces minor overlap ambiguity.

Suggestions

Fold a short "Use when..." clause into the description prose (e.g., "Use when doing morning prep, planning the day, or asking what's on your plate") so the "when" is explicit inline.

Tighten the closing line from "Extends briefing with actionable prep" to a concrete differentiator that distinguishes it from a generic briefing skill.

Add one or two common synonyms to triggers (e.g. "plan my day", "daily review") to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Calendar lookahead, meeting context loading, open threads from yesterday, active task review" — but the closing "Extends briefing with actionable prep" is generic, so it stops short of the fully comprehensive 5.	4 / 5
Completeness	The "what" is clear (the four prep actions), and the `triggers` field provides equivalent explicit trigger guidance for the "when"; it is not woven into the description prose, which keeps it just below a fully explicit 5.	4 / 5
Trigger Term Quality	The `triggers` field supplies natural phrases a user would say ("morning prep", "prepare for today", "what's on my plate", "day prep"); good coverage, though a few common synonyms (e.g. "daily standup prep", "plan my day") are missing.	4 / 5
Distinctiveness Conflict Risk	The morning-prep niche and its triggers are distinct, but the phrase "Extends briefing" signals overlap risk with a related briefing skill, so it is mostly distinct rather than minimal-conflict.	4 / 5
	Total	16 / 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: 8c70f62

Reviewed: 2 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.