CtrlK
BlogDocsLog inGet started
Tessl Logo

granola-core-workflow-b

Post-meeting note processing, sharing, and follow-up workflows in Granola. Use when enhancing notes after meetings, sharing to Slack/Notion/CRM, drafting follow-up emails, or processing action items. Trigger: "granola post-meeting", "share granola notes", "granola follow-up", "granola enhance", "granola share".

63

Quality

75%

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-core-workflow-b/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable workflow with clear sequencing, a review checklist, and error-recovery guidance. The main weakness is conciseness — the sample email and chat-query lists add padding that could be tightened without losing clarity.

Suggestions

Trim the full sample email body in Step 4 to a short illustrative excerpt and condense the chat-query bullet list to preserve token budget.

Add an explicit validation gate before sharing (e.g., 'Only proceed to Step 3 once the Step 2 checklist passes') to strengthen the workflow's feedback loop.

Consider moving the Error Handling and Folder tables into a reference file if the skill grows, to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient procedural guidance, but the full sample email body in the Chat example and the long enumeration of chat queries could be trimmed; a few padded sections compete with the token budget.

3 / 5

Actionability

Concrete UI guidance with specific button paths ('Click Share > Slack', 'Click Share > Notion') and example chat dialogue; as an instruction-only SaaS skill it is actionable, with minor gaps where a GUI flow cannot be scripted.

4 / 5

Workflow Clarity

Six clearly sequenced steps with a Step 2 review checklist and an Error Handling table providing feedback loops, but validation is a soft review rather than an explicit hard gate before sharing.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and clearly signaled references to sibling skills and external docs; no bundle files exist, so all content is inline, which is appropriate for this length with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

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

A strong description that explicitly answers both what and when with concrete trigger phrases and multiple specific actions. Minor gaps in capability coverage and slight command-style phrasing of some triggers keep specificity and trigger quality just below the top anchor.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'enhancing notes', 'sharing to Slack/Notion/CRM', 'drafting follow-up emails', 'processing action items' — but omits body-covered capabilities like People & Companies management and folder organization, leaving minor gaps.

4 / 5

Completeness

Clearly states both what ('Post-meeting note processing, sharing, and follow-up workflows in Granola') and when ('Use when enhancing notes after meetings, sharing..., drafting follow-up emails, or processing action items') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides explicit trigger phrases ('granola post-meeting', 'share granola notes', 'granola follow-up', 'granola enhance', 'granola share') with good natural coverage, though some read as command-style rather than common synonyms.

4 / 5

Distinctiveness Conflict Risk

'Granola' is a clear niche with distinct post-meeting triggers, but sibling skills (granola-core-workflow-a, granola-sdk-patterns) create minor overlap risk within the same app family.

4 / 5

Total

17

/

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.