meta-meeting-to-workflow

Use this meta-skill instead of answering directly when the user has meeting notes, transcripts, recordings, or rough discussion notes and wants them converted into decisions, owners, follow-ups, tasks, issues, or shareable minutes through multi-skill orchestration.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/opensquilla/skills/exp/meta-meeting-to-workflow/SKILL.md

Quality

Content

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

The body is extremely concise and cleanly organized but transfers almost all substantive guidance into the YAML frontmatter, leaving the markdown body as a bare summary with no actionable workflow or validation steps.

Suggestions

Move or mirror the orchestration workflow (intake -> clarify -> digest -> decision_map -> artifact_plan -> workflow_pack) into the body so Claude has an explicit, sequenced process to follow.

Add validation/checklist steps in the body for the batch external-creation steps (drafting issues, cards, follow-ups) to satisfy the destructive/batch feedback-loop requirement.

Include at least one concrete, copy-paste-ready example of an output artifact (e.g., a sample action-table row) so the body is actionable rather than purely descriptive.

Dimension	Reasoning	Score
Conciseness	The body is a single lean sentence with no padding and no over-explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	The body only describes outputs ("minutes, decisions, action ownership, and execution-ready task drafts") without any executable guidance or steps; the actual workflow lives in the frontmatter, out of scope for this judge.	2 / 5
Workflow Clarity	The body contains no sequenced steps or validation checkpoints; for a skill that drafts tasks/issues/cards (batch/external operations), the absence of any workflow in the body is a serious gap.	1 / 5
Progressive Disclosure	The body is well under 50 lines, well-organized, and needs no external references; the simple-skill exception applies and no bundle files exist to require navigation.	5 / 5
	Total	13 / 20 Passed

Description

92%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, well-structured description that clearly states capability and trigger conditions with concrete natural-language terms. Minor gap: a few common trigger synonyms ("minutes", "action items") are absent.

Dimension	Reasoning	Score
Specificity	Names the meeting-material domain and lists multiple concrete conversion actions ("decisions, owners, follow-ups, tasks, issues, or shareable minutes"), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both what (converts meeting material into decisions/owners/follow-ups/tasks/issues/minutes) and when ("Use this meta-skill instead of answering directly when the user has meeting notes...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users say ("meeting notes, transcripts, recordings, or rough discussion notes") but misses common synonyms like "minutes" or "action items" as triggers, landing just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (meeting-to-workflow via multi-skill orchestration) with specific triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/exp/meta-meeting-to-workflow/SKILL.md
Commit: 94ac35e

Reviewed: 3 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.