flow-nexus-platform

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

1.95x

Quality

52%

Does it follow best practices?

Impact

94%

1.95x

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

Discovery

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 and lists capability areas but lacks concrete actions and explicit trigger guidance. It reads more like a feature list than actionable skill documentation. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user mentions Flow Nexus, needs to manage sandboxes, deploy apps to Flow, or handle Flow payment integration.'

Replace high-level categories with specific concrete actions, e.g., 'Create and manage Flow Nexus sandboxes, deploy applications, configure authentication flows, process payments, and track challenges.'

Include natural user phrases and file types users might mention, such as 'Flow app', 'sandbox environment', 'Flow deployment', or specific Flow Nexus terminology.

Dimension	Reasoning	Score
Specificity	Names the domain (Flow Nexus platform) and lists several action areas (authentication, sandboxes, app deployment, payments, challenges), but these are high-level categories rather than concrete specific actions like 'create sandbox', 'deploy app', or 'process payment'.	2 / 3
Completeness	Only addresses 'what' at a high level with no 'Use when...' clause or equivalent trigger guidance. There's no explicit indication of when Claude should select this skill over others.	1 / 3
Trigger Term Quality	Includes some relevant keywords (authentication, sandboxes, app deployment, payments, challenges) but 'Flow Nexus' is a specific platform name that users may or may not use naturally. Missing common variations or natural phrases users might say.	2 / 3
Distinctiveness Conflict Risk	The 'Flow Nexus platform' name provides some distinctiveness, but terms like 'authentication', 'payments', and 'app deployment' are generic enough to potentially conflict with other platform management or deployment skills.	2 / 3
	Total	7 / 12 Passed

Implementation

72%

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

This is a comprehensive API reference skill with excellent actionability through executable code examples and good progressive disclosure structure. However, it suffers from verbosity in non-essential sections (best practices, troubleshooting, support resources) and lacks validation checkpoints in multi-step workflows. The core API documentation is strong, but the skill would benefit from trimming generic advice and adding explicit verification steps.

Suggestions

Remove or significantly condense the 'Best Practices', 'Troubleshooting', and 'Support & Resources' sections - these contain generic advice Claude already knows

Add validation steps to the Quick Start Guide workflows, e.g., 'Check sandbox.status === "running" before executing code'

Remove explanatory prose like 'Queen Seraphina is an advanced AI assistant with...' and let the code examples speak for themselves

Dimension	Reasoning	Score
Conciseness	While the skill provides useful API reference, it includes unnecessary sections like 'Best Practices' with generic advice Claude already knows (e.g., 'Never hardcode API keys'), verbose troubleshooting sections, and explanatory text that could be trimmed. The core API examples are efficient, but surrounding content adds bloat.	2 / 3
Actionability	Excellent actionability with fully executable JavaScript code examples for every API call, complete with realistic parameters, proper syntax, and copy-paste ready snippets. Each function shows exact parameter structures and expected values.	3 / 3
Workflow Clarity	The Quick Start Guide provides a reasonable sequence, but lacks validation checkpoints. For example, sandbox creation doesn't verify success before execution, payment processing doesn't confirm credits were applied before proceeding, and there's no error handling or retry guidance for multi-step operations.	2 / 3
Progressive Disclosure	Well-structured with clear Table of Contents, logical section organization, and appropriate use of collapsible details sections for advanced patterns. External resource links are clearly signaled and one level deep. Content is appropriately split between main reference and advanced topics.	3 / 3
	Total	10 / 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 (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	9 / 11 Passed

Repository: ruvnet/agentic-flow
Commit: 8db2712

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