CtrlK
BlogDocsLog inGet started
Tessl Logo

granola-rate-limits

Understand Granola plan limits, usage quotas, and API rate limiting. Use when hitting meeting limits, choosing between plans, or managing Enterprise API rate limits. Trigger: "granola limits", "granola quota", "granola plan", "granola usage", "granola restrictions".

68

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

77%

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

A well-organized, actionable reference that gives concrete commands and error-recovery guidance, but it is a long monolithic document that could benefit from splitting detail into bundle files and trimming redundant sections.

Suggestions

Split the detailed Plan Comparison and API Rate Limits tables into a separate reference file (e.g. references/plans.md) referenced from a concise overview, improving progressive_disclosure.

Consolidate the overlapping Plan Selection Guide with the Plan Comparison tables and merge Error Handling with What Happens at Limits to reduce redundancy and improve conciseness.

Add a short table of contents or lead summary so the monolithic single-file navigation is more explicit.

DimensionReasoningScore

Conciseness

The content is dense factual tables that Claude genuinely would not know, but at ~150 lines it is long and contains some redundancy (Plan Selection Guide overlaps the Plan Comparison tables; Error Handling overlaps What Happens at Limits), so it could be tightened rather than scoring a lean 3.

2 / 3

Actionability

For a reference skill it gives concrete, executable guidance: copy-paste curl command for rate-limit headers, specific UI navigation steps, and explicit error-to-fix mappings, which meets the actionable bar.

3 / 3

Workflow Clarity

Although mostly informational rather than a multi-step destructive workflow, the limit-resolution flow is unambiguous and the Error Handling / What Happens at Limits tables provide error-to-recovery feedback loops (429 -> Retry-After / exponential backoff), satisfying the simple-skill bar.

3 / 3

Progressive Disclosure

It is a single well-organized monolithic file with clear section headers but no bundle files or one-level-deep references; at over 50 lines the plan/API reference material is all inline where it could be split into separate reference files.

2 / 3

Total

10

/

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.

A strong, on-topic description with explicit what/when triggers and distinct Granola-specific keywords; its only weakness is the single vague action verb "Understand" in place of multiple concrete capabilities.

DimensionReasoningScore

Specificity

It names a clear domain ("Granola plan limits, usage quotas, and API rate limiting") but relies on a single abstract verb ("Understand") rather than listing multiple concrete actions, so it is not comprehensive enough for a 3.

2 / 3

Completeness

It states what the skill does ("Understand Granola plan limits, usage quotas, and API rate limiting") and explicitly when to use it ("Use when hitting meeting limits, choosing between plans, or managing Enterprise API rate limits") plus an explicit Trigger clause, satisfying both what and when.

3 / 3

Trigger Term Quality

The Trigger clause lists five natural user phrases ("granola limits", "granola quota", "granola plan", "granola usage", "granola restrictions"), giving good coverage of terms a user would say when hitting limits.

3 / 3

Distinctiveness Conflict Risk

All triggers are Granola-specific and the domain is a narrow product niche, making it unlikely to fire for unrelated skills.

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.