briefing

Compile daily briefing with meeting context, active deals, and citation tracking

Quality

70%

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/briefing/SKILL.md

Quality

Content

75%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 highly actionable with concrete gbrain commands and a clear pre-pull-then-phases workflow backed by an invariant contract. Its main weakness is conciseness: redundant context-loading sections and some over-explanatory prose could be tightened, and progressive disclosure is good but not fully split.

Suggestions

Merge the "GBrain-Native Context Loading" section into Phases to remove the duplicated search/get guidance and tighten conciseness.

Trim rationale prose (e.g., the salience and personal-recall explanations) to the minimum needed to pick the right flag, trusting Claude to infer the rest.

Add an explicit final validation step (e.g., re-check each Contract bullet before emitting the briefing) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but there is real redundancy — the "GBrain-Native Context Loading" section repeats the search/get pattern already in Phases, and several prose rationales (e.g., salience, personal recall) over-explain concepts Claude can infer, so it is tightenable without losing actionability.	3 / 5
Actionability	Provides copy-paste-ready gbrain commands with specific flags (e.g., `gbrain recall --since-last-run --supersessions --pending --rollup --json`, `gbrain waiting --json`) plus a concrete output-format template, covering the common briefing cases.	5 / 5
Workflow Clarity	Clear sequence — Pre-Briefing Context Pull (0a–0e) before Phases (1–6) — with a Contract section acting as an invariant checklist and a real feedback loop in 0e (waiting refuses on stale sources → sync → retry); minor validation gaps as there is no explicit final validation pass against the contract before delivery.	4 / 5
Progressive Disclosure	Well-organized single-file body with clearly signaled one-level-deep references (`skills/_brain-filing-rules.md`, `skills/google-loops/SKILL.md`); no bundle files exist, and some inline content (parallel context-loading sections) could be consolidated, leaving minor organization gaps.	4 / 5
	Total	16 / 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 clearly states what the skill does and covers several concrete facets, but it lacks an explicit "Use when..." trigger clause, which caps completeness and limits activation guidance to the separate triggers field. Trigger-term coverage is good but not exhaustive.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger phrases (e.g., "Use when the user asks for a daily/morning briefing or a brain pulse") so the description self-activates without relying on the triggers field.

Fold one or two natural synonyms ("morning briefing", "what's happening today") into the description to broaden trigger-term coverage.

Consider mentioning people/stale-alert coverage to round out the specificity toward comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete facets — "meeting context, active deals, and citation tracking" — giving clear scope, though it omits other body-covered areas (people, stale alerts, anomalies), so it is just short of comprehensive.	4 / 5
Completeness	The "what" is clear ("Compile daily briefing with meeting context, active deals, and citation tracking") but there is no "Use when..." clause or equivalent trigger guidance in the description, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Contains the natural user phrase "daily briefing" alongside topic keywords (meeting context, active deals, citation tracking); good coverage but missing common synonyms like "morning briefing" that live only in the triggers field.	4 / 5
Distinctiveness Conflict Risk	The daily-briefing niche is distinct and specific, with minor overlap risk against closely related meeting-prep or general briefing skills; not a fully isolated niche because adjacent skills could share triggers.	4 / 5
	Total	15 / 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/briefing/SKILL.md
Commit: 43597b1

Reviewed: 1 day 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.