flow-nexus-platform

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

5.55x

Quality

61%

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

65%

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

The content is highly actionable, packed with executable MCP calls and parameters, but it is a very long monolithic inline reference that should be split into per-domain reference files, and its destructive/batch workflows lack validation checkpoints. Tightening prose and adding verification steps would address the weakest dimensions.

Suggestions

Split each domain (Authentication, Sandbox, App Store, Payments, Challenges, Storage, System) into a separate reference file linked from a concise SKILL.md overview to improve progressive disclosure.

Add explicit validate-then-proceed steps for destructive and batch operations (e.g. sandbox_status before sandbox_delete; confirm deletion of non-temp files) to raise workflow clarity.

Trim tangential prose such as the RuVector "Self-Learning Intelligence" hook details and the Queen Seraphina capability bullet list, which do not advance the task instructions.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely concrete code rather than concepts Claude already knows, but at ~1175 lines it is a monolithic inline API reference that could be tightened and partly externalized; tangential prose ("Self-Learning Intelligence", Queen Seraphina capability bullets) adds unnecessary tokens.	2 / 3
Actionability	Every section provides complete, copy-paste-ready MCP calls with full parameter objects and inline comments, matching the level-3 anchor for fully executable guidance.	3 / 3
Workflow Clarity	The Quick Start Guide sequences five steps, but destructive and batch operations (sandbox_delete, storage_delete, batch uploads) have no validation or verification checkpoints, which caps workflow clarity at 2 per the rubric guidelines.	2 / 3
Progressive Disclosure	There are no bundle files; the per-domain API reference is inlined in one giant file rather than split across reference files, though the collapsible <details> "Progressive Disclosure" section and a table of contents provide some organization.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 names the Flow Nexus domain and enumerates its capability areas, giving it strong distinctiveness, but it relies on area nouns rather than concrete actions and lacks an explicit "Use when..." trigger clause. Adding a trigger clause and more natural user-facing verbs would raise the lower-scoring dimensions.

Suggestions

Append an explicit "Use when..." clause, e.g. "Use when the user asks to manage Flow Nexus authentication, sandboxes, app deployment, credits, or coding challenges."

Rephrase capability areas as concrete verb-actions (e.g. "register and log in users, create and run sandboxes, deploy apps, manage credits, and submit challenges") to lift specificity from 2 to 3.

Add natural trigger synonyms users would actually say ("deploy", "billing/credits", "leaderboards") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes "authentication, sandboxes, app deployment, payments, and challenges" name the domain and several sub-areas, but these are noun-phrase capability areas rather than the concrete verb-actions (e.g. "extract text, fill forms") that the level-3 anchor requires.	2 / 3
Completeness	The description states what the skill does but omits any "Use when..." clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Terms like "Flow Nexus platform", "sandboxes", and "app deployment" are relevant to the product but miss common variations a user might say ("deploy", "credits", "billing") and include no natural trigger phrasing, matching the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The skill is tightly scoped to the Flow Nexus platform with distinct product-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 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: 6a6c39e

Reviewed: about 13 hours 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.