grammy-bots
Guides writing grammY Telegram bot handlers, middleware, and plugins. Use when creating or modifying bot commands, inline queries, callback queries, message handlers, or middleware.
76
93%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 strong skill description that clearly identifies its domain (grammY Telegram bot development), lists specific capabilities (handlers, middleware, plugins), and includes an explicit 'Use when' clause with natural trigger terms. It follows third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: writing handlers, middleware, plugins, bot commands, inline queries, callback queries, message handlers. These are all concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (guides writing grammY Telegram bot handlers, middleware, and plugins) and 'when' (explicit 'Use when' clause listing specific trigger scenarios like creating/modifying bot commands, inline queries, callback queries, message handlers, or middleware). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'grammY', 'Telegram bot', 'handlers', 'middleware', 'plugins', 'bot commands', 'inline queries', 'callback queries', 'message handlers'. Good coverage of terms a developer working with grammY would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting specifically the grammY framework for Telegram bots. The combination of 'grammY' and 'Telegram bot' with specific handler types makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently communicates project-specific conventions for grammY bot development. Its strongest aspects are the concrete code examples with explicit correct/incorrect patterns and the lean, assumption-rich writing style. The only notable gap is the lack of validation or verification steps for ensuring filter chain correctness and handler registration.
Suggestions
Add a brief verification step or debugging tip for confirming filter chains are exhaustive and mutually exclusive (e.g., a logging middleware or test approach to catch unhandled updates).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows TypeScript, bot frameworks, and general programming patterns. Every section delivers specific, non-obvious project conventions (filter chains over if-return, Composer per domain, error boundary registration) without explaining basic concepts. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples for handler structure, filter chains, and message routing. Includes both correct and incorrect patterns with clear CORRECT/WRONG labels, making guidance immediately copy-paste ready. | 3 / 3 |
Workflow Clarity | The checklist at the end provides a clear sequence, and the handler file structure shows registration steps. However, there are no explicit validation checkpoints or feedback loops for verifying that handlers are correctly registered or that filter chains are exhaustive—important for avoiding silent handler misses. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections progressing from file structure to core patterns to context types to separation of concerns. External references to grammy.dev and Telegram Bot API are clearly signaled and one level deep. The skill is appropriately self-contained without needing bundle files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- divaltor/starlight
- Commit
421844e
- 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.