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, but lacks concrete actions and any explicit trigger guidance for when Claude should select this skill. The categories listed are too high-level to clearly communicate what specific operations the skill enables, and the absence of a 'Use when...' clause significantly weakens its utility for skill selection.
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, configure authentication, or handle payments on the Flow Nexus platform.'
Replace high-level category names with specific concrete actions, e.g., 'Create and manage Flow Nexus sandboxes, deploy and configure apps, process payments, authenticate users, and track challenges.'
Include natural language variations users might say, such as 'login', 'deploy', 'billing', 'sandbox setup', 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 (Flow Nexus 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 the primary distinguishing term. Missing common variations or more natural phrasing users might use (e.g., 'login', 'deploy', 'billing'). | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Flow Nexus' as a specific platform name provides some distinctiveness, but the broad categories like 'authentication', 'payments', and 'app deployment' could overlap with other platform management skills. Without clearer scoping, there's moderate conflict risk. | 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 excels at actionability with comprehensive, executable API call examples covering the entire Flow Nexus platform. However, it is severely bloated — subscription tier details, marketing-style feature lists, tips sections, and category enumerations consume hundreds of tokens that should either be in separate reference files or omitted entirely. The workflow lacks validation checkpoints between dependent steps.
Suggestions
Move reference material (pricing tiers, category lists, achievement types, best practices, troubleshooting, support links) into separate files and link to them from the main skill, reducing the main file to under 200 lines.
Remove informational padding that Claude doesn't need (e.g., 'Tips for Success', 'Cost Optimization Tips', 'Publishing Best Practices', subscription marketing copy) — these are user-facing docs, not agent instructions.
Add explicit validation checkpoints in the Quick Start workflow, e.g., 'Check sandbox status before executing code' and 'Verify auth_status returns authenticated before proceeding'.
Remove the version history and consolidation note at the bottom — these serve no actionable purpose for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 700+ lines. Includes extensive lists of tips, best practices, pricing tiers, achievement types, challenge categories, and other reference material that could be in separate files. Much content is informational padding (e.g., subscription tier marketing copy, 'Tips for Success' lists) rather than actionable instruction Claude needs. | 1 / 3 |
Actionability | Every API call includes concrete, copy-paste-ready JavaScript examples with realistic parameters. Function signatures, parameter names, and expected values are all clearly specified with no pseudocode. | 3 / 3 |
Workflow Clarity | The Quick Start Guide provides a clear 5-step sequence, but lacks validation checkpoints. There's no guidance on verifying sandbox creation succeeded before executing code, no error handling between steps, and no feedback loops for destructive operations like sandbox deletion or file deletion. | 2 / 3 |
Progressive Disclosure | Uses HTML details/summary tags for advanced patterns and has a table of contents, which shows awareness of progressive disclosure. However, the main body is a monolithic wall of 700+ lines that should be split into separate reference files. The inline pricing tables, category lists, and best practices sections bloat the main skill file significantly. | 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/ruflo
- Commit
398f7c2
- 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.