rust-port-status

Show the status of all Rust port plan documents and recent related commits. Use when you need to understand what's been done vs what remains.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./compiler/.claude/skills/rust-port-status/SKILL.md

Quality

Content

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

A lean, well-structured instruction body with concrete executable git commands and a clear numbered workflow. The only notable weakness is an unspecified '<key phrase>' placeholder in the per-document git log grep, which leaves a small ambiguity in an otherwise copy-paste-ready skill.

Suggestions

Replace the '<key phrase>' placeholder with a concrete derivation, e.g. 'grep the doc's slug (e.g. rust-port-0001) from its filename', so every command is copy-paste ready.

Specify where the status line lives (e.g. a 'Status:' line under the first heading) and what statuses to expect, removing ambiguity in the per-doc extraction step.

Dimension	Reasoning	Score
Conciseness	The ~20-line body is lean and efficient: it assumes Claude's competence (no explanation of git or markdown), contains zero padding, and every instruction adds information, matching the lean-and-efficient top anchor.	5 / 5
Actionability	Concrete, executable commands are given for the git steps ('git log --oneline --grep="rust-compiler" -10') plus an exact directory path, but 'git log --oneline --grep="<key phrase>"' leaves an unspecified placeholder Claude must infer, a minor gap below the copy-paste-ready top anchor.	4 / 5
Workflow Clarity	A clear, well-sequenced 4-step numbered workflow with concrete sub-steps; as a read-only reporting skill it needs no validation checkpoints. It falls just short of unambiguous because the grep '<key phrase>' and how to surface the status line ('if present') are left slightly underspecified.	4 / 5
Progressive Disclosure	This is a simple, single-purpose skill under 50 lines with no need for external reference files; the body is well-organized with a title, brief summary, and an Instructions section, which per the simple-skills note earns the top score with no unnecessary indirection.	5 / 5
	Total	18 / 20 Passed

Description

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

A concise, third-person description with an explicit 'Use when' clause and a clearly distinct niche. It is held back by limited action specificity and thin trigger-term coverage — natural synonyms like 'progress' or 'remaining work' are absent.

Suggestions

List the concrete actions performed (e.g., 'Lists each plan document, its title, status, and remaining work; shows a summary table and the 10 most recent [rust-compiler] commits') to raise specificity.

Add natural trigger variations users would say, such as 'porting progress', 'remaining work', or 'what's left on the Rust port', to broaden trigger coverage.

Sharpen the 'when' clause with more concrete trigger conditions, e.g. 'Use when asked about Rust port progress, remaining work, or recent port commits.'

Dimension	Reasoning	Score
Specificity	The description names its domain ("Rust port plan documents") and 1-2 concrete actions ("Show the status of..." and "recent related commits"), but stops short of the several-specific-actions level — it never mentions listing plan docs, showing titles, or a summary table.	3 / 5
Completeness	Both what ("Show the status of all Rust port plan documents and recent related commits") and when ("Use when you need to understand what's been done vs what remains") are present. Not 5: the when clause is a single somewhat generic trigger rather than the multiple concrete trigger phrases of the top anchor; not 3 because the when is explicit, not merely implied.	4 / 5
Trigger Term Quality	Phrases like "Rust port", "plan documents", and "what's been done vs what remains" are relevant, but common natural variations users would say — "porting progress", "remaining work", "port status" — are missing, matching the some-keywords-but-missing-synonyms anchor.	3 / 5
Distinctiveness Conflict Risk	The "Rust port" niche is distinct with clear triggers, but "recent related commits" and "what's been done" could cause minor overlap with general git-log or commit-review skills, matching the mostly-distinct anchor rather than the minimal-conflict top anchor.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: facebook/react
Path: compiler/.claude/skills/rust-port-status/SKILL.md
Commit: 7c6ac13

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