flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill flow-nexus-platform60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 capability areas but lacks concrete actions and completely omits usage triggers. The high-level category listing (authentication, sandboxes, etc.) doesn't help Claude understand when to select this skill over others, and the absence of a 'Use when...' clause significantly weakens its utility for skill selection.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, 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 actions, e.g., 'Create and manage Flow Nexus sandboxes, deploy applications, configure authentication, process payments, and complete platform challenges'
Include natural user phrases and variations, e.g., 'Flow sandbox', 'deploy to Flow', 'Flow auth', 'Flow Nexus setup'
| 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 | Only describes 'what' at a high level but completely lacks any 'when' guidance. No 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap this at 2, but the 'what' is also weak, warranting a 1. | 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 natural phrases users might say. | 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 platform management or deployment skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable API reference documentation with comprehensive coverage of the Flow Nexus platform. However, it suffers from verbosity with explanatory content Claude doesn't need (tier descriptions, tips, category lists) and lacks explicit validation checkpoints in multi-step workflows. The monolithic structure would benefit from splitting into focused reference files.
Suggestions
Remove explanatory prose (tier descriptions, 'Tips for Success', category explanations) and keep only the executable examples and essential parameters
Add explicit validation steps to workflows: check sandbox status after creation, verify deployment success before proceeding, include error handling patterns
Split into focused files: SKILL.md (quick start + overview), API_REFERENCE.md (all endpoints), PRICING.md (tiers/costs), TROUBLESHOOTING.md
Remove the 'Best Practices' and 'Tips' sections - these describe general knowledge Claude already has about security, performance, and development
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | While the skill provides comprehensive coverage, it includes unnecessary explanatory text (e.g., 'Queen Seraphina is an advanced AI assistant with...', pricing tier descriptions, 'Tips for Success' sections) that Claude doesn't need. The content could be significantly tightened while preserving utility. | 2 / 3 |
Actionability | Excellent executable code examples throughout with complete function calls, proper parameters, and realistic values. Every API endpoint has copy-paste ready JavaScript examples with clear parameter documentation. | 3 / 3 |
Workflow Clarity | The Quick Start Guide provides a reasonable sequence, but multi-step workflows lack explicit validation checkpoints. For example, sandbox creation doesn't verify success before execution, and deployment workflows don't include rollback or verification steps for destructive operations. | 2 / 3 |
Progressive Disclosure | Uses collapsible details sections for advanced content which is good, but the main document is a monolithic 800+ line file. Content like pricing tiers, achievement types, and troubleshooting could be split into separate reference files with clear navigation links. | 2 / 3 |
Total | 9 / 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 | |
- 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.