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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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 body is highly actionable with complete, executable code and a clear step sequence, but it is verbose and duplicates the reference file, lacks inline validation gates for batch operations, and leaves the reference orphaned and unlinked.

Suggestions

Move the detailed per-step YAML/JS into references/implementation.md and keep SKILL.md as a concise overview with links, eliminating the duplication between the body and the reference file.

Add explicit inline validation checkpoints (e.g., verify Zapier Code output before the batch issue-creation step; confirm the GitHub PAT has repo scope before dispatching) rather than relying solely on the post-hoc testing checklist.

Signal the reference from the body (e.g., 'See implementation.md for full webhook setup and retry config') so references/implementation.md is discoverable instead of orphaned.

Dimension	Reasoning	Score
Conciseness	Largely concrete code with no padding about concepts Claude already knows, but the six full inline YAML/JS blocks are verbose and duplicate material also present in references/implementation.md, so the body could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code throughout — a Zapier Code JS parser, per-step YAML, a GitHub Actions workflow, and a curl test command with concrete values.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced with an error-handling table and testing checklist, but inline validate-then-proceed checkpoints are absent for a pipeline that performs batch issue creation and repo commits, capping clarity at 2 per the batch-operation guideline.	2 / 3
Progressive Disclosure	Section headers give structure and a reference file exists, but the reference is never linked from the body and duplicates inline content rather than holding deeper detail, fitting the 'references present but not clearly signaled; content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

100%

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

A strong, third-person description that concisely states concrete capabilities and pairs them with an explicit set of natural trigger terms. It fully answers both 'what' and 'when' with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'GitHub Issues, Linear tasks, Slack notifications, and documentation updates using Zapier and GitHub Actions' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Build automated pipelines from Granola meeting notes to...') and when via a dedicated 'Trigger:' clause, satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say ('granola to github', 'granola to linear', 'meeting notes automation') with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear Granola-specific niche with granola-prefixed triggers, making conflict with unrelated skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 1628598

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.