CtrlK
BlogDocsLog inGet started
Tessl Logo

granola-observability

Monitor Granola adoption, meeting analytics, and build custom dashboards. Use when tracking team meeting patterns, measuring adoption, building analytics pipelines, or creating executive reports. Trigger: "granola analytics", "granola metrics", "granola monitoring", "granola adoption", "meeting insights".

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The skill is highly actionable with complete, executable code and a clear step sequence, but it is held back by mild verbosity, missing explicit validation checkpoints for batch/data-load operations, and under-signaled use of its bundle reference file.

Suggestions

Add explicit validation checkpoints for the data pipeline (e.g., verify row counts / run a deduplication check after the BigQuery insert before reporting), and reference the existing Error Handling loop inline at the relevant step.

Link and signal references/implementation.md from the body where the detailed pipeline/schema belongs, moving the large inline BigQuery/Zapier blocks out of SKILL.md to improve progressive disclosure.

Tighten the Overview and Step 2 prose to remove context Claude already knows about adoption analytics, keeping only Granola-specific guidance.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete tables and code, but it re-explains some context Claude already knows (e.g., the Overview restating what adoption tracking is) and could be tightened; the inline BigQuery/Zapier examples are lengthy and partly restated across steps.

2 / 3

Actionability

Provides fully executable code blocks (Zapier transform, BigQuery schema DDL, SQL queries, a curl+python3 status check) that are specific and largely copy-paste ready.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 1-6), but the batch/destructive pipeline and data-load operations lack explicit validate-then-proceed checkpoints or feedback loops; the Error Handling table provides recovery notes rather than in-line validation gates.

2 / 3

Progressive Disclosure

The body is a single monolithic SKILL.md with substantial inline detail that could live in the existing references/implementation.md; the reference is neither signaled nor linked from the body, so navigation and content split are only partially realized.

2 / 3

Total

9

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states capabilities and includes explicit, natural trigger terms tied to the Granola analytics niche. It is slightly limited in the breadth of concrete actions listed, but otherwise answers what and when well.

DimensionReasoningScore

Specificity

Names the domain ("Monitor Granola adoption, meeting analytics, and build custom dashboards") and a few concrete actions, but the action list is narrow and not comprehensive enough to anchor at the highest level.

2 / 3

Completeness

Explicitly answers both what ("Monitor Granola adoption, meeting analytics, and build custom dashboards") and when ("Use when tracking team meeting patterns... Trigger: ..."), satisfying the what-and-when requirement.

3 / 3

Trigger Term Quality

Includes a natural Trigger clause with phrases users would plausibly say ("granola analytics", "granola metrics", "granola monitoring", "granola adoption", "meeting insights"), giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Granola-specific trigger terms and a clearly scoped analytics niche make it unlikely to fire for an unrelated skill, occupying a distinct niche.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.