Name: rust-daily
Rating: 64.8 (1 reviews)
Author: actionbook

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

Quality

81%

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

75%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.

The body is a well-structured, actionable reference for a multi-source aggregation skill, with concrete commands and explicit validation/error handling. The main gaps are minor redundancy between the inline and tool-chain sections and a few non-executable placeholders.

Suggestions

Resolve the '<selector_from_actionbook>' and '<agent content>' placeholders with concrete fallbacks so the commands are fully copy-paste ready.

Consolidate the inline per-source tool examples with the 'Tool Chain Priority' table to remove the duplicated agent-browser/WebFetch guidance.

Move the 'Version / Last Updated' stamp into a changelog or deprecated-patterns section so time-sensitive tokens don't compete with the live instructions.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean tables and commands with no padding about what Rust/Reddit are, but the 'Tool Chain Priority' section partly duplicates the inline commands and the 'Last Updated: 2025-01-27' version stamp is time-sensitive content outside a deprecated section.	4 / 5
Actionability	It provides concrete, executable commands (agent-browser, mcp__actionbook, WebFetch) and an output template, but placeholders like '<selector_from_actionbook>' and '<agent content>' keep it just short of fully copy-paste ready.	4 / 5
Workflow Clarity	Mode detection, the two workflows, time-filtering, and a Validation/Error-Handling section give a clear sequence with retry/fallback checkpoints for this batch fetch; it stops short of a 5 because the per-source feedback loop is described tersely rather than as an explicit checklist.	4 / 5
Progressive Disclosure	Content is well organized under clear section headers with a clearly signaled one-level-deep external reference (../../agents/rust-daily-reporter.md) and no nested refs; with no bundle files present and the skill over 50 lines, it is good but not a fully split 5.	4 / 5
	Total	16 / 20 Passed

Description

81%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.

The description has excellent trigger-term coverage and a distinct niche, with an explicit 'when' clause. Its main weakness is a 'what' that names the domain and output type but omits concrete action verbs, leaving the capability slightly underspecified.

Suggestions

Add an explicit action verb to the 'what', e.g. 'Fetches and aggregates Rust community news into daily/weekly/monthly reports.'

Lead with the capability statement before the trigger list so the 'what' is as strong as the 'when'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Rust news') and a concrete deliverable type ('daily/weekly/monthly reports'), but lacks explicit action verbs like fetch, aggregate, or compile, so it sits at 'names domain and 1-2 concrete actions' rather than comprehensive.	3 / 5
Completeness	Both 'what' (Rust news and reports) and 'when' ('Use for... Triggers on...') are present, with the when being explicit and specific; the what could be more explicit about the concrete action, keeping it just below a 5.	4 / 5
Trigger Term Quality	It lists comprehensive natural trigger terms including synonyms and abbreviations ('rust news, rust daily, rust weekly, TWIR, rust blog') plus Chinese variants ('Rust 日报, Rust 周报'), covering exactly what a user would say.	5 / 5
Distinctiveness Conflict Risk	It carves a clear niche (Rust community news aggregation) with distinct, specific triggers (TWIR, rust daily/weekly) and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: actionbook/rust-skills
Path: skills/rust-daily/SKILL.md
Commit: 5c40d3a

Reviewed: 14 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.