CtrlK
BlogDocsLog inGet started
Tessl Logo

bloc-cubit

Use when working with Flutter Bloc/Cubit state management. Covers when to choose Bloc vs Cubit, how to use bloc and flutter_bloc together, lifecycle, testing, and safe defaults.

66

Quality

81%

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

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.

A well-structured, actionable reference of bloc/cubit guidance that assumes Claude's competence and avoids concept padding. It would benefit from a few concrete code snippets and deduplication of the repeated bloc-vs-flutter_bloc rules.

Suggestions

Add one minimal copy-paste Cubit and one Bloc code example to lift actionability from concrete-naming to fully executable.

Collapse the repeated bloc-vs-flutter_bloc dependency guidance (in Core Rule, Required Project Setup, and Minimal Reference Checklist) into a single authoritative section to reduce redundancy.

Provide an explicit decision workflow or numbered sequence (choose → set up deps → implement → lifecycle → bind UI → test) to make the implicit section order an explicit checklist.

DimensionReasoningScore

Conciseness

Mostly lean rules-based guidance with no padding of concepts Claude already knows, but the bloc-vs-flutter_bloc distinction and the closing 'Minimal Reference Checklist' restate points made earlier, so minor trimming is possible.

4 / 5

Actionability

Concrete, specific guidance naming exact widgets and methods (BlocProvider, BlocBuilder, BlocListener, BlocConsumer, BlocSelector, close(), buildWhen, listenWhen) with clear when-to-use rules; lacks code examples, which is acceptable for an instruction-only skill but leaves minor gaps.

4 / 5

Workflow Clarity

Sections are logically ordered (decide Cubit vs Bloc, set up deps, implement pattern, lifecycle, UI binding, testing) with explicit decision criteria; no validation checkpoints, but none are needed since the skill involves no destructive or batch operations.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and no external files needed; the ~100-line body is self-contained and navigable, with minor redundancy between sections preventing a top score.

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.

A concise, well-targeted description that clearly states both what the skill covers and when to invoke it, using natural trigger terms tied to a specific package ecosystem. Minor specificity gains are possible by adding a couple more natural phrasings.

DimensionReasoningScore

Specificity

Names the domain and several concrete capabilities ('when to choose Bloc vs Cubit', 'how to use bloc and flutter_bloc together, lifecycle, testing, and safe defaults'), with only minor gaps in coverage.

4 / 5

Completeness

Explicitly answers 'what' ('Covers when to choose Bloc vs Cubit... lifecycle, testing, and safe defaults') and 'when' ('Use when working with Flutter Bloc/Cubit state management') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Includes natural user-facing terms ('Flutter Bloc/Cubit', 'bloc', 'cubit', 'flutter_bloc', 'state management', 'lifecycle', 'testing'); a few common phrasings like 'flutter state management' are implicit rather than stated.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (the bloc/cubit/flutter_bloc ecosystem) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
andrewyng/context-hub
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.