flow-nexus-platform

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

2.04x

Quality

—

Does it follow best practices?

Impact

94%

2.04x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

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 body is a comprehensive, highly actionable API reference with strong code examples and a useful quick-start sequence, but it is monolithic and verbose, mixing overview, full reference, pricing, and advice into one file without external bundle files or validation checkpoints. Its strongest dimension is actionability; its weakest are conciseness and progressive disclosure.

Suggestions

Split the full API reference into bundle files (e.g. references/sandboxes.md, references/payments.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links, to improve progressive disclosure and conciseness.

Add explicit validation/verification checkpoints to destructive and batch workflows (e.g. confirm sandbox_id before sandbox_delete, verify balance/threshold after configure_auto_refill) so workflow clarity can reach the top anchor.

Trim sections that restate platform knowledge Claude already has (subscription tier features, generic cost-optimization and "Tips for Success" lists) to recover token budget.

Dimension	Reasoning	Score
Conciseness	The body is an ~1150-line reference that restates every MCP tool signature with explanatory category lists, subscription tiers, cost tips, and generic "Tips for Success" prose; it is accurate but padded with content Claude largely already infers and could be tightened substantially. It does not reach the top anchor's lean, every-token-earns-its-place bar.	2 / 3
Actionability	It provides numerous concrete, copy-paste-ready code examples with full parameter objects and inline comments (e.g. sandbox_create, user_register, template_deploy), matching the top anchor for fully executable, specific examples.	3 / 3
Workflow Clarity	A sequenced Quick Start Guide (Steps 1-5) gives a clear path, but workflows involving destructive or batch operations (sandbox_delete, storage_delete, app_store_publish_app, payments/auto-refill) lack explicit validation checkpoints and fix-retry feedback loops, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist, so there are no real one-level-deep reference files; the bulk of the API reference is inline in SKILL.md with only collapsible <details> blocks for advanced patterns. Sections and a table of contents provide organization, but content that should be split into separate reference files is monolithic.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 a competent one-liner that names the platform and its main subsystems, but it stays at the category level, omits any explicit use-when trigger clause, and uses branded-but-broad terms. It reads as a tagline rather than a precise trigger description.

Suggestions

Rewrite using concrete action verbs, e.g. "Authenticate users, create and execute sandboxes, deploy apps, manage credits and payments, and submit coding challenges on the Flow Nexus platform."

Add an explicit "Use when..." clause listing the natural trigger phrases a user would say (e.g. "Use when managing Flow Nexus sandboxes, deploying Flow Nexus apps, or handling Flow Nexus credits/payments").

Add common term variations (e.g. "rUv credits", "MCP", "Flow Nexus API") to improve trigger term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain and five concrete capability areas ("authentication, sandboxes, app deployment, payments, and challenges"), but these are category nouns rather than the concrete action verbs (e.g. "extract", "fill", "merge") that the top anchor requires.	2 / 3
Completeness	It answers "what" (platform management across the listed areas) but provides no "when should Claude use it" guidance; per the rubric, a missing "Use when..." clause caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "authentication", "payments", and "deployment" are words users would say, and the branded "Flow Nexus" is distinctive, but coverage lacks common variations and there are no explicit "Use when..." trigger phrases.	2 / 3
Distinctiveness Conflict Risk	The branded "Flow Nexus platform management" gives it a recognizable niche, but the listed subsystems (auth, payments, deployment) are broad enough to overlap with other generic platform/code skills, so it is not yet a clearly distinct trigger set.	2 / 3
	Total	8 / 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 (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/claude-flow
Commit: 8ae8752

Reviewed: 2 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.