CC telegram-checklist
Native Telegram To-Do checklists: create, append, toggle.
Native Telegram To-Do checklists: create, append, toggle.
As a process C 59/100 · Has gaps — weak spots: result and completion, consistency, running it twice
TemplateTelegramDesignSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0Consistency. Frontmatter name (telegram-checklist) differs from the folder (hermes-telegram-checklist)
- 30Running it twice. 31 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 30 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 2887 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 57: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 14 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.