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 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 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 efficiently communicates a specific, opinionated pattern (filter chains over if/early-return) with concrete, executable examples and clear anti-patterns. The content is well-organized, appropriately scoped, and respects Claude's intelligence by focusing on project-specific conventions rather than general concepts. The checklist provides a useful validation summary.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows TypeScript, grammY basics, and general bot development concepts. Every section delivers specific, project-relevant patterns without explaining what Telegram bots are or how middleware conceptually works. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples for handler structure, filter chains, and registration. The CORRECT/WRONG pattern comparison is immediately actionable, and the context type definition is copy-paste ready. | 3 / 3 |
Workflow Clarity | The workflow is clear: create a Composer file scoped to a domain, use filter chains for routing, register on the error boundary. The checklist at the end serves as a validation checkpoint. For this type of skill (handler writing, not destructive operations), the sequence and constraints are unambiguous. | 3 / 3 |
Progressive Disclosure | The skill is well-structured 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. The content is appropriately sized for a single SKILL.md without needing additional bundle files. | 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.
5e7c296
Table of Contents
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.