CtrlK
BlogDocsLog inGet started
Tessl Logo

meeting-synthesis

Workflow for turning meeting transcripts or notes into decisions, action items, unresolved questions, risks, and follow-up artifacts. Use for prompts like "summarize this meeting", "extract action items", "what did we decide", or "draft the follow-up". Best when you have notes or a transcript, attendee context, and the reason the meeting happened. Optional Open Brain search and capture can pull surrounding context and store the final synthesis or decisions.

76

Quality

95%

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

100%

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

A clean, focused instruction skill with an unambiguous process, explicit judgment guardrails, and a concrete output spec. It is appropriately lean and self-contained.

DimensionReasoningScore

Conciseness

Lean and well-sectioned with no padding explaining concepts Claude already knows; every section (Process, Evidence and Judgment Rules, Output) earns its place.

3 / 3

Actionability

Concrete six-step process with sub-bullets, explicit deliverable list, and specific rules like 'Separate decided, assigned, and discussed'; absence of code is appropriate for this instruction-only skill.

3 / 3

Workflow Clarity

Clear numbered sequence with the 'Evidence and Judgment Rules' section functioning as validation checkpoints (e.g., 'Do not inflate tentative discussion into final decisions'); the task is non-destructive so the feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

Single self-contained file with well-organized sections and no nested or external references; no bundle files exist, so the well-organized overview qualifies for full marks.

3 / 3

Total

12

/

12

Passed

Description

90%

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, well-targeted description that clearly states capabilities and provides explicit natural-language triggers. Its only weakness is a second-person clause that costs it a specificity point under the rubric.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('decisions, action items, unresolved questions, risks, and follow-up artifacts'), which would be a 3, but the second-person phrasing 'Best when you have notes' triggers the rubric's -1 specificity penalty.

2 / 3

Completeness

Explicitly answers both what it does and when to use it via an explicit 'Use for prompts like…' trigger clause, matching the 'clearly answers both what AND when' anchor.

3 / 3

Trigger Term Quality

Quotes natural phrases a user would actually say ('summarize this meeting', 'extract action items', 'what did we decide', 'draft the follow-up'), giving strong coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Carves a clear meeting-specific niche with distinct triggers ('what did we decide', 'draft the follow-up') unlikely to fire for non-meeting synthesis skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
NateBJones-Projects/OB1
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.