flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
68
52%
Does it follow best practices?
Impact
100%
5.55xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/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 and lists capability areas but lacks concrete actions and completely omits trigger guidance. It reads more like a feature list than a skill description that helps Claude choose when to use it. The absence of a 'Use when...' clause significantly limits its effectiveness for skill selection.
Suggestions
Add an explicit 'Use when...' clause specifying trigger conditions, e.g., 'Use when the user mentions Flow Nexus, needs to manage sandboxes, deploy apps to Flow, or handle Flow payments.'
Replace high-level categories with specific concrete actions, e.g., 'Create and manage sandboxes, deploy applications, configure authentication, process payments, and track challenges on Flow Nexus.'
Include natural user trigger terms like 'deploy to Flow', 'Flow sandbox', 'Flow app', 'Flow login' to improve keyword matching.
| 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 | Describes what the skill does (platform management across several areas) but completely lacks any 'Use when...' clause or explicit guidance on when Claude should select this skill. The 'when' is entirely missing. | 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 user-friendly trigger terms like 'deploy', 'login', 'pay', etc. | 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 skills handling those domains. | 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. The structure and progressive disclosure are well-implemented. However, it suffers from some verbosity in explanatory sections and lacks validation checkpoints for multi-step and destructive operations, which is important for a platform management skill.
Suggestions
Remove explanatory prose that Claude already knows (e.g., what Queen Seraphina is, general best practices about security and performance) to improve conciseness
Add explicit validation steps after destructive operations like sandbox_delete and storage_delete (e.g., 'Verify deletion: mcp__flow-nexus__sandbox_status({ sandbox_id }) should return 404')
Include error handling patterns and recovery steps for multi-step workflows like deployment and sandbox configuration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | While the skill provides comprehensive coverage, it includes some unnecessary explanatory text (e.g., 'Queen Seraphina is an advanced AI assistant with...', tips sections, best practices that Claude already knows). The code examples are efficient, but surrounding prose could be trimmed significantly. | 2 / 3 |
Actionability | Excellent actionability with fully executable JavaScript code examples for every operation. Each API call shows exact parameters, realistic values, and copy-paste ready syntax. The examples cover common patterns and real-world use cases. | 3 / 3 |
Workflow Clarity | The Quick Start Guide provides a clear sequence, but most sections lack validation checkpoints. For destructive operations like sandbox deletion or file deletion, there are no verification steps. Multi-step processes like deployment don't include error recovery or validation feedback loops. | 2 / 3 |
Progressive Disclosure | Well-structured with clear table of contents, logical section organization, and appropriate use of collapsible details sections for advanced topics. The main content stays focused while advanced patterns are properly hidden behind disclosure elements. | 3 / 3 |
Total | 10 / 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 (1176 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/ruvector
- Commit
462536e
- 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.