gamma-prod-checklist
Production readiness checklist for Gamma integration. Use when preparing to deploy Gamma integration to production, or auditing existing production setup. Trigger with phrases like "gamma production", "gamma prod ready", "gamma go live", "gamma deployment checklist", "gamma launch".
76
72%
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/gamma-pack/skills/gamma-prod-checklist/SKILL.mdQuality
Discovery
79%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 excels at trigger term coverage, completeness of when/what guidance, and distinctiveness due to the specific 'Gamma integration' scope. However, it is notably weak on specificity—it fails to describe what the checklist actually covers or what concrete actions the skill performs (e.g., checking configuration, verifying API keys, validating error handling, reviewing monitoring setup). This makes it hard for Claude to know the depth and scope of the skill's capabilities.
Suggestions
Add specific concrete actions the checklist covers, e.g., 'Verifies API authentication, validates error handling, checks rate limiting, reviews monitoring and alerting configuration, confirms rollback procedures.'
Clarify what 'Gamma integration' refers to if possible, or list the types of integration components covered (API endpoints, webhooks, data pipelines, etc.) to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'production readiness checklist' but does not list any concrete actions or capabilities. It doesn't specify what the checklist covers, what steps are performed, or what outputs are produced—just that it's a 'checklist' for 'Gamma integration.' | 1 / 3 |
Completeness | It answers both 'what' (production readiness checklist for Gamma integration) and 'when' (preparing to deploy Gamma to production, auditing existing production setup) with explicit trigger phrases. Both dimensions are clearly addressed. | 3 / 3 |
Trigger Term Quality | The description includes a good set of natural trigger phrases: 'gamma production', 'gamma prod ready', 'gamma go live', 'gamma deployment checklist', 'gamma launch'. These are realistic phrases a user would say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The skill is narrowly scoped to 'Gamma integration' production readiness, which is a very specific niche. The trigger terms all include 'gamma' combined with production/deployment terms, making conflicts with other skills unlikely. | 3 / 3 |
Total | 10 / 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 solid production readiness checklist with good actionable code examples and comprehensive coverage of important production concerns. Its main weaknesses are the monolithic structure (everything inline rather than using progressive disclosure), lack of explicit ordering/dependencies between checklist sections, and some unnecessary inline comments explaining things Claude already knows. The verification script at the end is a nice touch but only validates API connectivity rather than the broader checklist completion.
Suggestions
Add explicit sequencing or dependency notes between sections (e.g., 'Complete Authentication & Security before Monitoring & Logging') and include validation checkpoints after critical sections.
Move detailed code examples (circuit breaker, error handling patterns) into separate reference files and keep the main checklist lean with links to those files.
Remove redundant inline comments like '# 30000: 30 seconds in ms' and '# HTTP 503 Service Unavailable' — Claude already knows these.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The checklist is reasonably efficient but includes some unnecessary inline comments (e.g., '# 30000: 30 seconds in ms', '# HTTP 503 Service Unavailable', '# HTTP 200 OK') that explain things Claude already knows. The checklist items themselves are lean, but the overall document is somewhat long for what amounts to a checklist. | 2 / 3 |
Actionability | The skill provides concrete, executable code examples for key areas (client configuration, error handling with Sentry, health checks, circuit breakers, and a verification bash script). Checklist items are specific and checkable rather than vague. | 3 / 3 |
Workflow Clarity | The checklist is well-organized into numbered sections with clear categories, but it lacks explicit sequencing guidance (which items must be done before others?) and has no validation checkpoints or feedback loops between sections. The final verification script only checks API connectivity, not whether all checklist items are actually complete. | 2 / 3 |
Progressive Disclosure | The content is structured with clear sections and references external resources at the end, but the document is quite long and monolithic. Some sections (like the full circuit breaker implementation or error handling patterns) could be split into separate reference files, with the checklist itself kept leaner. | 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 | |
- 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.