flow-nexus-platform

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

5.55x

Quality

41%

Does it follow best practices?

Impact

100%

5.55x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/flow-nexus-platform/SKILL.md

Quality

Content

50%

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

This skill is highly actionable with excellent concrete MCP tool call examples throughout, but it is severely bloated — functioning more as a complete platform documentation dump than a focused skill. The lack of validation checkpoints for destructive operations and the monolithic structure significantly reduce its effectiveness. Splitting into a concise overview SKILL.md with separate reference files would dramatically improve token efficiency.

Suggestions

Reduce the SKILL.md to a concise overview (~100-150 lines) covering the most common workflows, and move detailed API references, pricing tiers, categories, tips, and troubleshooting into separate bundle files (e.g., API_REFERENCE.md, PRICING.md, TROUBLESHOOTING.md).

Remove marketing-style content (subscription tier descriptions, 'Ways to Earn', achievement type lists, 'Tips for Success') that doesn't provide actionable guidance Claude needs.

Add explicit validation checkpoints to workflows involving destructive operations — e.g., confirm sandbox status before deletion, verify file existence before storage delete, validate deployment health after template deploy.

Cut redundant patterns — the 'Common Sandbox Patterns' section repeats the sandbox_create call three times with only different package lists, which Claude can infer from a single example.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~700+ lines. Massive amounts of content that could be split into reference files. Includes extensive lists of tips, best practices, categories, pricing tiers, achievement types, and troubleshooting that are informational rather than instructional. Much content (e.g., subscription tier marketing copy, 'Tips for Success', cost optimization tips) doesn't teach Claude how to do anything it couldn't infer.	1 / 3
Actionability	All API calls are shown as concrete, executable MCP tool invocations with realistic parameters. Code examples are copy-paste ready with clear parameter names and values. The Quick Start Guide provides a complete end-to-end workflow with real function calls.	3 / 3
Workflow Clarity	The Quick Start Guide provides a reasonable 5-step sequence, but there are no validation checkpoints or error recovery loops. For destructive operations like sandbox deletion, storage deletion, or app publishing, there are no verification steps. The multi-stage sandbox execution pattern lacks validation between stages.	2 / 3
Progressive Disclosure	Uses HTML details/summary tags for advanced patterns which is a good technique, but the main body is a monolithic wall of content that should be split into separate reference files (e.g., API reference, pricing, challenges). References to external docs exist but the skill itself contains far too much inline content that belongs in supporting files. No bundle files are provided to offload this content.	2 / 3
	Total	8 / 12 Passed

Description

32%

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 identifies a specific platform (Flow Nexus) and lists high-level capability areas, which provides some distinctiveness. However, it lacks concrete action verbs describing what operations are performed, omits a 'Use when...' clause entirely, and uses category labels rather than specific capabilities. The description reads more like a table of contents than actionable guidance for skill selection.

Suggestions

Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user asks about Flow Nexus platform operations, sandbox creation, deploying apps to Flow Nexus, or managing Flow Nexus payments and challenges.'

Replace category labels with concrete actions, e.g., 'Authenticates users, creates and manages sandboxes, deploys applications, processes payments, and configures challenges on the Flow Nexus platform.'

Include natural keyword variations users might say, such as 'login', 'deploy', 'billing', 'sandbox environment', or 'Flow Nexus API'.

Dimension	Reasoning	Score
Specificity	The description names a specific domain ('Flow Nexus platform') and lists several action areas (authentication, sandboxes, app deployment, payments, challenges), but these are category labels rather than concrete actions. It doesn't describe what specific operations are performed (e.g., 'create sandboxes', 'deploy apps', 'process payments').	2 / 3
Completeness	The description answers 'what' at a high level (platform management across several areas) but completely lacks any 'when' guidance — there is no 'Use when...' clause or equivalent explicit trigger guidance. Per the rubric, a missing 'Use when' clause should cap completeness at 2, and since the 'what' is also only surface-level, a score of 1 is appropriate.	1 / 3
Trigger Term Quality	It includes some relevant keywords like 'authentication', 'sandboxes', 'app deployment', 'payments', and 'challenges' that users might mention, but 'Flow Nexus' is a specific platform name that helps. However, it lacks common variations or natural phrasing users might use (e.g., 'login', 'deploy', 'billing', 'sandbox environment').	2 / 3
Distinctiveness Conflict Risk	The mention of 'Flow Nexus platform' provides some distinctiveness since it's a specific platform name. However, broad terms like 'authentication', 'payments', and 'app deployment' could overlap with other skills that handle those domains in different contexts.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: ruvnet/ruvector
Commit: 6d2da75

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