granola-observability
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill granola-observabilityMonitor Granola usage, analytics, and meeting insights. Use when tracking meeting patterns, analyzing team productivity, or building meeting analytics dashboards. Trigger with phrases like "granola analytics", "granola metrics", "granola monitoring", "meeting insights", "granola observability".
Review Score
65%
Validation Score
13/16
Implementation Score
38%
Activation Score
90%
Generated
Validation
Total
13/16Score
Passed| Criteria | Score |
|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) |
metadata_version | 'metadata' field is not a dictionary |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata |
Implementation
Suggestions 4
Score
38%Overall Assessment
This skill provides useful reference material for Granola analytics including metrics definitions, SQL schemas, and dashboard configurations. However, it reads more like a reference document than an actionable skill - it lacks a clear workflow for actually implementing observability, has no validation steps, and mixes conceptual information with implementation details without clear sequencing.
Suggestions
- Add a clear 'Getting Started' workflow with numbered steps: 1) Check prerequisites, 2) Access dashboard, 3) Set up export pipeline, 4) Verify data flowing, with explicit validation at each step
- Convert the YAML configurations to actual executable scripts or provide clear instructions on where/how to implement them (e.g., specific Zapier setup steps)
- Split detailed SQL schemas and dashboard configurations into separate reference files (e.g., SCHEMAS.md, DASHBOARDS.md) and keep SKILL.md as a concise overview with links
- Add a verification section showing how to confirm the observability pipeline is working correctly (expected outputs, test queries, health check commands)
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The content is reasonably efficient but includes some unnecessary structure like markdown checkboxes in code blocks and verbose YAML configurations that could be tightened. The metric tables are useful but some explanatory text is redundant. |
Actionability | 2/3 | Provides concrete SQL queries and YAML configurations, but much content is pseudocode/configuration templates rather than executable code. The API export example is good, but many sections describe what to do rather than providing copy-paste ready implementations. |
Workflow Clarity | 1/3 | No clear sequential workflow for setting up observability. Content is organized by topic but lacks step-by-step guidance, validation checkpoints, or feedback loops. A user wouldn't know where to start or how to verify their setup is working. |
Progressive Disclosure | 2/3 | Content is organized into logical sections with headers, but it's a monolithic document that could benefit from splitting detailed SQL schemas and dashboard configs into separate reference files. The 'Next Steps' reference is good but internal organization is dense. |
Activation
Suggestions 1
Score
90%Overall Assessment
This is a well-structured skill description with excellent trigger term coverage and clear completeness. The explicit 'Use when' and 'Trigger with' clauses make it easy for Claude to select appropriately. The main weakness is that the specific capabilities could be more concrete - it describes general categories (monitoring, analytics) rather than specific actions.
Suggestions
- Add more concrete actions to improve specificity, e.g., 'generate meeting frequency reports, track attendance trends, export analytics data, visualize participation metrics'
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (Granola usage/analytics) and mentions some actions (tracking, analyzing, building dashboards), but lacks concrete specific actions like 'generate reports', 'export data', or 'visualize trends'. |
Completeness | 3/3 | Clearly answers both what (monitor Granola usage, analytics, meeting insights) and when (tracking meeting patterns, analyzing team productivity, building dashboards) with explicit 'Use when' and 'Trigger with' clauses. |
Trigger Term Quality | 3/3 | Excellent coverage of natural trigger terms including 'granola analytics', 'granola metrics', 'meeting insights', 'granola monitoring', and 'granola observability' - these are terms users would naturally say when needing this skill. |
Distinctiveness Conflict Risk | 3/3 | Highly distinctive due to the specific 'Granola' product name combined with meeting analytics context. The unique trigger terms like 'granola analytics' and 'granola observability' make conflicts with other skills very unlikely. |