CtrlK
BlogDocsLog inGet started
Tessl Logo

frb-manual-test

Use when adding, executing, reviewing, or updating flutter_rust_bridge manual test reports under tools/manual_tests for scenarios that require human or agent-driven manual verification.

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/frb-manual-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 highly actionable with concrete commands, clear sequencing, and explicit validation gates. It loses points on conciseness due to repetition in the gist-upload section and on progressive disclosure because the referenced template files are not verifiable in the provided bundle.

Suggestions

Consolidate the repeated gist-upload instructions in the Reviewable Workflow Gate into a single definitive statement to reduce redundancy.

Ensure the referenced bundle files (test-template.md, execution-template.md) are present in the skill bundle so the one-level-deep references resolve.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and templates, but sections like the Reviewable Workflow Gate repeat the gist-upload requirement across multiple numbered steps and paragraphs, adding padding that could be tightened.

3 / 5

Actionability

Provides copy-paste ready commands (cp of templates), concrete artifact paths, exact evidence fields to capture, and specific examples of pass indicators like 'All tests passed!' — fully executable guidance covering common cases.

5 / 5

Workflow Clarity

Add and Execute sections are clearly sequenced, the Reviewable Workflow Gate is a 7-step numbered checklist, and it includes a validation/feedback loop ('report blocked until gist can be created') with explicit completion criteria.

5 / 5

Progressive Disclosure

References two real bundled templates (test-template.md, execution-template.md) as the source of truth one level deep, but the bundle files are not present in ./references, ./scripts, or ./assets to verify, and detailed report shape is delegated to the template rather than inlined appropriately.

4 / 5

Total

17

/

20

Passed

Description

75%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 third-person, includes an explicit 'Use when' trigger, and names a clear niche with several concrete actions. It is strong but stops short of comprehensive trigger-term coverage and fully explicit 'when' guidance.

Suggestions

Add common-sense trigger synonyms (e.g., 'manual QA', 'human verification', 'release checklist') so users searching with those phrasings surface the skill.

Tighten the 'when' clause with a few concrete example scenarios (e.g., 'when automated tests are unavailable or cannot exercise UI/device/release flows').

DimensionReasoningScore

Specificity

Lists several concrete actions — 'adding, executing, reviewing, or updating' — and a specific scope ('tools/manual_tests'), with only minor gaps in coverage of all manual-test lifecycle tasks.

4 / 5

Completeness

It has an explicit 'Use when...' trigger clause and a clear 'what' (adding, executing, reviewing, updating manual test reports), but the 'when' could be more concrete about the exact situations beyond 'scenarios that require human or agent-driven manual verification'.

4 / 5

Trigger Term Quality

Natural triggers like 'manual test reports' and 'manual verification' are present, but common variations such as 'manual QA', 'human verification', or 'checklist' are missing, leaving a few natural terms out.

4 / 5

Distinctiveness Conflict Risk

The 'flutter_rust_bridge manual test reports under tools/manual_tests' niche is mostly distinct with a clear trigger, with only minor overlap risk against a general testing skill.

4 / 5

Total

16

/

20

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.