CtrlK
BlogDocsLog inGet started
Tessl Logo

flow-nexus-platform

Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges

75

1.95x
Quality

66%

Does it follow best practices?

Impact

94%

1.95x

Average score across 3 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/flow-nexus-platform/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The skill is highly actionable — packed with executable, parameterized code examples — but it is a monolithic ~1100-line inline reference that could be split into bundle files, and its destructive/batch workflows lack validation checkpoints. Quick Start sequencing helps but does not fully compensate.

Suggestions

Move the per-section API reference into separate reference files under ./references/ and keep SKILL.md as a concise overview with one-level-deep links, leveraging the existing <details> pattern.

Add explicit validation/verification steps for destructive and batch operations (e.g., confirm sandbox_id via sandbox_status before sandbox_delete; verify upload via storage_get_url).

Remove the redundant Quick Start Guide or replace it with a brief pointer, since its steps duplicate the detailed sections above.

DimensionReasoningScore

Conciseness

The ~1100-line body is mostly copy-paste code blocks rather than concept prose, but the exhaustive inline API catalog and a duplicated Quick Start section make it far longer than necessary and easily tightened or split.

2 / 3

Actionability

Nearly every operation ships with a complete, parameterized code example that is copy-paste ready, e.g. sandbox_create with template, env_vars, install_packages, and timeout.

3 / 3

Workflow Clarity

The Quick Start Guide sequences Steps 1-5, but destructive and batch operations (sandbox_delete, storage_delete, app_store_publish_app) lack validation or verification checkpoints, capping this at 2.

2 / 3

Progressive Disclosure

Content is organized with a TOC and collapsible <details> advanced sections, but the entire API reference is inline in SKILL.md with no separate bundle/reference files, so material that should be split out is monolithic.

2 / 3

Total

9

/

12

Passed

Description

67%

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 clearly scopes the skill to the Flow Nexus platform and lists several concrete capability areas, giving it good distinctiveness and specificity. Its main weakness is the missing explicit 'when to use' trigger clause, which caps completeness at 2.

Suggestions

Append an explicit 'Use when...' clause (e.g., 'Use when managing Flow Nexus authentication, sandboxes, deployments, payments, or coding challenges').

Add natural user phrasings alongside the platform jargon so trigger terms match what a user would actually say.

Consider phrasing the capabilities as actions (e.g., 'authenticates users, creates sandboxes, deploys apps') rather than a noun list.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capability areas ('authentication, sandboxes, app deployment, payments, and challenges'), naming specific sub-domains rather than abstract actions.

3 / 3

Completeness

It states what the skill does ('Comprehensive Flow Nexus platform management' plus listed areas) but provides no 'Use when...' clause or explicit trigger guidance, so the 'when' half is only implied.

2 / 3

Trigger Term Quality

Terms like 'authentication, sandboxes, app deployment, payments, challenges' are relevant domain keywords, but they read as platform jargon and miss natural user phrasings and common variations.

2 / 3

Distinctiveness Conflict Risk

Tying the description to the named 'Flow Nexus' platform gives it a clear niche with distinct triggers, making it unlikely to fire for the wrong skill.

3 / 3

Total

10

/

12

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

skill_md_line_count

SKILL.md is long (1158 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
ruvnet/agentic-flow
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.