CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction-only skill that delivers concrete FRB-specific judgment logic, a sequenced diff-analysis workflow with checkpoints, and lean prose throughout. The absence of code is appropriate and not penalized given the actionable guidance.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains basic concepts (submodules, flutter_rust_bridge) and every section earns its place, with little to trim.

3 / 3

Actionability

For an instruction-only skill it gives concrete executable commands ('./frb_internal sync-cargokit-copies', 'generate-internal --set-exit-if-changed --coverage') and exact source-of-truth path globs, not vague direction.

3 / 3

Workflow Clarity

The 'Diff Analysis Order' is an explicit numbered sequence with gating checkpoints ('Compare the SHAs... before saying anything', 'Only then inspect copied files') and a fix→sync→commit feedback loop for drift.

3 / 3

Progressive Disclosure

With no bundle files present, the body is a single-level, well-sectioned document with clear header navigation and no monolithic wall of text or nested references.

3 / 3

Total

12

/

12

Passed

Description

100%

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 tight, domain-specific description that names concrete actions, gives explicit Use-when triggers, and is clearly distinguishable from sibling skills. It satisfies all four dimensions without padding.

DimensionReasoningScore

Specificity

The description lists three concrete actions — 'sourced, copied, and analyzed' — rather than naming only the domain, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It explicitly answers both what ('Explain how cargokit is sourced, copied, and analyzed') and when via an explicit 'Use when...' clause, satisfying the completeness bar.

3 / 3

Trigger Term Quality

It provides natural trigger phrases a developer would say ('cargokit', 'diff that mentions cargokit', 'integrate/generate output drift', specific path globs), giving good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

The niche is narrowly scoped to cargokit inside flutter_rust_bridge with specific path globs and a source-of-truth framing, making a wrong-skill trigger unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fzyzcjy/flutter_rust_bridge
Reviewed

Table of Contents

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.