flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
59
41%
Does it follow best practices?
Impact
94%
2.04xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/flow-nexus-platform/SKILL.mdQuality
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 (Flow Nexus) and lists broad capability areas, which provides some useful context. However, it lacks concrete action verbs describing what operations are performed, and critically, it has no 'Use when...' clause to guide skill selection. The capability areas listed are too high-level to serve as effective triggers.
Suggestions
Add a 'Use when...' clause specifying trigger conditions, e.g., 'Use when the user asks about Flow Nexus, managing sandboxes, deploying apps to Flow Nexus, or configuring Flow Nexus payments.'
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 alternative terms or file types users might reference, such as specific Flow Nexus CLI commands, API names, or common task descriptions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a specific domain ('Flow Nexus platform') and lists several action areas (authentication, sandboxes, app deployment, payments, challenges), but these are 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 areas) 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 at a category level, this scores a 1. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'authentication', 'sandboxes', 'app deployment', 'payments', and 'challenges', which users might mention. However, 'Flow Nexus' is a specific platform name that helps, but common variations or alternative phrasings users might use are missing. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Flow Nexus platform' provides some distinctiveness since it's a specific platform name. However, broad terms like 'authentication', 'payments', and 'app deployment' could overlap with other skills that handle those domains in different contexts. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%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 excellent concrete code examples for every API call, but it is severely bloated — it reads more like full platform documentation than a focused skill file. It includes extensive non-essential content (pricing tiers, tips for success, achievement type descriptions, category lists, troubleshooting FAQs) that inflates token usage without adding operational value for Claude. Workflow clarity suffers from missing validation/error-handling checkpoints in multi-step processes.
Suggestions
Reduce content by 60-70%: remove pricing tiers, tips lists, achievement type descriptions, category enumerations, troubleshooting FAQs, and support links — these are reference docs, not skill instructions.
Split into multiple files (e.g., SANDBOX.md, PAYMENTS.md, CHALLENGES.md) and keep SKILL.md as a concise overview with links, rather than inlining everything.
Add explicit validation checkpoints to the Quick Start workflow: check auth_status after login, verify sandbox_status after creation, confirm balance before deployment.
Remove the 'Best Practices', 'Tips for Success', 'Cost Optimization Tips' sections — Claude can infer these from the API signatures and doesn't need generic software development advice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~700+ lines. Includes extensive lists of tips, best practices, achievement types, category enumerations, subscription tiers with pricing details, and troubleshooting FAQs that Claude doesn't need spelled out. Much of this is reference documentation that could be drastically condensed or linked externally. | 1 / 3 |
Actionability | Every API call is shown with concrete, copy-paste-ready JavaScript examples including realistic parameters. The function signatures, parameter names, and expected values are all explicit and executable. | 3 / 3 |
Workflow Clarity | The Quick Start Guide provides a clear 5-step sequence, but lacks validation checkpoints — there's no guidance on checking if registration succeeded before logging in, verifying sandbox creation before executing code, or handling failures at any step. For operations like sandbox deletion and storage deletion, no confirmation or validation steps are mentioned. | 2 / 3 |
Progressive Disclosure | Uses HTML <details> tags for advanced patterns which is a good technique, but the main body is still a monolithic wall of content (~700 lines inline). With no bundle files, all content is crammed into one file when categories like Payments, Challenges, and Storage could each be separate reference files linked from a concise overview. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%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/claude-flow
- Commit
ca77f83
- Reviewed
Table of Contents
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.