granola-reference-architecture
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill granola-reference-architectureEnterprise meeting workflow architecture with Granola. Use when designing enterprise deployments, planning integrations, or architecting meeting management systems. Trigger with phrases like "granola architecture", "granola enterprise", "granola system design", "meeting system", "granola infrastructure".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
42%This skill provides a comprehensive reference architecture overview with good visual organization and structure, but lacks actionable implementation guidance. It reads more like documentation or a whitepaper than a skill that teaches Claude how to perform specific tasks. The content describes what an enterprise Granola deployment looks like rather than how to build or configure one.
Suggestions
Add concrete, executable examples for key integration points (e.g., actual Zapier configuration JSON, API calls, or setup commands)
Include step-by-step implementation workflows with validation checkpoints for deploying each tier of the architecture
Replace descriptive sections with actionable checklists or decision trees that guide specific architecture decisions
Add troubleshooting guidance with specific error scenarios and resolution steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient with good use of tables and diagrams, but includes some redundant information (e.g., the ASCII architecture diagram duplicates what's explained in tables below). Some sections like 'Component Responsibilities' explain obvious concepts Claude would know. | 2 / 3 |
Actionability | The skill is almost entirely descriptive rather than instructive. It describes architecture patterns and data flows but provides no executable code, specific commands, or concrete implementation steps. The YAML snippet is illustrative rather than actionable. | 1 / 3 |
Workflow Clarity | Data flow patterns are clearly visualized with ASCII diagrams showing sequences, but there are no validation checkpoints, error handling, or feedback loops. The 'Failover Procedures' section lists steps but lacks specificity on how to execute them. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, tables for reference data, and appropriate external links. The 'Next Steps' section provides clear navigation to related content. Structure is logical and easy to navigate. | 3 / 3 |
Total | 8 / 12 Passed |
Activation
40%This description suffers from excessive abstraction and buzzword usage ('workflow architecture', 'architecting meeting management systems') without explaining concrete capabilities. While it includes explicit trigger guidance, the lack of specific actions makes it difficult to understand what this skill actually enables Claude to do. The Granola branding provides some distinctiveness but the core value proposition is unclear.
Suggestions
Replace abstract terms with concrete actions (e.g., 'Configure Granola for multi-team deployments, set up SSO integration, design meeting note workflows, plan API integrations with calendar systems').
Add natural user phrases to triggers like 'set up Granola for my organization', 'Granola deployment', 'configure Granola', 'Granola for enterprise teams'.
Clarify what specific outputs or guidance this skill provides - does it generate architecture diagrams, configuration guides, integration plans?
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'workflow architecture', 'planning integrations', and 'architecting meeting management systems' without listing any concrete actions. No specific capabilities are described - just abstract concepts. | 1 / 3 |
Completeness | Has a 'Use when' clause and explicit trigger phrases, but the 'what' portion is extremely weak - it doesn't explain what the skill actually does beyond vague architectural concepts. The triggers exist but the capabilities are unclear. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'granola architecture', 'granola enterprise', 'meeting system', but these are somewhat technical/jargon-heavy. Missing natural user phrases like 'set up Granola for my company', 'deploy Granola', or 'Granola for teams'. | 2 / 3 |
Distinctiveness Conflict Risk | The Granola-specific terms provide some distinctiveness, but 'meeting system', 'enterprise deployments', and 'planning integrations' are generic enough to potentially conflict with other enterprise or meeting-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
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.