weekly-agenda

Generate a day-by-day overview of the week combining calendar events, email deadlines, and vault tasks into a single structured agenda. Triggers: EN: "weekly agenda", "what's this week", "week overview", "plan my week". IT: "agenda settimanale", "cosa c'è questa settimana", "panoramica della settimana". FR: "agenda de la semaine", "programme de la semaine". ES: "agenda semanal", "qué hay esta semana". DE: "Wochenagenda", "Wochenübersicht". PT: "agenda semanal", "o que tem esta semana".

Quality

82%

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

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.

A well-structured, actionable instruction skill with concrete CLI/MCP commands, a clear sequenced procedure, and explicit error handling. Minor gaps are an underspecified email-search syntax, slight redundancy, and an inline template/protocol that could move to reference files.

Suggestions

Specify the email-scan command syntax (e.g. the exact `gws gmail search` query or Hey box flags for "last 7 days with deadlines") so the email step is as executable as the calendar step.

Add an explicit validation checkpoint before saving — e.g. "Confirm every weekday section has Calendar and Tasks subsections; re-scan any empty source before writing" — to strengthen the workflow's feedback loop.

Move the full Weekly Agenda template and the Inter-Agent Coordination protocol into reference files (e.g. `references/template.md`, `references/agent-orchestration.md`) and link to them from the body to reduce inline length.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no "what is a calendar" filler), but repeats the description line and carries some emphatic redundancy ("This is not optional", "Max 30 lines" stated twice) that could be trimmed.	4 / 5
Actionability	Provides concrete commands (`gws calendar events list`, `hey box imbox --json`, `hey box laterbox --json`) and named MCP fallback tools (`gcal_list_events`, `gmail_search_messages`), but the email-scan step leaves the exact search query/flag syntax unspecified, a minor gap.	4 / 5
Workflow Clarity	A clear five-step procedure with an end-of-run post-it checkpoint and an error-handling section; the operation is read-mostly with a single note write, so the destructive/batch validation cap does not apply, though an explicit pre-save verification of the compiled agenda is missing.	4 / 5
Progressive Disclosure	No bundle files exist under references/scripts/assets, but the body is well-sectioned with clear headers and signals its few external references explicitly (`.claude/references/agent-orchestration.md`, `agents-registry.md`); the long inline template and inter-agent protocol could be split out, a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

90%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, third-person description with explicit "what" and "when" guidance and rich multilingual trigger coverage. The only gap is that it states one composite action rather than listing the discrete operations the skill performs.

Suggestions

Enumerate the concrete actions in the description — e.g. "compile a day-by-day agenda, flag overloaded and free days, and suggest follow-up agents" — to lift specificity beyond a single composite verb.

Dimension	Reasoning	Score
Specificity	Names the domain and one composite action ("Generate a day-by-day overview of the week combining calendar events, email deadlines, and vault tasks into a single structured agenda") but does not enumerate the several discrete actions the skill actually performs (compile, identify gaps, flag conflicts), so it stops at 1-2 concrete actions rather than comprehensive coverage.	3 / 5
Completeness	Explicitly answers both "what" (generate a structured day-by-day agenda combining three sources) and "when" via a labeled "Triggers:" clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases across six languages with synonyms ("weekly agenda", "what's this week", "week overview", "plan my week" + IT/FR/ES/DE/PT variants) that users would naturally say.	5 / 5
Distinctiveness Conflict Risk	A clear niche (weekly agenda fusing calendar + email + vault) with distinctive multilingual 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: gnekt/My-Brain-Is-Full-Crew
Path: tests/regression/snapshot/.claude/skills/weekly-agenda/SKILL.md
Commit: 238ae8c

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.