CtrlK
BlogDocsLog inGet started
Tessl Logo

board-minutes

Drafts board or committee meeting minutes in your house format. Auto-detects upcoming board and committee meetings from your calendar, asks for the agenda and any slides or pre-read materials, and produces a complete draft in the format learned from your seed minutes. Also handles written consents in lieu of meetings. Trigger: "board minutes", "draft minutes", "upcoming board meeting", "committee minutes", "written consent", or calendar detection of an upcoming board or committee event.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

A highly actionable, well-sequenced legal-drafting skill with strong validation gates and copy-paste templates, scoring well on actionability and workflow clarity. Its weaknesses are token efficiency (a repeatedly inlined long path and a motivational paragraph) and a monolithic single-file structure that underuses progressive disclosure.

Suggestions

Define the long plugin config path once near the top (e.g., as a short alias or a single 'context path' note) and reuse it, instead of repeating '~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md' verbatim throughout.

Trim the 'Purpose' paragraph ('Board minutes are a legal record...') to a single line or remove it — it motivates the task with context Claude already has; lead with the actionable process instead.

Move the full 'Standard structure' minutes template and the review checklist into a reference file (e.g., references/template.md) and link to it from SKILL.md, so the main file is a leaner overview and detailed material is progressively disclosed one level deep.

DimensionReasoningScore

Conciseness

Mostly efficient and directive (steps, templates, drafting notes, checklists) but the full plugin path '~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md' is repeated verbatim roughly eight times, and the 'Purpose' paragraph ('Board minutes are a legal record...') restates context Claude already knows. Not a 3 because not every token earns its place; not a 1 because the bulk is lean, actionable guidance rather than padded concept explanation.

2 / 3

Actionability

Provides copy-paste-ready templates (header block, agenda-item structure, resolution language), exact quoted user prompts, and a checkbox review checklist — concrete and executable instruction-only guidance. Not a 2 because the guidance is complete and specific rather than vague or pseudocode.

3 / 3

Workflow Clarity

Clear Step 1→5 sequence with explicit validation checkpoints: quorum check ('If not: stop and flag before drafting'), a consequential-action adoption gate requiring an explicit yes, and a pre-circulation review checklist. Not a 2 because validation/feedback gates are explicit rather than missing or implicit.

3 / 3

Progressive Disclosure

Well-organized into clear sections (Matter context, Load context, Steps 1–5, Written consents, What this skill does not do) with no deeply nested references, but it is a monolithic ~230-line SKILL.md with the full minutes template and review checklist inline and no bundle files to progressively disclose detail. Not a 3 because content that could be split (template, checklist) is not separated into one-level-deep reference files; not a 1 because sectioning is clear and there is no nested-reference maze.

2 / 3

Total

10

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 Trigger clause answering both what and when, and well-chosen natural trigger terms for a distinctive legal niche. The only weakness is repeated second-person possessive phrasing, which the rubric penalizes under the third-person-voice rule.

Suggestions

Replace second-person possessives ('your house format', 'your calendar', 'your seed minutes') with third-person phrasing such as 'the user's house format' to satisfy the third-person-voice guideline and recover the specificity penalty.

Optionally tighten 'asks for the agenda and any slides or pre-read materials, and produces a complete draft in the format learned from your seed minutes' into a single leaner clause so every token earns its place.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Drafts board or committee meeting minutes', 'Auto-detects upcoming board and committee meetings from your calendar', 'asks for the agenda and any slides or pre-read materials', 'handles written consents in lieu of meetings'), which is a level-3 base, but the repeated second-person possessives ('your house format', 'your calendar', 'your seed minutes') trigger the rubric's -1 third-person-voice penalty. Not a 3 because of that voice penalty; not a 1 because the action verbs are concrete and domain-specific.

2 / 3

Completeness

Explicitly answers what ('Drafts... minutes', 'Auto-detects', 'handles written consents') and when (an explicit 'Trigger:' clause with multiple trigger phrases and calendar detection). Not a 2 because the when is explicit, not merely implied.

3 / 3

Trigger Term Quality

The Trigger clause lists natural phrases a user would actually say — 'board minutes', 'draft minutes', 'upcoming board meeting', 'committee minutes', 'written consent' — plus calendar detection, giving good coverage. Not a 2 because common variations are well represented rather than partially missing.

3 / 3

Distinctiveness Conflict Risk

A clear legal niche (board/committee minutes, written consents) with distinctive triggers unlikely to fire for unrelated skills. Not a 2 because the domain and triggers are specific enough to avoid overlap with general-purpose skills.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
anthropics/claude-for-legal
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.