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.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, highly actionable skill body built around executable correct/wrong code contrasts and a clear architectural checklist. It loses only a little on workflow clarity (recall-based checklist vs. executable validation loop) and progressive disclosure (no bundle files, slightly thin filter-query section).

Suggestions

Add an explicit verification feedback loop to the checklist — e.g., 'register on the boundary, then send a test command in each chat type and confirm the expected handler fires' — to turn recall-based checks into an executable validate-fix-retry cycle.

Expand the 'grammY Filter Query Language' section beyond a single link with 1–2 inline predicate examples, or move detailed query patterns into a references file the body points to, deepening progressive disclosure.

Add a brief note on how to test handlers locally (e.g., grammY bot.inspect() or a dev token) so the workflow includes a concrete validation step before registration.

Dimension	Reasoning	Score
Conciseness	Lean throughout: jumps straight into executable patterns with no padding about what Telegram or grammY is; every section (handler structure, filter chains, context type, checklist) earns its tokens.	5 / 5
Actionability	Provides copy-paste-ready TypeScript showing correct vs. wrong patterns for filter chains, commands, and message routing, plus concrete registration and context-composition details.	5 / 5
Workflow Clarity	Clear sequenced structure with a closing checklist that acts as validation checkpoints, but the checklist is verification-by-recall rather than an executable validate-and-fix feedback loop, so it sits just below a 5.	4 / 5
Progressive Disclosure	Well-organized sections with external links signaled one level deep (grammy.dev filter-queries guide, Telegram Bot API docs); no bundle files to split into, though the filter-query section is slightly thin and could point to a deeper reference.	4 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that names a specific framework and enumerates concrete capabilities alongside a precise 'Use when' trigger clause. It is concise, comprehensive, and clearly distinguishes the skill from alternatives.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'writing grammY Telegram bot handlers, middleware, and plugins' — covering the core surface comprehensively.	5 / 5
Completeness	Explicitly answers both 'what' (writing handlers/middleware/plugins) and 'when' via a concrete 'Use when...' clause enumerating specific trigger scenarios.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms including synonyms and specific entry points: 'bot commands, inline queries, callback queries, message handlers, or middleware' — exactly what a user would name.	5 / 5
Distinctiveness Conflict Risk	Clear niche scoped to grammY Telegram bots with distinct handler-type triggers; minimal conflict risk with unrelated skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: divaltor/starlight
Path: .agents/skills/grammy-bots/SKILL.md
Commit: b273683

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.