CtrlK
BlogDocsLog inGet started
Tessl Logo

minutes-weekly

Weekly meeting synthesis — themes, decision arcs, stale commitments, and what deserves your attention next week. Use when the user says "weekly review", "what happened this week", "weekly summary", "recap my week", "any outstanding items", "week in review", or at the end of a work week.

73

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An excellent instruction-only skill body: fully executable commands, explicit validation checkpoints at every phase, and rich concrete output templates. The main improvement space is trimming meta-explanation and moving the long example-output blocks out of the main flow.

Suggestions

Move the full example presentation blocks (theme summary, decision-arc table, Attention Monday) into a bundled reference file and keep only one short inline exemplar per output format, reducing body length by roughly a third.

Cut meta-commentary such as 'This is a synthesis skill, not a command wrapper' and rely on the phase structure to convey the workflow's nature.

Clarify the provenance of the '_runtime/hooks/lib/minutes-learn-cli.mjs' script (bundle path vs. external dependency) so the referenced path is verifiable.

DimensionReasoningScore

Conciseness

Largely efficient — lean command blocks with brief purpose notes and no teaching of known concepts — but meta-explanation like "This is a synthesis skill, not a command wrapper" and three long inline example-output blocks could be trimmed.

4 / 5

Actionability

Fully executable guidance throughout: exact commands ("minutes list --limit 50", "minutes get \"<exact path>\" --json", "minutes search \"<topic>\" --since <30-days-ago> --limit 20"), concrete classification schemes (STABLE/VOLATILE/CONFLICTING/NEW), and copy-paste output templates covering common cases including zero-recording and light weeks.

5 / 5

Workflow Clarity

Seven clearly sequenced phases with explicit validation checkpoints ("require exit status 0" after each command), defined error-recovery paths ("report the source unavailable; never grep meeting files as a fallback"), zero-recording handling, and an explicit priority ordering rule for the final brief.

5 / 5

Progressive Disclosure

Well-organized single file with clear phase headers and easy navigation, but the long inline example-presentation blocks (~40% of the body) could live in a reference file, and the referenced runtime paths ("_runtime/hooks/lib/minutes-learn-cli.mjs") are not part of any bundled files.

4 / 5

Total

18

/

20

Passed

Description

91%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 description: concrete deliverables, comprehensive and natural trigger phrases, and an explicit when-to-use clause. Its only weaknesses are nominal phrasing instead of action verbs and slight overlap risk with sibling minutes skills.

DimensionReasoningScore

Specificity

Names the domain and several concrete deliverables — "themes, decision arcs, stale commitments, and what deserves your attention next week" — but delivers them as nominal output labels rather than multiple explicit action verbs, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both questions: a clear what ("Weekly meeting synthesis — themes, decision arcs, stale commitments...") and an explicit "Use when the user says..." clause with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage: "weekly review", "what happened this week", "weekly summary", "recap my week", "any outstanding items", "week in review", plus the situational "at the end of a work week" — no common variant is missing.

5 / 5

Distinctiveness Conflict Risk

A clear weekly-synthesis niche that is mostly distinct, but generic phrases like "any outstanding items" carry minor overlap risk with closely related minutes skills (e.g., prep/daily variants).

4 / 5

Total

18

/

20

Passed

Validation

100%

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
silverstein/minutes
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.