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 and lists broad capability areas but lacks concrete actions and any explicit trigger guidance ('Use when...'). It reads more like a feature list headline than a discriminating skill description. The specificity of 'Flow Nexus' helps with distinctiveness, but the absence of when-to-use guidance and actionable detail significantly weakens its utility for skill selection.
Suggestions
Add an explicit 'Use when...' clause specifying trigger conditions, e.g., 'Use when the user mentions Flow Nexus, or asks about managing sandboxes, deploying apps, configuring payments, or handling authentication on the Flow Nexus platform.'
Replace high-level category names with concrete actions, e.g., 'Create and manage sandboxes, deploy and configure apps, process payments, set up authentication flows, and manage challenges on the Flow Nexus platform.'
Include natural user-facing trigger terms and variations such as 'login', 'deploy', 'billing', 'sandbox environment', 'Flow Nexus API' to improve keyword coverage.
| 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 specified, 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 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-specific or general-purpose skills covering similar domains. | 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.
This skill is essentially a comprehensive API reference manual inlined into a single massive file. While the actionability is excellent with complete, executable MCP tool examples throughout, the document is severely bloated with generic advice (tips for success, best practices, cost optimization), pricing information, and category lists that don't help Claude execute tasks. The content would benefit enormously from being split into a concise overview SKILL.md pointing to separate reference files for each domain.
Suggestions
Split into a concise SKILL.md overview (under 100 lines) with links to separate files like AUTH.md, SANDBOX.md, APPSTORE.md, PAYMENTS.md, CHALLENGES.md for detailed API references.
Remove generic advice sections (Tips for Success, Best Practices, Cost Optimization Tips, Publishing Best Practices) that Claude can infer or that don't provide actionable tool guidance.
Remove pricing tiers, subscription details, and credit cost tables - these are business information that changes and doesn't help Claude execute API calls.
Add validation checkpoints to the Quick Start workflow: check auth_status after login, verify sandbox_status after creation, confirm deployment succeeded before proceeding.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 700+ lines. Massive amounts of content that could be split into separate files. Includes extensive lists of categories, tips, pricing tiers, achievement types, and best practices that are largely generic advice Claude already knows. The 'Quick Start Guide' repeats nearly identical code from earlier sections. | 1 / 3 |
Actionability | Every API call includes complete, executable JavaScript examples with realistic parameters. The MCP tool invocations are concrete and copy-paste ready with clear parameter names and example values. | 3 / 3 |
Workflow Clarity | The Quick Start Guide provides a sequential 5-step workflow, 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 sections which is a good pattern, but the main body is a monolithic wall of content that should be split into separate reference files. The Table of Contents helps navigation, but 700+ lines of inline API reference belongs in separate files with the SKILL.md serving as an 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/ruflo
- Commit
3d8f171
- 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.