cerebro-rust-migration

Work on the Go-to-Rust migration - porting compatibility callers, family authority promotion, parity evidence, or Rust read API capabilities.

Quality

72%

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 ./.claude/skills/cerebro-rust-migration/SKILL.md

Quality

Content

82%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 tight, actionable, well-structured migration guide with concrete commands and validation guidance, succeeding as an instruction-only skill. The main gap is an explicit validate→fix→retry loop within the porting workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — invariants, numbered steps, and make targets with no padding or explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Concrete executable commands ("make fixture-oracle-generate", "make projection-parity-test", "make rust-fmt-check rust-clippy rust-test", "cerebro-platform evaluate-family") with specific CLI steps, but no complete copy-paste walkthrough leaves minor gaps.	4 / 5
Workflow Clarity	The "Porting a compatibility caller" section is a clear numbered sequence and validation is present (parity tests, "fails closed" invariants, "make changed-check"), so the destructive-operation cap does not apply; a fully explicit validate→fix→retry loop inside the porting steps would reach 5.	4 / 5
Progressive Disclosure	Sections are well-organized and two external docs are referenced one level deep with clear signaling of their contents ("authority model, compatibility port...", "sequencing and capability gaps"); no bundle files exist, and most project detail is inlined rather than split out, keeping it just below 5.	4 / 5
	Total	17 / 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.

The description is specific and clearly distinct within its niche, but relies on project-internal jargon and lacks an explicit "Use when..." trigger clause, capping completeness and trigger quality.

Suggestions

Add an explicit "Use when..." clause naming the natural user requests that should activate this skill (e.g. "Use when porting a Go compatibility caller to Rust or promoting a family's authority").

Soften project jargon with natural synonyms so the description matches phrasings a user would actually say.

Include concrete trigger terms such as "port to Rust", "migrate caller", or "authority promotion" alongside the existing domain language.

Dimension	Reasoning	Score
Specificity	"porting compatibility callers, family authority promotion, parity evidence, or Rust read API capabilities" lists several specific concrete actions, though each is framed in project-internal jargon leaving minor coverage gaps.	4 / 5
Completeness	The description gives a clear "what" (the four migration activities) but has no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Terms like "Go-to-Rust migration" and "Rust read API" are relevant but project-jargon-heavy, missing the natural phrasings and synonyms a user would actually say.	3 / 5
Distinctiveness Conflict Risk	"Go-to-Rust migration" with family-authority promotion and parity evidence is a clear, narrow niche with distinct triggers and minimal conflict risk.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: writer/cerebro
Path: .claude/skills/cerebro-rust-migration/SKILL.md
Commit: ce4230a

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