granola-core-workflow-a

Meeting preparation and template setup in Granola — templates, recipes, and pre-meeting workflows. Use when configuring note templates for 1:1s, standups, discovery calls, or sprint planning, creating custom recipes, or preparing agenda notes before important meetings. Trigger: "granola template", "granola meeting prep", "granola recipe", "granola agenda".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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 GUI workflow for Granola meeting prep with clear sequencing and error-recovery guidance, though it carries some explanatory padding and does not split its longer reference material into bundle files.

Suggestions

Trim explanatory asides like 'Templates tell the AI how to structure the enhanced output' and 'Granola ships with 29 built-in templates' to lift conciseness toward a lean 3.

Move the large template- and recipe-reference tables into a references/ file (e.g. TEMPLATES.md, RECIPES.md) and link to them from SKILL.md to enable one-level-deep progressive disclosure.

Consider pruning or collapsing the full built-in template and per-folder default tables to only the entries the workflow actually relies on, reducing token cost.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tables and steps, but padded with explanatory prose such as 'Templates tell the AI how to structure the enhanced output — a sales call produces different sections than a standup' and 'Granola ships with 29 built-in templates', so it is not the lean 'every token earns its place' level.	2 / 3
Actionability	As an instruction-only skill it gives concrete, copy-paste-ready guidance — exact click paths ('Granola Settings > Templates', 'Click Create New Template'), a recipe-prompt table, and full template markdown blocks — so absence of code is not penalized.	3 / 3
Workflow Clarity	Five steps are clearly sequenced (Step 1–5) with an Error Handling table acting as a feedback loop for recovery and a Best Practices checklist; no destructive/batch operations exist to trigger a validation cap, so it is above the 'checkpoints missing' level.	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the ~140-line body keeps reference-style template and recipe tables inline, so it has structure but lacks the well-signaled one-level-deep references needed for a 3.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 that names concrete capabilities, supplies natural trigger terms, and explicitly states both what it does and when to use it, with a distinct Granola-scoped niche that limits conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'configuring note templates for 1:1s, standups, discovery calls, or sprint planning, creating custom recipes, or preparing agenda notes' — matching the 'lists multiple specific concrete actions' anchor rather than the score-2 'names domain and some actions' level.	3 / 3
Completeness	Explicitly answers both 'what' (templates, recipes, pre-meeting workflows) and 'when' via an explicit 'Use when...' clause, so it is not capped at 2 for a missing trigger clause.	3 / 3
Trigger Term Quality	Provides natural trigger terms a user would say — 'granola template', 'granola meeting prep', 'granola recipe', 'granola agenda' — plus domain phrases like '1:1s, standups, discovery calls', giving good coverage rather than just 'some relevant keywords'.	3 / 3
Distinctiveness Conflict Risk	A clear Granola-specific niche with 'granola'-prefixed triggers makes it unlikely to fire for the wrong skill, rather than being 'somewhat specific but could still overlap'.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 1628598

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