CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

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

SKILL.md
Quality
Evals
Security

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 strong, highly actionable skill document: exact commands, explicit contracts, a defined output format, and genuine failure-handling guidance. Its main weaknesses are moderate redundancy and version-stamped detail that cost token efficiency, plus a slightly tangential email-reply subsection.

Suggestions

Merge 'Citation in Briefings' into the Contract section and drop the 'Tools Used' section (it duplicates the frontmatter tools list) to tighten conciseness.

Move version-specific detail like 'Hot memory pulse (v0.32)' into a changelog or deprecation-style section so time-sensitive numbers don't burden the working instructions.

Extract 'GBrain-Native Context Loading' into a reference file and remove or relocate the 'Before an email reply' subsection, which is outside the briefing workflow.

DimensionReasoningScore

Conciseness

The body is mostly dense and actionable, but includes redundancy (the citation rule appears in both the Contract and Citation in Briefings sections, and Tools Used repeats the frontmatter tool list) and time-sensitive version detail ('Hot memory pulse (v0.32)') that the guidelines penalize outside a deprecation section.

3 / 5

Actionability

Guidance is fully executable: copy-paste-ready commands with flags ('gbrain salience --days 7', 'gbrain recall --since-last-run --supersessions --pending --rollup --json', 'gbrain whois <email> --json'), a concrete output template with placeholders, and worked citation examples cover the common cases.

5 / 5

Workflow Clarity

The pre-briefing pulls (0a-0e), Phases 1-6, and output template give a clear sequence, and the 'When it fails' section supplies error-recovery loops (retry after sync, ship remaining sections and name the missing one). It falls short of 5 due to minor gaps: the 'Before an email reply' subsection is tangential to the briefing workflow, and 'get_health' is referenced in Tools Used but absent from the frontmatter tools list.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers and clearly signaled one-level cross-references (skills/_brain-filing-rules.md, ../conventions/agent-operator-protocol.md); however, the ~200-line body inlines multi-part material such as 'GBrain-Native Context Loading' that could live in a reference file, and no bundle files are provided to verify the referenced paths, leaving 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 gives a clear, third-person statement of what the skill produces, but it is a what-only description: it lists no usage triggers and only a single action. Folding a 'Use when' clause with the natural trigger phrases (which already exist in separate frontmatter fields) into the description would lift both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when the user asks for a daily or morning briefing or wants to know what's happening today.', to move completeness and trigger_term_quality up.

Vary the natural keywords inside the description itself (daily briefing, morning briefing, catch-up, what's happening today) instead of relying on the separate triggers field.

Describe the concrete actions performed (search participants, pull deal timelines, compile citations) rather than only naming the output content areas.

DimensionReasoningScore

Specificity

The description names the domain ('daily briefing') and content areas ('meeting context, active deals, and citation tracking') but only one action verb ('Compile'), matching the anchor for domain plus 1-2 concrete actions rather than the several distinct actions of level 4.

3 / 5

Completeness

It clearly answers 'what' (compile a daily briefing with meeting context, active deals, citation tracking) but contains no 'Use when...' clause or equivalent trigger guidance in the description itself, which caps completeness at 3.

3 / 5

Trigger Term Quality

'daily briefing' is a natural phrase a user would say, but the description field omits common variations and synonyms such as 'morning briefing' or 'what's happening today' (those appear only in separate frontmatter fields), fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The briefing-compilation niche with citation tracking is mostly distinct, but 'meeting context' and 'active deals' could overlap with dedicated calendar/meeting or CRM-style skills, giving minor overlap risk rather than the minimal risk of level 5.

4 / 5

Total

13

/

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: 3 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

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