frb-cargokit

Explain how cargokit is sourced, copied, and analyzed inside flutter_rust_bridge. Use when working on `integration_template/**/cargokit`, `frb_example/**/cargokit`, integrate/generate output drift, or any diff that mentions cargokit and you need to identify the true source of truth before judging the change.

Quality

81%

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

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 content is well-structured, domain-specific, and actionable with concrete commands and a clear diff-analysis sequence plus a sync feedback loop. It is held at 4 across dimensions by minor over-explanation, interpretive analysis steps, and slight section overlap rather than any real deficiency.

Suggestions

Tighten the Mental Model paragraph so the 'large cargokit diff' restatement is a single sentence instead of two, removing the only padding in an otherwise lean body.

Add an explicit validation checkpoint to the Diff Analysis Order (e.g. 'Confirm the copied files match the submodule SHA before judging them as local edits') to lift workflow clarity toward 5.

Merge or cross-reference 'What To Say Explicitly' and 'Common Mistakes' since both cover the same layer-confusion failure mode, reducing structural overlap.

Dimension	Reasoning	Score
Conciseness	The body is sectioned and lean with domain-specific (not generic) explanation, but a few sentences restate the propagation point (e.g. the 'large cargokit diff ... may only mean a template or submodule change' pair), matching 'efficient with minor instances of over-explanation' rather than the every-token-earns-its-place anchor 5.	4 / 5
Actionability	It gives concrete executable commands ("./frb_internal sync-cargokit-copies", "./frb_internal generate-internal --set-exit-if-changed --coverage") and exact source-of-truth paths, but some diff-analysis steps are interpretive ("Compare the old and new submodule SHAs") without a copy-paste command, fitting anchor 4.	4 / 5
Workflow Clarity	The 'Diff Analysis Order' is a clear 4-step sequence and the sync section includes a feedback loop (drift -> fix source -> re-sync -> commit) with a CI diff-gate checkpoint, but the primary analysis workflow lacks explicit validation checkpoints, so anchor 4 fits better than 5.	4 / 5
Progressive Disclosure	No bundle files exist; the body is well-sectioned and points one level deep to sibling skills (frb-code-generation, frb-debugging) in the Scope Boundary, giving good structure with minor organization overlap between 'What To Say Explicitly' and 'Common Mistakes', matching anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

87%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 strong: it names concrete actions, provides an explicit 'Use when...' trigger with path globs and scenario terms, and is tightly scoped to a distinct niche. Minor gaps in keyword synonyms keep trigger quality and specificity at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	"Explain how cargokit is sourced, copied, and analyzed" lists three concrete actions (sourced, copied, analyzed) with minor coverage gaps, matching the 'several specific actions' anchor rather than the comprehensive anchor 5.	4 / 5
Completeness	It states the 'what' ("Explain how cargokit is sourced, copied, and analyzed inside flutter_rust_bridge") and an explicit 'Use when...' clause with concrete trigger phrases, matching the anchor for clearly answering both what and when.	5 / 5
Trigger Term Quality	Includes natural domain triggers like "integrate/generate output drift", "diff that mentions cargokit", and cargokit path globs, giving good keyword coverage with a few natural variations (e.g. rust_builder/cargokit, submodule) missing, so anchor 4 fits better than 5.	4 / 5
Distinctiveness Conflict Risk	The niche is tightly scoped to cargokit within flutter_rust_bridge with path-specific triggers, giving a clear niche with distinct triggers and minimal conflict risk.	5 / 5
	Total	18 / 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: fzyzcjy/flutter_rust_bridge
Path: .claude/skills/frb-cargokit/SKILL.md
Commit: 8f2ab1b

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