CRITICAL: Use for Rust news and daily/weekly/monthly reports. Triggers on: rust news, rust daily, rust weekly, TWIR, rust blog, Rust 日报, Rust 周报, Rust 新闻, Rust 动态
70
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/rust-daily/SKILL.mdQuality
Discovery
62%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 description excels at trigger term coverage with both English and Chinese keywords, making it highly discoverable and distinctive. However, it critically fails to explain what the skill actually does - does it fetch news, summarize articles, compile reports, or something else? The lack of concrete actions makes it difficult to understand the skill's actual capabilities.
Suggestions
Add specific actions the skill performs, e.g., 'Fetches and summarizes Rust ecosystem news, compiles daily/weekly/monthly reports from sources like This Week in Rust'
Restructure to follow the pattern: '[Concrete actions]. Use when [triggers]' rather than leading with 'CRITICAL: Use for'
Specify what outputs the skill produces (summaries, curated links, formatted reports, etc.)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'news' and 'reports' but provides no concrete actions - it doesn't explain what the skill actually does (fetch, summarize, compile, analyze?). 'Use for Rust news' is vague about capabilities. | 1 / 3 |
Completeness | The 'when' is well-covered with explicit trigger terms, but the 'what' is severely lacking - it says 'Use for Rust news and daily/weekly/monthly reports' without explaining what actions the skill performs with that content. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'rust news', 'rust daily', 'rust weekly', 'TWIR', 'rust blog' plus Chinese equivalents (Rust 日报, Rust 周报, Rust 新闻, Rust 动态). These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Rust programming language news and reports. The specific trigger terms like 'TWIR' (This Week in Rust) and Chinese translations make it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid actionable guidance with executable commands and clear tool chain priorities. However, it's somewhat verbose with redundant information across sections, and the validation/error handling could be better integrated into the workflow rather than tacked on at the end. The dual-mode structure (agent vs inline) is practical but adds complexity.
Suggestions
Consolidate the tool chain priority section with the inline mode section to eliminate redundancy
Add explicit validation checkpoints after each source fetch (e.g., 'Verify at least 1 result before proceeding to next source')
Consider moving the detailed per-source fetch instructions to a separate SOURCES.md file, keeping only the workflow overview in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundancy - the tool chain priority section repeats information already covered in the inline mode section, and the dual-mode structure (agent vs inline) adds bulk that could potentially be streamlined. | 2 / 3 |
Actionability | Provides fully executable commands with specific CLI syntax, MCP function calls, and concrete selectors. The code examples are copy-paste ready with clear fallback options for each data source. | 3 / 3 |
Workflow Clarity | Steps are clearly listed with good sequencing, but validation is limited to a brief section at the end. Missing explicit checkpoints between fetching sources and combining results, and no feedback loop for handling partial failures during the multi-source fetch process. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections and tables, but everything is inline in one file. The agent file reference is good, but the detailed fetch instructions for 5+ sources could be split into a separate reference file to keep the main skill leaner. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
1f4becd
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.