gamma-webhooks-events
Handle Gamma webhooks and events for real-time updates. Use when implementing webhook receivers, processing events, or building real-time Gamma integrations. Trigger with phrases like "gamma webhooks", "gamma events", "gamma notifications", "gamma real-time", "gamma callbacks".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/gamma-pack/skills/gamma-webhooks-events/SKILL.mdQuality
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 solid description with excellent trigger term coverage and clear 'what/when' structure. Its main weakness is that the capability descriptions are somewhat generic—it describes webhook handling at a high level without listing specific concrete actions (e.g., event types handled, signature verification, retry logic). The explicit trigger phrases and Gamma-specific focus make it highly distinctive and easy to select correctly.
Suggestions
Add more specific concrete actions beyond generic webhook handling, e.g., 'verify webhook signatures, parse event payloads, handle retry logic, configure endpoint URLs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gamma webhooks/events) and some actions ('implementing webhook receivers', 'processing events', 'building real-time integrations'), but these are fairly generic descriptions of webhook handling rather than listing multiple specific concrete actions like parsing specific event types, verifying signatures, or configuring endpoints. | 2 / 3 |
Completeness | Clearly answers both 'what' (handle Gamma webhooks and events for real-time updates) and 'when' (explicit 'Use when...' clause with trigger scenarios and a 'Trigger with phrases like...' section). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms: 'gamma webhooks', 'gamma events', 'gamma notifications', 'gamma real-time', 'gamma callbacks'. These cover good variations of what a user would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The 'Gamma' qualifier combined with 'webhooks' and 'events' creates a clear niche. This is unlikely to conflict with generic webhook skills or other Gamma-related skills due to the specific focus on webhooks/events/real-time. | 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 well-structured skill with strong actionability—providing complete, typed TypeScript implementations across four distinct patterns for simulating webhooks via polling. Its main weaknesses are the length (all four patterns inline makes it heavy for a SKILL.md) and the absence of explicit validation/verification checkpoints in the workflow, which is important for background processing and polling-based architectures.
Suggestions
Add explicit validation checkpoints, e.g., 'Verify the generation started by checking the returned generationId is non-empty' and 'Confirm the Bull worker is connected to Redis before queueing jobs'.
Move the Bull queue worker (Step 3) and HTTP callback (Step 4) into separate referenced files to keep SKILL.md focused on the core pattern, improving progressive disclosure.
Trim the event listener examples (Step 2) to show one handler with a comment indicating where to add more, rather than three separate listeners with placeholder logic.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity. The event listener examples with placeholder DB and Slack calls add bulk without being directly executable. The overview explaining what Gamma doesn't have is useful context but could be tighter. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code across multiple patterns (EventEmitter, Bull queue, HTTP callback). Code is complete with imports, types, and concrete implementations that are copy-paste ready with minimal adaptation. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (1-4), but there are no explicit validation checkpoints. Given that this involves polling with timeouts and background workers (operations that can fail silently), the lack of verification steps (e.g., 'confirm the worker is processing', 'verify the callback was received') is a gap. | 2 / 3 |
Progressive Disclosure | The skill references external resources and a next-steps skill, but the main content is quite long with all four patterns inline. The Bull queue worker and HTTP callback patterns could reasonably be split into separate reference files, with the SKILL.md providing the core EventEmitter pattern and linking out. | 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.