CtrlK
BlogDocsLog inGet started
Tessl Logo

flutter-bloc-forms

Use when managing complex form state, synchronous and asynchronous input validation, or form submission transitions in BLoC.

65

Quality

78%

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 ./skills/flutter/flutter-bloc-forms/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A tight, well-structured prescriptive reference that earns top conciseness marks and gives concrete, actionable Flutter/BLoC guidance; the main gap is one non-executable code snippet that keeps actionability just short of full marks.

Suggestions

Replace the `sealed class FormStatus { ... }` snippet with valid Dart (e.g. `sealed class FormStatus {}; final class FormInitial extends FormStatus {}`) or label it as illustrative.

Add one short end-to-end FormBloc wiring example (events → states → submit handler) so the lifecycle sections connect into a runnable whole.

If the Common Form Patterns section grows, move multi-step and dependent-field recipes into a referenced file to preserve the lean overview.

DimensionReasoningScore

Conciseness

Lean bullet-list of prescriptive rules with no padding and no explanation of concepts Claude already knows (BLoC, Flutter, TextFormField); every line is actionable guidance.

5 / 5

Actionability

Highly concrete guidance with specific APIs (FilteringTextInputFormatter.digitsOnly, AutofillHints, debounce 300-500ms) and a valid validator snippet, but the `sealed class FormStatus { initial, submitting, success, failure }` example is not valid Dart and is illustrative rather than copy-paste ready.

4 / 5

Workflow Clarity

Content is organized along the form lifecycle (architecture → events → state → validation → widgets → lifecycle → submission → patterns) with a clear submission sequence; no validation checkpoints are needed since there are no destructive or batch operations.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections and appropriately self-contained for a prescriptive rule set with no external references, though it sits just over the 50-line simple-skill threshold and could split the larger pattern sections if it grows.

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.

A solid, mostly specific description that names the BLoC niche and provides an explicit trigger clause; it would reach the top level by splitting a standalone capability statement out from the "Use when" phrasing and adding a couple of natural synonyms.

Suggestions

Lead with a short capability statement before the trigger (e.g. "Architects Flutter forms with BLoC: state, validation, and submission. Use when...") so "what" and "when" are both explicit.

Add natural synonyms a user might say, such as "Flutter forms" or "form handling", to broaden trigger coverage.

Mention the multi-step and dependent-field patterns in the description to better signal breadth.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — "managing complex form state", "synchronous and asynchronous input validation", and "form submission transitions" — with only minor gaps (e.g. input widgets/controller lifecycle are in the body, not the description).

4 / 5

Completeness

Has an explicit "Use when..." trigger clause and embeds the "what" (form state, validation, submission transitions) inside it, but the capability statement is not separated out as plainly as the anchor-5 example.

4 / 5

Trigger Term Quality

Good coverage of natural terms a Flutter developer would say ("form state", "input validation", "form submission", "BLoC"), though a few natural synonyms like "Flutter forms" or "form handling" are missing.

4 / 5

Distinctiveness Conflict Risk

The "in BLoC" qualifier carves a clear niche within Flutter state management, leaving only minor overlap risk with general Flutter form or Riverpod/Provider skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
dhruvanbhalara/skills
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.