guidewire-rate-limits
Manage Guidewire Cloud API rate limits, quotas, and throttling for high-volume integrations. Trigger: "guidewire rate limits", "rate-limits".
56
48%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/guidewire-pack/skills/guidewire-rate-limits/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear, narrow niche (Guidewire Cloud API rate limiting) and provides explicit trigger terms, making it complete and distinctive. However, it could be more specific about the concrete actions it performs and could include more natural trigger term variations that users might actually say when encountering rate limit issues.
Suggestions
Add more specific concrete actions like 'configure retry strategies, set quota thresholds, handle 429 responses, implement backoff patterns'.
Expand trigger terms to include natural variations like 'API throttling', '429 errors', 'quota exceeded', 'too many requests', 'Guidewire API limits'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Guidewire Cloud API rate limits) and some actions (manage rate limits, quotas, throttling), but doesn't list specific concrete actions like 'configure retry logic', 'set quota thresholds', or 'monitor throttling metrics'. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage Guidewire Cloud API rate limits, quotas, and throttling for high-volume integrations) and 'when' (explicit trigger terms provided). The 'Trigger:' clause serves as an explicit 'use when' equivalent. | 3 / 3 |
Trigger Term Quality | Includes 'guidewire rate limits' and 'rate-limits' as trigger terms, but misses natural variations users might say like 'API throttling', 'quota exceeded', '429 errors', 'too many requests', 'Guidewire API limits', or 'high volume integration'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining Guidewire Cloud API with rate limiting/throttling concerns. Very unlikely to conflict with other skills due to the specific platform (Guidewire) and specific concern (rate limits/quotas). | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is extremely thin and lacks actionable content. It reads more like a brief summary or table of contents than an instructional skill. There are no code examples, no concrete rate limit values, no retry logic implementation, and no workflow for handling throttling scenarios.
Suggestions
Add executable code examples for exponential backoff on 429 responses (e.g., a Python or Gosu snippet with retry logic and jitter).
Include specific rate limit values or explain how to discover them per-tenant, along with concrete API Gateway throttling configuration steps.
Define a clear multi-step workflow: 1) Check current rate limits, 2) Implement backoff, 3) Monitor/validate, 4) Handle quota exhaustion — with explicit validation checkpoints.
Add at least one concrete example showing a batch API call and the expected 429 response handling pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but some statements are vague filler rather than precise instructions (e.g., 'Batch operations use the batch API endpoint' adds little value). It's not verbose, but not every token earns its place either. | 2 / 3 |
Actionability | There is no concrete code, no specific commands, no examples of exponential backoff implementation, no sample 429 handling, and no actual rate limit values or configuration snippets. The guidance is entirely abstract and descriptive. | 1 / 3 |
Workflow Clarity | There is no sequenced workflow, no steps for handling rate limits, no validation checkpoints, and no feedback loop for retry logic. The overview is a list of disconnected statements rather than a clear process. | 1 / 3 |
Progressive Disclosure | There is a reference to an implementation guide and external resources, which shows some structure. However, the overview itself is too thin to serve as a useful quick-start, and it's unclear what the referenced implementation guide contains. | 2 / 3 |
Total | 6 / 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
70e9fa4
- 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.