granola-sdk-patterns
Zapier automation patterns and Enterprise API integration for Granola. Use when building automated workflows, connecting Granola to 8,000+ apps via Zapier, or querying the Enterprise API for notes and transcripts. Trigger: "granola zapier", "granola automation", "granola API", "granola SDK".
59
70%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/granola-pack/skills/granola-sdk-patterns/SKILL.mdQuality
Discovery
89%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 solid skill description that clearly identifies its niche (Granola + Zapier/API integration) with explicit trigger terms and a clear 'Use when' clause. Its main weakness is that the specific capabilities could be more granular—listing concrete actions like creating zaps, setting up triggers/actions, or specific API operations would strengthen it. Overall it performs well for skill selection purposes due to its distinctive domain.
Suggestions
Add more concrete actions to improve specificity, e.g., 'Create Zapier triggers for new notes, set up multi-step zaps, authenticate API keys, fetch transcripts by date range'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Zapier automation, Enterprise API, Granola) and mentions some actions like 'building automated workflows', 'connecting Granola to 8,000+ apps', and 'querying the Enterprise API for notes and transcripts', but doesn't list multiple concrete specific actions (e.g., creating zaps, handling webhooks, specific API endpoints). | 2 / 3 |
Completeness | Clearly answers both 'what' (Zapier automation patterns and Enterprise API integration for Granola) and 'when' (Use when building automated workflows, connecting Granola to apps via Zapier, or querying the Enterprise API). Includes explicit trigger terms as well. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms ('granola zapier', 'granola automation', 'granola API', 'granola SDK') and natural keywords like 'automated workflows', 'Zapier', '8,000+ apps', 'notes and transcripts'. These are terms users would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of Granola + Zapier + Enterprise API. The trigger terms are very specific ('granola zapier', 'granola API') and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 comprehensive overview of Granola integration patterns across Zapier, Enterprise API, and native integrations, with useful tables and structured examples. Its main weaknesses are the lack of validation checkpoints in multi-step workflows, pseudo-YAML patterns that aren't truly executable, and a monolithic structure that would benefit from splitting detailed patterns into separate reference files. The error handling table is a nice addition but doesn't compensate for missing inline verification steps.
Suggestions
Add explicit validation/testing steps after key operations (e.g., 'Test the Zap with a sample note before enabling' after Step 2, 'Verify API key with a test curl request' after Step 3)
Split the detailed Zap patterns and API reference into separate bundle files (e.g., ZAP_PATTERNS.md, API_REFERENCE.md) and keep SKILL.md as a concise overview with references
Make the API examples more actionable by including a complete working script (e.g., a Python script that lists notes and extracts action items) rather than just curl snippets
Remove the 'Output' section which restates goals without adding actionable content, and trim the Overview to just the essential integration channels
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary sections like the 'Output' section which just restates what the skill does, and the 'Overview' paragraph explains what Granola is in a way Claude doesn't need. The YAML-style Zap patterns are a reasonable format but some are verbose with redundant commentary. The reverse-engineered endpoints section adds useful but potentially risky information. | 2 / 3 |
Actionability | The Zapier patterns use YAML-like pseudocode rather than actual executable configurations—Zapier is configured via UI, so these are descriptive rather than executable. The curl commands for the Enterprise API are concrete and copy-paste ready, which is good. However, the JavaScript code step is a useful snippet but embedded in pseudo-YAML. Overall it's a mix of concrete API examples and descriptive workflow outlines. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced (Step 1 through Step 5) and the folder-based routing table provides good organizational guidance. However, there are no explicit validation checkpoints—no 'verify the Zap fires correctly' step, no 'test the API key works' step, and the multi-step automation chain in Step 4 has no error recovery or feedback loops for what to do when individual steps fail in the chain. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and tables, but it's a long monolithic file (~150+ lines of content) with no bundle files to offload detailed patterns into. The Zap patterns, API reference, and error handling could each be separate files. The reference to 'granola-common-errors' at the end is good but the inline content is heavy for a single SKILL.md. | 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.