flow-nexus-platform

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

1.95x

Quality

57%

Does it follow best practices?

Impact

94%

1.95x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

53%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 skill is highly actionable with extensive executable examples, but it is an oversized monolithic reference that should be split into bundled files, and its workflows lack the validation checkpoints required for destructive/batch operations.

Suggestions

Move the per-tool API reference into separate files under references/ (e.g., AUTH.md, SANDBOXES.md, PAYMENTS.md) and keep SKILL.md as a concise overview with one-level-deep links.

Add explicit validation checkpoints to destructive/batch workflows (e.g., confirm sandbox_id before sandbox_delete, verify upload before storage_delete).

Remove the redundant Quick Start section or consolidate it with the inline examples to cut token weight.

Dimension	Reasoning	Score
Conciseness	The body is a ~1148-line monolithic API reference inlined into SKILL.md with a redundant Quick Start that repeats earlier sections and light fluff (e.g., the Queen Seraphina capability list), so it is noticeably verbose for a skill body.	2 / 5
Actionability	Provides numerous concrete, copy-paste-ready MCP tool invocations with full parameter objects covering registration, sandbox creation/execution, deployment, payments, and challenges across the common cases.	5 / 5
Workflow Clarity	A 5-step Quick Start gives a clear sequence, but validation checkpoints are absent and the skill involves destructive/batch operations (sandbox_delete, storage_delete, payments), which caps workflow clarity at 3 per the rubric rule.	3 / 5
Progressive Disclosure	Despite a TOC, section headers, and end-of-file <details> blocks, the bulk of the API reference is inlined in SKILL.md with no references/, scripts/, or assets/ bundle files, so content that clearly belongs in separate files is inlined.	2 / 5
	Total	12 / 20 Passed

Description

61%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 identifies a specific platform and enumerates several capability areas, but it lacks an explicit 'when to use' trigger clause and leans on the buzzword 'Comprehensive'. It is decent but not exemplary.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when managing Flow Nexus sandboxes, deploying apps, or handling credits/payments').

Replace the padded word 'Comprehensive' with additional concrete verb-actions (e.g., 'Create and execute sandboxes, deploy apps, manage credits and payments').

Include omitted capabilities like storage and real-time subscriptions to improve coverage accuracy.

Dimension	Reasoning	Score
Specificity	Names the domain ('Flow Nexus platform management') and lists concrete capability areas ('authentication, sandboxes, app deployment, payments, and challenges'), but these are topical nouns rather than verb-actions, the word 'Comprehensive' is over-claim padding, and several real capabilities (storage, real-time, system utilities) are omitted.	3 / 5
Completeness	Has a clear 'what' (platform management across five areas) but no 'Use when...' clause or equivalent trigger guidance, so per the cap rule completeness cannot exceed 3.	3 / 5
Trigger Term Quality	Good keyword coverage with reasonably natural terms ('authentication', 'sandboxes', 'app deployment', 'payments', 'challenges') plus the platform name 'Flow Nexus'; a few natural variations like 'credits', 'billing', or 'API' are missing.	4 / 5
Distinctiveness Conflict Risk	Naming the specific 'Flow Nexus' platform gives it a clear niche with minor overlap risk against generic platform/auth/payment skills, though the lack of explicit trigger phrases keeps it from a 5.	4 / 5
	Total	14 / 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 (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
Path: .claude/skills/flow-nexus-platform/SKILL.md
Commit: e993605

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