flow-nexus-platform

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

5.55x

Quality

55%

Does it follow best practices?

Impact

100%

5.55x

Average score across 3 eval scenarios

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

57%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 complete copy-paste MCP examples and a clear Quick Start, but it is a monolithic ~1175-line reference dump that buries API, pricing, and guidance material in a single file. Workflows lack validation checkpoints for destructive operations, and progressive disclosure is undermined by the absence of any bundle/reference files.

Suggestions

Move the bulk API reference, pricing/subscription tiers, achievement types, and troubleshooting into separate reference files (e.g. reference/api.md, reference/payments.md) and link to them from SKILL.md, keeping only a concise overview and Quick Start inline.

Add explicit validation checkpoints to the Quick Start and to destructive flows (e.g. after sandbox_create verify sandbox_status is 'running' before executing code; confirm auth_status before billing steps).

Trim padded advisory sections (tips-for-success, best-practices, revenue-sharing prose) that restate what the tool examples already imply, to reduce token cost.

Dimension	Reasoning	Score
Conciseness	The ~1175-line body inlines an entire API catalog plus pricing tables, subscription tiers, achievement types, tips-for-success, best-practices, and troubleshooting sections that are padded reference material Claude does not need in context.	2 / 5
Actionability	Provides copy-paste-ready MCP tool invocations with full parameters for every feature, and a Quick Start Guide with concrete examples covering the common onboarding cases.	5 / 5
Workflow Clarity	The Quick Start offers a numbered 5-step sequence, but it lacks validation checkpoints, and destructive operations (sandbox_delete, storage_delete) appear as standalone calls with no validate-then-proceed feedback loops, capping the score at 3.	3 / 5
Progressive Disclosure	A Table of Contents, section headers, and collapsible <details> blocks provide some structure, but no bundle files exist and the full API reference plus supporting material is inlined in SKILL.md rather than split into one-level-deep references.	3 / 5
	Total	13 / 20 Passed

Description

53%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 clearly identifies the platform and its feature areas but stops short of concrete actions and omits any 'when to use' trigger guidance. It is reasonably distinct thanks to the named platform, yet reads more as a feature catalog than an action-oriented trigger.

Suggestions

Replace the generic 'management' framing with concrete verbs, e.g. 'Create and configure sandboxes, deploy apps, manage credits and payments, and submit coding challenges on the Flow Nexus platform.'

Add an explicit trigger clause: 'Use when the user wants to manage Flow Nexus sandboxes, deploy apps, handle credits/payments, or complete challenges.'

Drop the vague filler word 'Comprehensive' and include natural synonyms/extensions users might say (e.g. 'Flow Nexus API', 'rUv credits', 'sandboxes').

Dimension	Reasoning	Score
Specificity	Names the domain ('Flow Nexus platform management') and several feature areas ('authentication, sandboxes, app deployment, payments, and challenges'), but leads with the generic verb 'management' and a noun list rather than concrete actions; 'Comprehensive' is vague filler.	3 / 5
Completeness	Clearly states what the skill covers, but provides no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Contains relevant domain keywords (sandboxes, app deployment, payments, challenges) but lacks synonyms, natural phrasing variations, or file extensions users might say.	3 / 5
Distinctiveness Conflict Risk	Anchored to a named proprietary platform ('Flow Nexus'), making it mostly distinct; minor overlap risk remains from generic terms like 'authentication' and 'payments'.	4 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1176 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/RuVector
Path: .claude/skills/flow-nexus-platform/SKILL.md
Commit: 14db7a3

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.