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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

A clear, well-structured instruction-only guide for a GUI SaaS workflow with concrete examples, dense reference tables, and useful error-recovery guidance. It lands solidly above midpoint across all dimensions but lacks explicit validation checkpoints that would push workflow clarity higher.

Suggestions

Add an explicit validation step after template/recipe creation (e.g., 'Verify the template appears in the picker and applies the expected sections to a test meeting') to lift workflow clarity toward 5.

Tighten Step 2's custom-template creation into discrete sub-steps matching the specificity of the recipe and pre-meeting examples, so every workflow step is equally actionable.

Trim the few explanatory sentences that restate what the AI does with templates, since Claude can infer that from the section structure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and table-driven with little generic-concept padding; a few sentences ('Templates tell the AI how to structure the enhanced output — a sales call produces different sections than a standup') could be trimmed.	4 / 5
Actionability	Provides concrete GUI paths ('Open Granola Settings > Templates', 'Click Create New Template'), copy-paste recipe prompts, and a full template markdown example; the custom-template creation steps at Step 2 remain somewhat high-level.	4 / 5
Workflow Clarity	Steps 1-5 are clearly sequenced and the Error Handling table provides recovery guidance, but there are no explicit validation checkpoints (e.g., confirm a template applied correctly) within the numbered flow.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Prerequisites, Steps 1-5, Output, Error Handling, Best Practices, Resources, Next Steps) with no nested references; as a self-contained single-file guide over 50 lines it is appropriately structured but not split.	4 / 5
	Total	16 / 20 Passed

Description

87%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-formed description that clearly states what the skill does and when to invoke it, with explicit trigger phrases and a distinct Granola-scoped niche. Minor specificity and keyword-synonym gaps keep it just below perfect.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'configuring note templates', 'creating custom recipes', 'preparing agenda notes' — with only minor coverage gaps (workspace defaults and error handling from the body are absent).	4 / 5
Completeness	Explicitly answers both 'what' ('Meeting preparation and template setup in Granola — templates, recipes, and pre-meeting workflows') and 'when' ('Use when configuring note templates...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage including natural meeting-type terms ('1:1s, standups, discovery calls, sprint planning') and an explicit Trigger line, but a few natural synonyms a user might say are missing.	4 / 5
Distinctiveness Conflict Risk	Granola-specific scope with 'granola'-prefixed triggers carves a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	18 / 20 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
Path: plugins/saas-packs/granola-pack/skills/granola-core-workflow-a/SKILL.md
Commit: 0540a62

Reviewed: 1 day 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.