meeting-brief

Daily meeting preparation system that checks your calendar each morning, deeply researches external attendees (LinkedIn, company info, GitHub, past notes), and sends you personalized briefs via email (1 per person). Use when you want automated preparation for upcoming meetings with context about each person you're meeting.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sales/composites/meeting-brief/SKILL.md

Quality

Content

61%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.

A thorough, well-structured skill body with real executable scripts and clear setup guidance. It loses points for redundancy between overview and workflow sections and for lacking explicit validation checkpoints in a batch email-sending workflow.

Suggestions

Add an explicit validation checkpoint in the main workflow (e.g. 'Review generated brief, then confirm send') to lift workflow clarity above the batch-operation cap.

Merge or cross-reference the 'What It Does' and 'How It Works' sections to remove the duplicated step list.

Fix the 'send_brief.sh' reference in Manual Usage to point to the actual script that exists (e.g. send_slack.sh / the email path) to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete config and examples, but the 'What It Does' 6-step list largely duplicates the 'How It Works' 7-step workflow, and the full example brief + JSON output add length that could be trimmed.	3 / 5
Actionability	Provides concrete, mostly executable commands ('./scripts/run_daily.sh', 'node scripts/research_person.js "Jane Doe" "jane@example.com" "Example Corp"') backed by real scripts in the bundle, with a minor gap: Manual Usage references 'send_brief.sh' which is not present in scripts/.	4 / 5
Workflow Clarity	The 7-step sequence is clearly listed, but this is a batch, outward-facing operation (auto-sending emails to multiple people) with no explicit validation/checkpoint step in the main workflow before sending, so the batch-operation cap at 3 applies.	3 / 5
Progressive Disclosure	Well-organized into clear sections with one-level-deep references to real bundle scripts (run_daily.sh, check_calendar.sh, research_person.js, generate_brief.js, send_slack.sh); minor gaps in that some inlined reference material (full example brief, JSON schema) could live in separate files.	4 / 5
	Total	14 / 20 Passed

Description

87%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.

A strong, specific description with an explicit 'Use when' trigger and comprehensive capability list. Main weakness is second-person voice, which costs it a specificity point per the rubric voice rule.

Suggestions

Rewrite in third person to avoid the voice penalty: e.g. 'Checks the user's calendar each morning, researches external attendees, and sends personalized briefs via email.'

Add a few more natural trigger synonyms users might say ('meeting prep', 'who am I meeting today') to lift trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('checks your calendar each morning, deeply researches external attendees (LinkedIn, company info, GitHub, past notes), and sends you personalized briefs via email (1 per person)') with comprehensive coverage, but voice is second person ('your calendar', 'sends you') so specificity is reduced by 1 per the voice guideline.	4 / 5
Completeness	Clearly answers both what (checks calendar, researches attendees, sends briefs) and when via an explicit trigger clause ('Use when you want automated preparation for upcoming meetings with context about each person you're meeting').	5 / 5
Trigger Term Quality	Good coverage of natural terms ('meeting', 'calendar', 'briefs', 'external attendees', 'upcoming meetings', 'context about each person'), but a few natural variations a user might say (e.g. 'meeting prep', 'who am I meeting') are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (automated meeting preparation briefs) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: gooseworks-ai/goose-skills
Path: skills/sales/composites/meeting-brief/SKILL.md
Commit: 2523432

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.