flow-nexus-platform

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

2.04x

Quality

59%

Does it follow best practices?

Impact

94%

2.04x

Average score across 3 eval scenarios

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/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 skill is a comprehensive, highly actionable MCP reference for the Flow Nexus platform, but it is monolithic: a ~1150-line wall of tool calls inlined into SKILL.md with redundant Quick Start examples, corrupted slashes in some code samples, and no validation checkpoints around destructive operations. Splitting the API reference into separate files and adding verify steps would substantially improve it.

Suggestions

Move the per-tool API reference into separate reference files (e.g. AUTH.md, SANDBOXES.md, PAYMENTS.md) and keep SKILL.md as a concise overview pointing to them, with the Quick Start as the only inline walkthrough.

Add validation/verification checkpoints before destructive and batch operations (e.g. confirm sandbox status and prompt before sandbox_delete; verify upload before storage_delete) and a validate->fix->retry loop in the Quick Start.

Fix the corrupted slash characters ('$' rendered where '/' should be) in URLs and file paths so code samples are executable as written.

Dimension	Reasoning	Score
Conciseness	The body is code-dense and avoids explaining concepts Claude already knows, but at ~1150 lines it is very long and the Quick Start Guide repeats tool calls already shown in earlier sections, so it could be tightened.	3 / 5
Actionability	Dozens of copy-paste-ready MCP tool calls with full parameter examples cover the common cases, but several samples have corrupted path/URL slashes (e.g. 'https:/$api.example.com', '$app$config$database.json', 'credits$hour'), introducing minor execution gaps.	4 / 5
Workflow Clarity	The Quick Start Guide provides a clear 5-step sequence (register, bill, sandbox, deploy, challenge) but lacks validation checkpoints, and destructive operations (sandbox_delete, storage_delete, payments) have no verify-before-proceed steps — the missing-validation cap applies.	3 / 5
Progressive Disclosure	A table of contents and <details> blocks for advanced patterns give some structure, but the entire API reference is inlined in SKILL.md with no separate reference files, so content that should be split remains inline.	3 / 5
	Total	13 / 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 clearly scopes a distinct niche (Flow Nexus) and lists its main capability areas, but it relies on the generic verb 'management' and omits any explicit 'Use when...' trigger guidance. Adding concrete action verbs and a trigger clause would lift completeness and specificity.

Suggestions

Replace the generic 'management' with concrete action verbs (e.g. 'Authenticate users, create and run sandboxes, deploy apps, manage credits, and submit coding challenges').

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g. 'Use when working with the Flow Nexus platform, sandboxes, app deployment, credits, or coding challenges').

Include natural synonyms/file extensions users might say (e.g. 'credits', 'rUv', 'login') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Flow Nexus domain and five capability areas (authentication, sandboxes, app deployment, payments, challenges), but the only action verb is the generic 'management' — these are sub-domains rather than concrete actions like 'extract' or 'deploy', matching the score-3 anchor.	3 / 5
Completeness	A clear 'what' is present but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Good coverage of natural terms a user would say (authentication, sandboxes, app deployment, payments, challenges); a few common variations (e.g. 'credits', 'login') are absent, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Tied to the distinct Flow Nexus niche with minimal conflict risk, though 'comprehensive platform management' spanning many areas leaves minor overlap risk with closely related Flow Nexus skills.	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/ruflo
Path: .agents/skills/flow-nexus-platform/SKILL.md
Commit: fa13ee4

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