briefing

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

Quality

61%

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

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is genuinely actionable with concrete gbrain commands and a clear output template, and its phased workflow is well-sequenced. Its main weaknesses are duplicated content across sections, implicit rather than explicit verification checkpoints, and a dangling reference to a filing-rules file that does not exist.

Suggestions

Consolidate the duplicated meeting-loading guidance (Phase 1 vs "Before a meeting") and citation rules (Contract vs "Citation in Briefings") into single authoritative sections to recover tokens.

Add an explicit verification step before delivery, e.g. a final "Verify every fact carries a [Source: ...] citation and every meeting gap is flagged" checkpoint.

Either create the referenced `skills/_brain-filing-rules.md` (or a local reference file) and link it once-level-deep, or inline the essential filing rules and drop the dangling reference.

Dimension	Reasoning	Score
Conciseness	The body is largely actionable but duplicates content: meeting loading appears in both Phase 1 and "Before a meeting", citations in both the Contract and "Citation in Briefings", and the _brain-filing-rules reference appears twice — these could be tightened.	2 / 3
Actionability	It provides multiple fully executable commands with specific flags (e.g. `gbrain recall --since-last-run --supersessions --pending --rollup --json`, `gbrain search --type person --sort updated --limit 10`) plus a concrete output template, which is copy-paste ready.	3 / 3
Workflow Clarity	The seven phases (0-6) are clearly sequenced, but verification checkpoints are implicit (gap-flagging, staleness surfacing) rather than explicit gates or validate-then-fix loops in the main flow.	2 / 3
Progressive Disclosure	Sections are well-organized, but at ~135 lines the body keeps content inline that could be split out, and it references a non-existent `skills/_brain-filing-rules.md` with no bundle files actually present to back the reference.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 and distinctive about its purpose and niche, but omits an explicit when-to-use clause and only carries a single natural trigger term. Adding a "Use when..." sentence with common phrasings would lift both completeness and trigger-term quality.

Suggestions

Append an explicit when-to-use clause, e.g. "Use when the user asks for a daily briefing, morning briefing, or what's happening today."

Include common natural variations ("morning briefing", "what's happening today") directly in the description rather than relying on the separate triggers field.

Lead with stronger action verbs for each component (e.g. "Surface meeting context, track active deals, and cite sources") to raise specificity.

Dimension	Reasoning	Score
Specificity	"Compile daily briefing with meeting context, active deals, and citation tracking" names the domain and three content areas, but offers only a single action verb ("Compile") rather than a comprehensive set of concrete actions.	2 / 3
Completeness	It states what the skill does ("Compile daily briefing...") but includes no explicit "Use when..." / when-to-trigger clause, capping completeness at 2 per the judging guideline.	2 / 3
Trigger Term Quality	The description includes one natural term ("daily briefing") a user might say, but lacks common variations (e.g. "morning briefing", "what's happening today") inside the description itself.	2 / 3
Distinctiveness Conflict Risk	"Compile daily briefing with meeting context, active deals, and citation tracking" carves a clear niche with distinct, natural triggers unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 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: 3fafb69

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