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.
100
100%
Does it follow best practices?
Impact
Pending
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 provides explicit trigger guidance via a 'Use when' clause with natural developer terminology. It follows the third-person voice convention 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 distinct, concrete 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
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that is concise, actionable, and well-organized. It focuses exclusively on project-specific conventions (filter chain pattern, file structure, context types) without explaining concepts Claude already knows. The anti-pattern examples (CORRECT vs WRONG) are particularly effective for teaching the unconventional filter-chain-over-if-return pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what grammY is, what Telegram bots are, or how middleware works conceptually. Every section delivers project-specific patterns and conventions that Claude wouldn't know by default. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples for handler structure, filter chains, and registration. Includes both correct and incorrect patterns with clear CORRECT/WRONG labels, making guidance immediately actionable. | 3 / 3 |
Workflow Clarity | For this type of skill (writing handlers, not a destructive multi-step process), the workflow is clear: file structure → filter chain pattern → context types → separation of concerns → checklist. The checklist at the end serves as a validation checkpoint. No destructive/batch operations require feedback loops. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, appropriately references external documentation (grammy.dev, Telegram Bot API) for deeper details, and keeps the SKILL.md focused on project-specific conventions. No unnecessary inline bloat or deeply nested references. | 3 / 3 |
Total | 12 / 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
06a2962
- 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.