flow-nexus-platform

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

1.95x

Quality

53%

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

50%Weight 40%Scale 1-3

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 — every operation is a concrete, copy-paste tool call — but it is a bloated monolithic API dump padded with generic best-practice and troubleshooting filler, with no validation checkpoints on destructive operations and no external reference files to offload the bulk.

Suggestions

Move the per-tool API reference into one-level-deep reference files (e.g. AUTH.md, SANDBOXES.md, PAYMENTS.md) and keep SKILL.md as a concise overview with Quick Start plus pointers, cutting the bulk dramatically.

Remove generic filler Claude already knows — the Security/Performance/Development/Cost 'Best Practices' lists, 'Tips for Success', and the promotional Queen Seraphina description — keeping only platform-specific guidance.

Add explicit validate-then-proceed checkpoints for destructive/batch operations (e.g. confirm sandbox status before delete, verify deployment health after template_deploy) to lift workflow_clarity above 2.

Dimension	Reasoning	Score
Conciseness	The ~1150-line body dumps a full API reference inline plus padded generic guidance Claude already knows ('Never hardcode API keys', 'Enable 2FA', 'Start Simple', 'Review Solutions') and promotional prose ('Queen Seraphina is an advanced AI assistant with deep expertise...'), matching the verbose/padded level-1 anchor.	1 / 3
Actionability	Nearly every capability is shown as a concrete, copy-paste-ready MCP tool call with full parameter objects and inline comments (e.g. sandbox_create with template, env_vars, install_packages), matching the fully-executable level-3 anchor.	3 / 3
Workflow Clarity	The Quick Start Guide sequences five steps, but destructive and batch operations (sandbox_delete, storage_delete, template_deploy) have no validate-then-proceed checkpoints or error-recovery loops, which per the rubric caps workflow_clarity at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned with a TOC and uses <details> blocks for advanced patterns, but the entire per-tool API reference is inlined in SKILL.md rather than split into one-level-deep reference files, fitting 'content that should be separate is inline'.	2 / 3
	Total	8 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 clear, branded niche and enumerates capability domains, but it reads as a noun list rather than concrete actions and omits any explicit 'when to use' trigger clause, capping completeness and specificity at 2.

Suggestions

Reword the capability list as concrete actions using verbs (e.g., 'Authenticate users, create and run code sandboxes, deploy apps, manage credits and payments, and solve coding challenges').

Add an explicit 'Use when...' trigger clause naming natural user phrasings (e.g., 'Use when the user asks to deploy to Flow Nexus, manage sandboxes or credits, or browse challenges').

Include common synonym terms users would actually say — credits/billing, templates/apps, storage, leaderboards — to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description lists several concrete capability domains ('authentication, sandboxes, app deployment, payments, and challenges') but presents them as nouns rather than concrete actions, matching 'names domain and some actions' rather than the verb-driven level-3 anchor.	2 / 3
Completeness	It clearly states what the skill does but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant keywords (sandboxes, app deployment, payments, challenges) but misses common variations users would naturally say (credits, billing, templates, apps, storage, leaderboards), fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The Flow Nexus brand name scopes it to a specific platform with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 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/agentic-flow
Path: .claude/skills/flow-nexus-platform/SKILL.md
Commit: d3735a3

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