Content
50%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body delivers mostly real, copy-paste-ready code across setup, wallet connection, and monetization patterns, with genuinely useful anti-patterns. However, mis-nested code fences break the examples' rendering, the Sharp Edges table references sections (including the high-severity initData validation) that are missing entirely, and there is redundant filler (duplicated role text, Capabilities list, boilerplate 'When to Use').
Suggestions
Fix the mis-nested code fences: the Patterns sections open ```javascript fences that wrap inner ```html/```jsx blocks, breaking markdown rendering; use correct top-level fences per example.
Add the missing sections the Sharp Edges table promises - especially '## Validating initData' (server-side HMAC validation of initData), the highest-severity item, plus TON Connect mobile fixes, performance, and MainButton usage.
Name the bot library in the Bot Integration example (e.g., 'telegraf') and remove the duplicated role paragraph, redundant Capabilities list, and the filler 'When to Use' section.
Split the TON Connect and Monetization patterns into reference files (e.g., references/ton-connect.md, references/monetization.md) and link them from a leaner SKILL.md overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly code-driven and efficient, but the role paragraph repeats the frontmatter description verbatim, the 8-item Capabilities list duplicates what the Patterns sections demonstrate, and the 'When to Use' section is empty filler ('This skill is applicable to execute the workflow or actions described in the overview.'). | 3 / 5 |
Actionability | Mostly concrete, real code (HTML setup, React hook, TON Connect, Stars invoice, referral share), but the code fences are mis-nested (outer ```javascript fences wrap ```html/```jsx blocks, breaking rendering), the Bot Integration example never names its library, and the Sharp Edges table references sections like '## Validating initData' that do not exist - the single most important security step is promised but never shown. | 3 / 5 |
Workflow Clarity | The Patterns imply a rough sequence (setup -> connect wallet -> monetize) and each pattern has a 'When to use' line, but there are no validation checkpoints anywhere: the TON transaction and payment flows proceed with no verification steps, and the promised initData validation section (the highest-severity sharp edge) is absent. | 3 / 5 |
Progressive Disclosure | Section headers organize the ~285-line body reasonably, but there are no bundle files: the TON Connect integration and monetization details are inlined content that belongs in separate reference files, and the Sharp Edges table's links point to non-existent sections, leaving navigation partially broken. | 3 / 5 |
Total | 12 / 20 Passed |