Name: briefing
Rating: 56.00000000000001 (1 reviews)
Author: garrytan

Blog Docs Log inGet started

briefing

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

Quality

64%

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

The canonical home for this skill is briefing in garrytan/gbrain

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 a highly actionable, well-sequenced workflow with concrete commands, an exact output template, and genuine error-recovery guidance. Its main weakness is redundancy: rules and queries are repeated across the Contract, Phases, Context Loading, and Anti-Patterns sections, inflating token cost without adding information.

Suggestions

Consolidate the read-only rule and citation rule into the Contract only, leaving the Anti-Patterns section to reference them in one line instead of restating them.

Merge "GBrain-Native Context Loading" (the daily briefing queries and before-a-meeting steps) into the Phases section to eliminate the duplicated query lists.

Drop or relocate the "Before an email reply" subsection, which is tangential to a daily-briefing skill, into a separate reference file or skill.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with dense actionable commands, but noticeably redundant: the read-only rule appears in the Contract, the Anti-Patterns ("The briefing is read-only by default"), and the intro; the citation rule is stated three times; and the "GBrain-Native Context Loading" queries overlap the "Phases" section. This fits "mostly efficient but could be tightened," not level 4, which requires only minor trimmable instances.	3 / 5
Actionability	Commands are copy-paste ready and complete with flags (e.g. `gbrain recall --since-last-run --supersessions --pending --rollup --json`, `gbrain salience --days 7`, `gbrain waiting --json`), the output format is a concrete template, and failure handling names the exact fix ("run the sync it names, then retry"). This matches the anchor for fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	The sequence is clear (pre-briefing pulls 0a-0e, then phases 1-6, then the output format) with real checkpoints (gap-flagging for missing participant pages, stale-page flagging, retry-with-named-fix for stale google sources). It is not level 5 because there is no final validation step on the composed briefing before presenting it.	4 / 5
Progressive Disclosure	Good structure with clear sections (Contract, pulls, phases, output format, anti-patterns), and external detail is delegated to one-level-deep signaled references (`skills/_brain-filing-rules.md`, `skills/google-loops/SKILL.md`). It is not level 5 because no bundle reference files exist and overlapping sections (Phases vs. GBrain-Native Context Loading) leave minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

53%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 concrete and distinct, clearly stating what the skill produces, but it lacks any explicit "when to use" guidance and only carries one natural trigger phrase within the description field itself (variants live in the separate triggers frontmatter). It reads as a capable but incomplete description that would benefit from an explicit use-when clause.

Suggestions

Append a trigger clause to the description, e.g. "Use when the user asks for a daily or morning briefing, what's happening today, or a pre-briefing pull."

Fold 1-2 natural trigger synonyms (e.g. "morning briefing", "what's happening today") into the description text itself so trigger matching does not depend solely on the separate triggers field.

Slightly expand the action list (e.g. "surfaces high-salience pages, open loops, and stale-page alerts") to move specificity from 1-2 actions toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Compile daily briefing with meeting context, active deals, and citation tracking" names the domain and 2-3 concrete content components, but describes a single action ("compile") rather than several distinct actions, matching the anchor for domain plus 1-2 concrete actions. It is not level 4 because it does not list several specific actions with only minor gaps.	3 / 5
Completeness	It has a clear "what" (compile a daily briefing with meeting context, active deals, and citations) but no "Use when..." clause or equivalent trigger guidance in the description, which caps completeness at 3 per the judging guidelines. It is not level 2 because the "what" is concrete and specific.	3 / 5
Trigger Term Quality	The description contains one strong natural phrase ("daily briefing") but omits common variations users would say ("morning briefing", "what's happening today"), which appear only in the separate triggers frontmatter and not in the description itself. This fits the anchor for some relevant keywords but missing common variations, rather than level 4's good keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The combination of daily briefing compilation, brain-backed meeting context, active deals, and citation tracking carves a distinct niche with only minor overlap risk against generic scheduling or summarization skills. It is not level 5 because the phrase "meeting context" could weakly overlap with calendar-related skills.	4 / 5
	Total	13 / 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: plugin-variants/gbrain-daily/skills/briefing/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.