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 action-oriented and well-structured with executable gbrain commands, a clear pre-pull-to-phases sequence, and explicit anti-patterns. It is held to 4 across dimensions by light redundancy and the absence of an explicit validation checkpoint and any progressive-disclosure file split.

Suggestions

Add a brief validation step before composing (e.g., 'confirm each context pull returned data; if a query is empty, flag the gap rather than silently omitting it') to strengthen the workflow feedback loop.

Consolidate the repeated citation/back-linking guidance (currently in Contract, Output Format, and a dedicated section) into one place, pointing the others to it, to tighten token efficiency.

Move the detailed filing/back-linking rules fully into skills/_brain-filing-rules.md and reference them once, leaving the SKILL.md body as a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and no padding explaining what gbrain is or basic concepts; the context-loading and citation/back-linking guidance is restated across multiple sections and could be consolidated, keeping it below 5.	4 / 5
Actionability	Provides concrete, executable `gbrain` commands with specific flags (salience, anomalies, recall --since-last-run --supersessions) and explicit query strings; a few phases are described rather than given as copy-paste commands, so not 5.	4 / 5
Workflow Clarity	Clear ordered sequence (Pre-Briefing pulls 0a-0d then Phases 1-6), but no explicit validation/verify checkpoint or error-recovery loop before composing; the skill is read-only so the destructive cap does not strictly apply, leaving it at 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist; the ~175-line body is well-organized with clear section headers and one-level-deep external references (skills/_brain-filing-rules.md), but it is a single monolithic doc with restated filing/back-linking rules rather than a split-file structure, so not 5.	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 is third-person, specific, and names three concrete actions, but it omits any explicit 'when to use' guidance, which caps completeness at 3. Trigger coverage is good thanks to the companion frontmatter triggers list.

Suggestions

Add a 'Use when...' clause (e.g., 'Use when the user asks for a daily/morning briefing or wants to know what's happening today') so the description answers both what and when.

Fold one or two natural trigger phrases from the triggers list (e.g., 'morning briefing', 'brain pulse') directly into the description for better trigger-term surface coverage.

Consider naming the brain-recall/salience/anomaly pulls that dominate the body, to make the description more comprehensive and distinctive.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete sub-actions ("meeting context, active deals, and citation tracking"), matching the 'several specific actions; minor gaps' anchor; not 5 because the body's brain-recall/anomaly/salience pulls are not surfaced in the description.	4 / 5
Completeness	Has a clear 'what' (compile a daily briefing with meeting context, active deals, citation tracking) but no 'when' / 'Use when...' clause at all, so per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	The description surfaces "daily briefing" and the frontmatter triggers add several natural user phrases ("morning briefing", "what's happening today", "brain pulse"); good keyword coverage, though not every natural synonym is in the description itself.	4 / 5
Distinctiveness Conflict Risk	"daily briefing with meeting context, active deals, and citation tracking" carves a fairly distinct niche; mostly distinct with minor overlap risk against a generic brain-query or meetings skill, so not 5.	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: 055ac6c

Reviewed: about 16 hours 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.