granola-deploy-integration

Deploy Granola native integrations — Slack, Notion, HubSpot, Attio, Affinity, and Zapier. Step-by-step setup for each platform with configuration, testing, and automation chains. Trigger: "granola slack", "granola notion", "granola hubspot", "granola attio", "connect granola", "granola integration".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

A genuinely actionable deployment guide with concrete UI paths, config tables, and Zapier templates, undermined by an unlinked reference bundle and validation that is separated from the steps rather than woven in. Token efficiency suffers from overlap with the existing reference file.

Suggestions

Link references/integration-guides.md from the body (e.g., a 'Detailed guides' pointer) and move the duplicated multi-integration workflow, Zapier recipes, message formats, and deployment checklist into it to reduce inline redundancy.

Add an inline 'Test with a sample note and confirm the post/record appears' checkpoint after each integration's setup steps, rather than only listing verification in the Output section.

Trim the Overview paragraph and consolidate the duplicated multi-integration diagram (it appears both in the body and the reference) to one canonical location.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concept explanations Claude already knows, but the multi-integration workflow and Zapier recipe tables overlap content already present in references/integration-guides.md, so the body could be tightened by offloading that detail.	2 / 3
Actionability	Concrete, executable guidance throughout: exact UI paths ('Settings (avatar bottom-left) > Integrations > Slack > Connect'), per-folder config tables, and copy-paste Zapier YAML blocks for Notion and HubSpot workarounds.	3 / 3
Workflow Clarity	Setup steps are clearly numbered and sequenced, but per-integration validation/test checkpoints are not inline; verification lives only in the separate 'Output' section rather than as explicit validate-then-proceed steps.	2 / 3
Progressive Disclosure	Sections are well-organized, but the bundled references/integration-guides.md is never linked or signaled from the body, and content that could live there (message formats, schemas, deployment checklist) is instead duplicated inline.	2 / 3
	Total	9 / 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 description: third-person voice, concrete per-platform actions, and explicit natural-language triggers that clearly answer both what the skill does and when to invoke it. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Deploy Granola native integrations', 'Step-by-step setup for each platform with configuration, testing, and automation chains') and names every target platform, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what it does (deploy/setup/configure/test integrations per platform) and when to use it via an explicit 'Trigger:' clause, satisfying both 'what' and 'when'.	3 / 3
Trigger Term Quality	Provides natural, sayable triggers ('granola slack', 'granola notion', 'granola hubspot', 'granola attio', 'connect granola', 'granola integration') with good coverage of how a user would phrase the request.	3 / 3
Distinctiveness Conflict Risk	A clear niche (Granola integrations) with platform-specific distinct triggers makes collision with other skills unlikely.	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: 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.