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

76%

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 ./plugin-variants/gbrain-daily/skills/daily-task-prep/SKILL.md

The canonical home for this skill is daily-task-prep in garrytan/gbrain

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 skill: concrete commands, specific data sources, a complete output template, explicit error-recovery loops, and clean section organization with one-level references. The remaining gaps are the Contract section duplicating the Phases, unspecified tool calls for attendee-context and task loading, and no inline validation checkpoint before the briefing is compiled.

Suggestions

Merge or trim the Contract section — it restates the Phases almost verbatim; fold the guarantees into the phase list or output format.

Name the exact tool calls for phases 1 and 3 (e.g., which of search/query/get_page/get_timeline to use for attendee brain pages and loading `ops/tasks`).

Add an inline validation checkpoint before Phase 4, e.g. confirm every meeting has attendee context and `gbrain waiting` succeeded before compiling the briefing.

DimensionReasoningScore

Conciseness

The ~49-line body is lean, assumes competence, and explains nothing Claude already knows, but the "Contract" section restates the four phases nearly verbatim ("Calendar/meetings for today are loaded with brain context per attendee" vs. Phase 1, "Open threads from yesterday are surfaced" vs. Phase 2) — minor duplication that could be trimmed. It is not 5 because of that redundancy and not 3 because every other section earns its tokens.

4 / 5

Actionability

Concrete guidance is present: a specific command ("`gbrain waiting --json` is the real data source"), a named data source ("Load `ops/tasks` from brain"), and a full copy-paste output template. It is not 5 because phases 1 and 3 do not specify the actual tool invocations (which of search/query/get_page/get_timeline to use for attendee context or task loading), and not 3 because the guidance is mostly executable with specific commands and a complete output format.

4 / 5

Workflow Clarity

The four numbered phases are clearly sequenced, and "When it fails" supplies genuine feedback loops ("run (or ask the user to run) the sync it names, then retry; do not prep from stale mail"). It is not 5 because the happy path lacks an inline validation checkpoint (e.g., confirming every meeting has attendee context before compiling the briefing), and not 3 because error-recovery checkpoints are explicit rather than missing.

4 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections (Contract, Phases, Output Format, When it fails, Anti-Patterns), and its external pointers are one level deep and clearly signaled ("see `skills/google-loops/SKILL.md`" and the linked agent-operator-protocol). Per the simple-skill guideline this earns a 5 with no separate bundle files needed.

5 / 5

Total

17

/

20

Passed

Description

66%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 specific, concrete, and distinct, naming four real capabilities in a tight frame without fluff. Its main weakness is completeness: it answers "what" thoroughly but never says "when" to use it, since no "Use when..." clause or trigger guidance appears in the description field itself. Adding an explicit when-clause with the natural trigger phrases would raise it to the good-example tier.

Suggestions

Append an explicit when-clause with concrete trigger phrases, e.g. "Use when the user asks for 'morning prep', 'prepare for today', or 'what's on my plate'."

Replace the vague "Extends briefing with actionable prep" with a concrete statement of the deliverable, e.g. "Compiles a per-meeting prep briefing with open threads and prioritized tasks."

Include a few natural synonyms users would say ("daily prep", "agenda", "today's meetings") to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Calendar lookahead, meeting context loading, open threads from yesterday, active task review" — matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because "Extends briefing with actionable prep" is vague and the concrete output (a compiled prep briefing) is only implied, and clears 3 because four distinct concrete actions exceed the 1-2 actions that anchor requires.

4 / 5

Completeness

The "what" is clear (calendar lookahead, meeting context loading, open threads, active task review) but the description contains no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. It is not 4 because the "when" half is entirely absent rather than present but imprecise, and not 2 because the "what" is concrete and multi-part.

3 / 5

Trigger Term Quality

Natural terms are present — "Morning preparation", "open threads", "active task review", "prep" — giving good keyword coverage with only a few natural variations missing, matching anchor 4. It is not 5 because common phrasings users would say ("agenda", "today", "daily overview", "what's on today") are absent, and not 3 because coverage goes well beyond the single-keyword anchor-3 example.

4 / 5

Distinctiveness Conflict Risk

The morning-preparation framing with calendar/meeting/thread/task terminology carves a mostly distinct niche. It is not 5 because "Extends briefing with actionable prep" signals a companion briefing skill with some overlap risk, and not 3 because the domain terms are specific enough to be clearly distinguishable from generic briefing or task-list skills.

4 / 5

Total

15

/

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

plugin-variants/gbrain-daily/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.