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".
62
75%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/granola-pack/skills/granola-deploy-integration/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly identifies the product (Granola), lists specific supported platforms, describes concrete actions (setup, configuration, testing, automation chains), and provides explicit trigger terms. The description is concise, uses third-person voice, and would be easily distinguishable from other skills in a large collection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: deploying integrations across six named platforms (Slack, Notion, HubSpot, Attio, Affinity, Zapier), with step-by-step setup, configuration, testing, and automation chains. | 3 / 3 |
Completeness | Clearly answers 'what' (deploy native integrations with step-by-step setup, configuration, testing, and automation chains) and 'when' (explicit trigger terms listed). The 'Trigger:' clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say like 'granola slack', 'granola notion', 'granola hubspot', 'connect granola', 'granola integration'. These cover the main platform names and common phrasing patterns users would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Granola' with specific integration platforms creates a very clear niche. The named platforms and 'granola' prefix make it unlikely to conflict with generic integration or platform-specific skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid reference for deploying Granola integrations with clear per-platform setup steps, useful Zapier templates, and a helpful error handling table. Its main weaknesses are the lack of explicit validation checkpoints in workflows (e.g., 'test with a sample note'), uneven depth across integrations (Slack/HubSpot are detailed while Attio/Affinity are skeletal), and the monolithic structure that would benefit from splitting into per-integration files.
Suggestions
Add explicit validation steps after each integration setup (e.g., 'Test: Share a sample note to Slack and verify it appears in the configured channel within 30 seconds')
Either flesh out Attio and Affinity sections to match HubSpot/Slack depth, or collapse them into a brief 'Other CRM Integrations' section with links to external docs
Split per-integration details into separate files (e.g., granola-slack.md, granola-hubspot.md) and keep SKILL.md as a concise overview with links
Add a verification checklist at the end of the multi-integration workflow to confirm each leg of the chain is firing correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary padding — the overview explains what Granola integrations are (which Claude doesn't need), and some integrations like Attio and Affinity are thin enough to be collapsed into a single section. The tables and Zapier recipes add useful density, but the overall document could be tightened by ~20-30%. | 2 / 3 |
Actionability | Setup steps are concrete (click paths like 'Settings > Integrations > Slack > Connect'), and the Zapier YAML snippets provide useful templates. However, there's no truly executable code — the YAML blocks are illustrative config rather than runnable scripts, and the multi-integration workflow is a diagram rather than actionable steps. CRM integrations (especially Attio and Affinity) lack specific configuration details. | 2 / 3 |
Workflow Clarity | Each integration has a clear setup sequence, and the multi-integration workflow provides a good visual chain. However, there are no explicit validation/verification checkpoints — no 'test by sending a sample note and confirming it appears in Slack' step, no feedback loops for when authorization fails mid-setup. The error handling table partially compensates but is reactive rather than built into the workflow. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headings and tables, and the Resources section provides external links. However, for a skill this long (~150+ lines covering 6 integrations), the detailed per-integration instructions could be split into separate files with SKILL.md serving as an overview. No bundle files exist to support this, and the 'Next Steps' reference to 'granola-webhooks-events' is unverifiable. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
a04d1a2
- Reviewed
Table of Contents
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.