CtrlK
BlogDocsLog inGet started
Tessl Logo

coderabbit-rate-limits

Understand and handle CodeRabbit and GitHub API rate limits for review automation. Use when hitting rate limits on @coderabbitai commands, automating review queries, or building scripts that interact with CodeRabbit via the GitHub API. Trigger with phrases like "coderabbit rate limit", "coderabbit throttling", "coderabbit too many requests", "github api rate limit coderabbit".

64

Quality

77%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/coderabbit-pack/skills/coderabbit-rate-limits/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%

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

The skill provides highly actionable, executable bash scripts for handling both GitHub API and CodeRabbit rate limits, which is its strongest quality. However, it's somewhat verbose for what it covers, with repeated patterns across scripts and some unnecessary explanatory text. The workflow structure would benefit from clearer validation checkpoints and the large code blocks could be extracted into bundle files for better progressive disclosure.

Suggestions

Extract the bash scripts (rate-safe-query.sh, cache-coderabbit-metrics.sh) into bundle files and reference them from SKILL.md to improve progressive disclosure and reduce inline bulk.

Add explicit validation checkpoints between steps, such as verifying the rate limit check output before proceeding to bulk queries, and confirming cache file integrity after creation.

Trim the Overview and Prerequisites sections — Claude doesn't need to be told what rate limits are or that it needs 'understanding of GitHub rate limit headers'.

Consolidate the rate limit checking pattern (used in Steps 1, 2, and implicitly in Step 5) into a single reusable snippet referenced by the other steps to reduce repetition.

DimensionReasoningScore

Conciseness

The skill includes some unnecessary context (e.g., the Prerequisites section explaining 'Understanding of GitHub rate limit headers', the Overview paragraph restating what's obvious from the title). The tables and code are mostly efficient, but the overall document is quite long with some redundancy between steps (e.g., rate limit checking logic repeated across multiple scripts). The CodeRabbit command rate limits section in Step 3 uses markdown comments to explain things Claude already knows.

2 / 3

Actionability

All scripts are fully executable bash with proper error handling (set -euo pipefail), real gh CLI commands, and concrete jq filters. The code is copy-paste ready with parameterized inputs, and covers REST, GraphQL, and caching patterns with complete implementations.

3 / 3

Workflow Clarity

Steps are numbered and sequenced, but they read more like independent recipes than a cohesive workflow. There are rate limit checks within scripts (good), but no explicit validation checkpoint between steps. The error handling table at the end is helpful but disconnected from the workflow steps themselves. Missing feedback loops for the overall process (e.g., what to do if the cache script fails, how to verify the GraphQL output is correct).

2 / 3

Progressive Disclosure

The content is a monolithic document with ~200 lines of inline code that could benefit from being split into separate files (e.g., the bash scripts as standalone files in a bundle). References to external resources are present at the bottom, and there's a cross-reference to 'coderabbit-security-basics', but the main content is all inline with no bundle files to support progressive disclosure.

2 / 3

Total

9

/

12

Passed

Description

89%

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 well-structured skill description with strong trigger terms and explicit 'Use when' and 'Trigger with' clauses that make it highly discoverable. Its main weakness is that the 'what' portion is somewhat vague — 'understand and handle' doesn't convey specific concrete actions like implementing retry logic, checking rate limit headers, or configuring request intervals. Overall it's a solid description for a narrow, well-defined niche.

Suggestions

Replace the vague 'Understand and handle' with specific concrete actions, e.g., 'Implement retry logic, configure backoff strategies, check rate limit headers, and troubleshoot 429 errors for CodeRabbit and GitHub API rate limits.'

DimensionReasoningScore

Specificity

The description names the domain (CodeRabbit/GitHub API rate limits) and mentions some actions like 'handle rate limits', 'automating review queries', and 'building scripts', but doesn't list multiple concrete specific actions (e.g., what exactly does 'handle' mean — retry logic, backoff strategies, quota checking?).

2 / 3

Completeness

Clearly answers both 'what' (understand and handle CodeRabbit and GitHub API rate limits for review automation) and 'when' (explicit 'Use when...' clause with specific scenarios, plus a 'Trigger with phrases like...' section providing additional explicit triggers).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms: 'coderabbit rate limit', 'coderabbit throttling', 'coderabbit too many requests', 'github api rate limit coderabbit', '@coderabbitai commands'. These are phrases users would naturally say when encountering this issue.

3 / 3

Distinctiveness Conflict Risk

Very specific niche combining CodeRabbit + rate limits + GitHub API. This is unlikely to conflict with general GitHub skills, general rate limiting skills, or general CodeRabbit usage skills due to the narrow intersection of these topics.

3 / 3

Total

11

/

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.

Validation9 / 11 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

9

/

11

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.