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".
86
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines its scope around Granola post-meeting workflows, lists concrete actions, provides explicit trigger guidance with a 'Use when' clause and dedicated trigger terms, and is highly distinctive due to the product-specific context. The description is concise yet comprehensive, covering both capabilities and activation conditions effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: enhancing notes after meetings, sharing to Slack/Notion/CRM, drafting follow-up emails, and processing action items. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (post-meeting note processing, sharing, follow-up workflows) and 'when' (explicit 'Use when' clause with specific triggers, plus a dedicated Trigger section with example phrases). | 3 / 3 |
Trigger Term Quality | Includes natural keywords like 'share granola notes', 'granola follow-up', 'granola enhance', plus mentions specific platforms (Slack, Notion, CRM) and actions (follow-up emails, action items) that users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Granola', the post-meeting context, and the combination of specific platforms (Slack/Notion/CRM). Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized, clearly sequenced workflow guide for Granola's post-meeting features. Its main weakness is that it describes GUI interactions rather than providing executable commands or API calls that Claude could directly act on, and it includes some descriptive content about features that doesn't add actionable value. The workflow structure and error handling are strong points.
Suggestions
Remove explanatory content about what the AI does during enhancement (bullet list under Step 1) and what the CRM tracks (bullet list under Step 5)—Claude doesn't need feature descriptions to follow the workflow.
Clarify what Claude's role is in this workflow—if Claude is guiding a user through GUI steps, frame it as coaching instructions; if there are API/automation hooks Claude can execute directly, include those instead of UI click paths.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., explaining what GPT-4o/Claude does during enhancement, describing what the built-in CRM tracks) that Claude would already understand. The content is reasonably organized but could be tightened—the folder table and CRM feature descriptions add bulk without much actionable value. | 2 / 3 |
Actionability | The steps are clearly described with UI click paths (e.g., 'Click Share > Slack'), but the guidance is entirely UI-driven with no executable code or API commands. The Chat example is illustrative but not something Claude can execute. The skill describes what a human does in a GUI rather than providing commands Claude can act on. | 2 / 3 |
Workflow Clarity | The six-step workflow is clearly sequenced with logical progression from enhancement through review, sharing, follow-up, CRM management, and organization. Step 2 includes an explicit review checklist before sharing (validation checkpoint), and the error handling table provides recovery guidance for common failures. | 3 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections, references to related skills ('granola-core-workflow-a', 'granola-sdk-patterns') for prerequisites and next steps, and a Resources section with external links. Content is appropriately scoped without deeply nested references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
c8a915c
- 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.