flow-nexus-platform

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

1.95x

Quality

41%

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

40%

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 broad capability areas, which helps with distinctiveness. However, it lacks concrete action verbs describing what operations are performed and entirely omits 'when to use' guidance, significantly weakening its utility for skill selection among many options.

Suggestions

Add a 'Use when...' clause specifying trigger conditions, e.g., 'Use when the user mentions Flow Nexus, or needs to manage sandboxes, deploy apps, handle payments, or configure authentication on the Flow Nexus platform.'

Replace category nouns with specific action phrases, 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 platform ('Flow Nexus') and lists several domain areas (authentication, sandboxes, app deployment, payments, challenges), but these are high-level categories 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 domains) 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 partially addressed, this scores a 1.	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 description is tied to a specific platform ('Flow Nexus'), which creates a clear niche. It's unlikely to conflict with other skills since the platform name serves as a strong distinguishing identifier.	3 / 3
	Total	8 / 12 Passed

Implementation

42%

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 covering the entire Flow Nexus platform. However, it is severely bloated — a monolithic document that tries to be both a quick reference and comprehensive documentation simultaneously. The lack of file splitting, validation checkpoints in workflows, and excessive non-instructional content (pricing tiers, tips lists, achievement descriptions) significantly reduce its effectiveness as a skill file.

Suggestions

Split into multiple files (e.g., AUTH.md, SANDBOX.md, APP_STORE.md, PAYMENTS.md, CHALLENGES.md, STORAGE.md) and make SKILL.md a concise overview with one-level-deep references to each.

Remove non-instructional content that Claude doesn't need: subscription tier marketing details, 'tips for success' lists, achievement type descriptions, category enumerations, and support/resource links.

Add explicit validation checkpoints to the Quick Start workflow (e.g., 'Check sandbox status before executing code', 'Verify auth_status returns authenticated before proceeding').

Eliminate the 'Best Practices', 'Troubleshooting', 'Version History', and 'Support & Resources' sections — these are documentation concerns, not skill instructions.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~800+ lines. Massive amounts of content that could be split into reference files. Includes extensive lists of categories, tips, best practices, pricing tiers, achievement types, and troubleshooting that pad the document significantly. Much of this (e.g., subscription tier details, cost optimization tips, challenge tips for success) is not actionable instruction for Claude.	1 / 3
Actionability	Every API call is shown with concrete, executable MCP tool invocations including realistic parameters. The code examples are copy-paste ready with clear parameter names and values, covering the full range of platform operations.	3 / 3
Workflow Clarity	The Quick Start Guide provides a reasonable 5-step sequence, but lacks validation checkpoints. There's no guidance on checking if sandbox creation succeeded before executing code, no error handling between steps, and no feedback loops for operations like deployment or challenge submission that could fail.	2 / 3
Progressive Disclosure	Despite having a section literally titled 'Progressive Disclosure' with collapsible details, the skill is a monolithic wall of text with everything inline. There are no bundle files to reference, and the content (~800+ lines) desperately needs to be split into separate files (e.g., SANDBOX.md, PAYMENTS.md, CHALLENGES.md) with the main SKILL.md serving as a concise overview.	1 / 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 (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: 6a06854

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.