rust-daily

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 动态

Install with Tessl CLI

npx tessl i github:actionbook/rust-skills --skill rust-daily

What are skills?

Review — 54%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 12 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

44%

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 terms and distinctiveness with excellent keyword coverage in multiple languages, but critically fails to explain what the skill actually does. It tells Claude when to use it but not what capabilities it provides, making it incomplete despite strong selection triggers.

Suggestions

Add specific actions the skill performs, e.g., 'Fetches and summarizes Rust ecosystem news, compiles daily/weekly reports from sources like This Week in Rust'

Include a 'Use when...' clause that combines the triggers with the capability, e.g., 'Use when users want to stay updated on Rust developments or need curated Rust news summaries'

Specify output formats or sources if relevant, e.g., 'aggregates from official Rust blog, TWIR, and community sources'

Dimension	Reasoning	Score
Specificity	The description mentions 'news and daily/weekly/monthly reports' but provides no concrete actions - it doesn't explain what the skill actually does (fetch, summarize, compile, analyze?). Very vague about capabilities.	1 / 3
Completeness	While it has strong 'when' triggers, the 'what' is almost entirely missing. We know it's for Rust news but not what actions it performs - does it fetch, summarize, generate, or aggregate? The core capability is undefined.	1 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms including 'rust news', 'rust daily', 'rust weekly', 'TWIR', 'rust blog' plus Chinese equivalents like '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 triggers like 'TWIR' (This Week in Rust) and Chinese terms make it highly distinctive and unlikely to conflict with other skills.	3 / 3
	Total	8 / 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 alternatives. However, it suffers from some redundancy between sections and lacks robust validation checkpoints for a multi-source fetching workflow. The dual-mode structure adds complexity that could be better organized through progressive disclosure.

Suggestions

Add explicit validation checkpoints after each source fetch (e.g., 'Verify at least 1 result before proceeding to next source')

Consolidate the tool chain priority information to avoid repetition with the inline mode section

Consider moving detailed per-source fetch instructions to a separate SOURCES.md file, keeping SKILL.md as a concise overview

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes some redundancy - the tool chain priority section repeats information already shown 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 bash examples and WebFetch calls are copy-paste ready with clear parameters.	3 / 3
Workflow Clarity	Steps are listed with clear sequence for each source, but validation is limited to a brief section at the end. Missing explicit checkpoints between fetching sources and no feedback loop for retry logic beyond 'retry once, then skip'.	2 / 3
Progressive Disclosure	Content is reasonably structured with clear sections, but everything is inline in one file. The reference to an external agent file is good, but the inline mode section is quite long and could benefit from splitting detailed source instructions into separate files.	2 / 3
	Total	9 / 12 Passed

Validation

75%

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 — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	12 / 16 Passed

Reviewed: 23 days 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.