granola-prod-checklist

Production readiness checklist for Granola team and enterprise deployment. Use when rolling out Granola to a team, planning enterprise deployment, or verifying all configuration is production-ready. Trigger: "granola production", "granola rollout", "granola deployment", "granola checklist", "granola go-live".

Quality

70%

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 ./plugins/saas-packs/granola-pack/skills/granola-prod-checklist/SKILL.md

Quality

Content

53%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 a well-sequenced, actionable rollout checklist, but it is held back by an unlinked reference file and missing validation checkpoints for a batch deployment operation. Tying the body to the existing implementation.md and adding explicit go/no-go gates would materially raise the score.

Suggestions

Link references/implementation.md from the body (e.g., a 'See implementation.md for full sub-checklists' line) so the bundle is actually surfaced and signaled.

Add explicit validation checkpoints between phases — e.g., 'Pilot meets targets → proceed to go-live; if not, extend pilot and recheck' — to give the batch rollout a validate-fix-retry loop.

Trim inlined security/integration/pilot detail that duplicates implementation.md and point to it instead, improving conciseness and progressive disclosure together.

Dimension	Reasoning	Score
Conciseness	The checklist format is mostly efficient and assumes Claude's competence, but the body re-lists security, integration, pilot, and go-live content that also appears in references/implementation.md, so it could be tightened by offloading detail.	3 / 5
Actionability	Concrete checkboxes with specific settings paths ('Settings > Calendar > Connect'), exact plan prices ('Business ($14/user/mo)'), and a detailed issue-cause-fix table give mostly executable guidance with only minor gaps.	4 / 5
Workflow Clarity	The seven phases are clearly sequenced and the pilot phase provides a partial gate before go-live, but an org-wide rollout is a batch operation that lacks explicit validate-before-proceed checkpoints and retry loops, capping the score at 3.	3 / 5
Progressive Disclosure	A references/implementation.md bundle exists but is never linked or signaled from the body, and content that overlaps with that reference (security, integrations, pilot, go-live) is inlined rather than split out, leaving references effectively buried.	2 / 5
	Total	12 / 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.

The description is strong: it concisely states the skill's purpose, gives explicit 'Use when' guidance, and lists natural trigger phrases anchored to a distinct Granola-specific niche. Minor improvement could come from broadening trigger term coverage slightly.

Dimension	Reasoning	Score
Specificity	Names the Granola deployment domain and several concrete actions (rolling out to a team, planning enterprise deployment, verifying production-ready configuration), with only minor gaps in coverage rather than a fully comprehensive action list.	4 / 5
Completeness	It clearly states what the skill does ('Production readiness checklist for Granola team and enterprise deployment') and explicitly states when to use it via both a 'Use when...' clause and concrete trigger phrases, fully satisfying both criteria.	5 / 5
Trigger Term Quality	An explicit Trigger block lists five natural phrases ('granola production', 'granola rollout', 'granola deployment', 'granola checklist', 'granola go-live') that users would say, though a few natural variations like 'granola setup' are absent.	4 / 5
Distinctiveness Conflict Risk	The Granola-specific niche and brand-qualified trigger phrases make it clearly distinguishable from other deployment skills with minimal conflict risk.	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-prod-checklist/SKILL.md
Commit: 8585d6d

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