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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

The body is an excellent, lean, actionable checklist with a clear phased workflow and real validation/feedback checkpoints. Its one weakness is progressive disclosure: a reference bundle file exists but is neither linked from the body nor cleanly separated from it, leaving duplicate content in two places.

Suggestions

Reference references/implementation.md from the body (e.g., a 'Detailed implementation guide' pointer) so the bundle file is discoverable, and remove the overlapping checklist content that is duplicated between the body and implementation.md.

Split the lengthy per-phase detail (security, integration, pilot metrics) into the reference file and keep SKILL.md as a concise overview pointing to it, so each file earns its place and content is not duplicated.

Verify all in-body skill cross-links (granola-install-auth, granola-hello-world, granola-upgrade-migration) resolve to real sibling skills, since broken cross-skill links undermine the navigation that progressive disclosure depends on.

Dimension	Reasoning	Score
Conciseness	The body is a lean, dense checklist with no concept-explanation padding — concrete prices, settings paths, and retention values appear with no filler, matching the level-3 anchor; it is not level 2 because there is no unnecessary explanation to tighten.	3 / 3
Actionability	It provides copy-paste-ready, specific guidance throughout (e.g. "$14/user/mo", "Settings > Calendar > Connect", "notes: 1-2yr, transcripts: 90d", IdP options, metric targets in tables), matching the level-3 anchor; as an instruction-only skill, the absence of code is not penalized because the guidance is concrete and actionable.	3 / 3
Workflow Clarity	A clear seven-phase sequence (Plan → Security → Integration → Workspace → Pilot → Go-Live → Post-Launch) is paired with explicit verification columns in the integration table, a pilot-to-go-live gate on metrics meeting targets, monitoring checklists, and an Error Handling feedback table (issue → cause → fix), matching the level-3 anchor with validation checkpoints present rather than just listed.	3 / 3
Progressive Disclosure	The body is well-organized with one-level-deep links to other skills and external docs, but the provided bundle file references/implementation.md is never referenced from the body and largely duplicates inline content, so content that should be split out is instead duplicated — matching the level-2 anchor rather than level 3's clean signaled split.	2 / 3
	Total	11 / 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.

The description is well-constructed: it states the purpose, includes an explicit Use-when clause, and supplies a strong set of natural trigger terms scoped to a specific product. Its only weakness is that the described actions are process-level/abstract rather than concrete technical operations.

Dimension	Reasoning	Score
Specificity	Names the domain and several actions ("Production readiness checklist", "rolling out", "planning enterprise deployment", "verifying all configuration is production-ready"), but the actions are abstract/process-level rather than a list of concrete technical actions, matching the level-2 anchor rather than level 3.	2 / 3
Completeness	It answers both what (production readiness checklist for team/enterprise deployment) and when (an explicit "Use when rolling out Granola... planning enterprise deployment... verifying all configuration is production-ready" clause plus trigger terms), matching the level-3 anchor; it is not level 2 because the when is explicit, not merely implied.	3 / 3
Trigger Term Quality	The explicit Trigger block lists "granola production", "granola rollout", "granola deployment", "granola checklist", and "granola go-live" — natural phrases a user would say with good coverage of variations, matching the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	Granola is a specific named product and all triggers are granola-scoped, giving it a clear niche unlikely to conflict with other skills, matching the level-3 anchor rather than the overlapping level-2 case.	3 / 3
	Total	11 / 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: 2 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.