CtrlK
BlogDocsLog inGet started
Tessl Logo

granola-ci-integration

Build automated pipelines from Granola meeting notes to GitHub Issues, Linear tasks, Slack notifications, and documentation updates using Zapier and GitHub Actions. Trigger: "granola CI", "granola automation pipeline", "granola to github", "granola to linear", "meeting notes automation".

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/granola-pack/skills/granola-ci-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

The content is actionable and reasonably concise with a clear step sequence, but it suffers from missing inline validation for a batch operation and a disconnected, duplicated reference bundle that is not surfaced from the body.

Suggestions

Add mid-pipeline validation checkpoints (e.g. verify the Zapier trigger fired and action items were parsed before creating issues) to lift workflow clarity above the batch-operation cap.

Link references/implementation.md from the body and de-duplicate the overlapping Zapier/GitHub Actions content so the reference file is actually signaled and used as one-level-deep detail.

Trim the Overview, Complete Pipeline Flow, and Output sections, which restate the description and step contents, to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly tight, concrete code with minimal concept explanation, though the Overview, Complete Pipeline Flow, and Output sections restate information already conveyed elsewhere and could be trimmed.

4 / 5

Actionability

Provides concrete JavaScript, GitHub Actions workflow YAML, and Zapier step configs that are largely executable, but Zapier GUI steps are represented as descriptive YAML with placeholders ('your-org/your-repo', '{{github_pat}}') leaving minor gaps.

4 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced with an error table and testing checklist, but this batch skill (creating multiple issues/tasks per meeting) lacks inline validation checkpoints between steps, so the batch-operation cap at 3 applies.

3 / 5

Progressive Disclosure

Sections are well-organized, but the provided references/implementation.md bundle is never linked from the body and its content is largely duplicated inline, so references are not signaled and content that belongs in a separate file is inlined.

3 / 5

Total

14

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 is specific, complete, and distinctive, clearly stating both capability and trigger conditions with concrete phrases. Trigger term coverage is strong but slightly short of fully comprehensive synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (GitHub Issues, Linear tasks, Slack notifications, documentation updates) and names the tools (Zapier, GitHub Actions), giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly states both what it does (build pipelines from Granola notes to named dev tools) and when to use it via a concrete 'Trigger:' clause with multiple phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Provides several natural trigger phrases ('granola CI', 'granola to github', 'granola to linear', 'meeting notes automation') that users would plausibly say, though it lacks synonyms or shorthand variations like bare 'granola'.

4 / 5

Distinctiveness Conflict Risk

The Granola-to-dev-tools niche via Zapier is highly specific with distinct triggers, making overlap with other skills minimal.

5 / 5

Total

19

/

20

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.