guidewire-rate-limits
Manage Guidewire Cloud API rate limits, quotas, and throttling. Use when encountering 429 errors, optimizing API call patterns, or implementing rate limit handling strategies. Trigger with phrases like "guidewire rate limit", "api quota", "429 error", "throttling", "api limits guidewire".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill guidewire-rate-limits80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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 excellent trigger terms and completeness. The explicit 'Use when' and 'Trigger with phrases' sections provide clear guidance for skill selection. The main weakness is that the capabilities could be more specific about what concrete actions the skill enables beyond the general 'manage' verb.
Suggestions
Replace 'Manage' with specific actions like 'Implement exponential backoff, configure retry logic, monitor quota usage, and handle 429 responses for Guidewire Cloud API rate limits'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Guidewire Cloud API rate limits) and some actions (manage rate limits, quotas, throttling), but lacks specific concrete actions like 'implement exponential backoff', 'configure retry logic', or 'monitor quota usage'. | 2 / 3 |
Completeness | Clearly answers both what (manage rate limits, quotas, throttling) and when (encountering 429 errors, optimizing API call patterns, implementing rate limit handling). Includes explicit 'Use when' clause and 'Trigger with phrases' guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'guidewire rate limit', 'api quota', '429 error', 'throttling', 'api limits guidewire'. These are specific, natural phrases a user encountering these issues would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Guidewire' as a specific platform identifier combined with rate limiting context. The combination of 'guidewire' + '429 error' + 'api quota' creates a clear niche unlikely to conflict with generic API or rate limiting skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, actionable skill with excellent executable code examples covering multiple rate limiting strategies. However, it's overly long for a single skill file, includes some unnecessary explanatory content, and lacks explicit validation steps to confirm implementations are working correctly. The content would benefit from being split into a concise overview with references to detailed implementation files.
Suggestions
Remove the Prerequisites section - Claude already understands HTTP rate limiting and exponential backoff concepts
Split detailed implementations (circuit breaker, Gosu code, monitoring) into separate reference files and link from a concise overview
Add explicit validation steps, e.g., 'Test rate limit handling by temporarily lowering thresholds and verifying backoff behavior in logs'
Remove redundant code comments that merely restate what the code obviously does
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity. The prerequisites section explains concepts Claude already knows (HTTP rate limiting, exponential backoff patterns). Some code comments are redundant (e.g., '// Track rate limits from response headers' before a class called RateLimitTracker). | 2 / 3 |
Actionability | Provides fully executable TypeScript and Gosu code examples that are copy-paste ready. Includes complete class implementations, specific HTTP headers, concrete rate limit values, and practical patterns like request queuing and circuit breakers. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced (Steps 1-5), but lacks explicit validation checkpoints. For rate limiting operations that can fail silently or cause cascading issues, there's no clear 'verify rate limit handling is working' step or feedback loop for confirming the implementation is effective. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic at ~400 lines. The Gosu implementation, monitoring code, and circuit breaker pattern could be split into separate reference files. Only minimal external references are provided (Resources section links, Next Steps). | 2 / 3 |
Total | 9 / 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 | |
- 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.