CtrlK
BlogDocsLog inGet started
Tessl Logo

flutter-animating-apps

Implement animated effects, transitions, and motion in Flutter apps. Useful for native iOS/Android motion design.

56

Quality

64%

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-animating-apps/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The body is a concise, well-organized catalogue entry that points to an upstream bundle rather than containing its own instructions. Its main weakness is actionability: it offers no concrete executable steps, relying entirely on an external repository.

Suggestions

Replace the abstract 'install the upstream bundle into your active agent's skills directory' with concrete, copy-paste-ready commands (e.g., git clone target path) so the action is executable.

Add a short inline quick-start example (e.g., a minimal Flutter animation snippet) so the skill provides value even before the upstream bundle is installed.

Include a verification step (e.g., how to confirm the skill was installed and is invokable) to add a validation checkpoint to the workflow.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it does not explain what Flutter or animation is, and every line earns its place with no padding.

3 / 3

Actionability

Guidance is abstract rather than executable: 'Inspect the upstream README for exact paths' and 'ask the agent to invoke this skill by name' with no concrete code, commands, or install steps.

1 / 3

Workflow Clarity

It gestures at a sequence ('install the upstream bundle... then ask the agent to invoke this skill') but provides no actual sequenced steps or validation checkpoints, so the workflow is present only implicitly.

2 / 3

Progressive Disclosure

Under 50 lines with a single clear purpose and well-organized sections (What it does, Source, How to use); per the simple-skills note this can score 3 without external file references.

3 / 3

Total

9

/

12

Passed

Description

72%

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 specific to the Flutter animation niche with natural trigger terms, but it lacks an explicit 'Use when...' clause, which caps its completeness. It is concise and distinct but not fully actionable as a trigger specification.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggering situations (e.g., 'Use when the user asks for Flutter animations, screen transitions, or native iOS/Android motion design').

Expand the capability list with a few concrete actions (e.g., 'build explicit/implicit animations, hero transitions, staggered motion') to lift specificity from 2 to 3.

DimensionReasoningScore

Specificity

The description names the domain ('animated effects, transitions, and motion in Flutter apps') and a few actions, but it does not list multiple specific concrete actions like the score-3 anchor; it stops at a general capability statement.

2 / 3

Completeness

It states what the skill does but has no explicit 'Use when...' trigger clause; per the guidelines, a missing explicit trigger guidance caps completeness at 2.

2 / 3

Trigger Term Quality

The frontmatter triggers ('flutter animation', 'flutter motion', 'mobile animation', 'flutter transitions') are natural phrases a user would actually say, with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Flutter-specific niche and distinct Flutter/motion triggers make it clearly distinguishable and unlikely to fire for the wrong skill.

3 / 3

Total

10

/

12

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.