agent-v3-integration-architect
Agent skill for v3-integration-architect - invoke with $agent-v3-integration-architect
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-v3-integration-architect31
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
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is critically deficient across all dimensions. It functions only as an invocation reference rather than a proper skill description, providing no information about capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add specific concrete actions describing what the skill does (e.g., 'Designs integration architectures, creates API specifications, maps data flows between systems')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about system integration, API design, connecting services, or v3 architecture planning')
Remove or relocate the invocation syntax to focus the description on capabilities and selection criteria
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for v3-integration-architect' is completely abstract and provides no information about what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command with no explanation of capabilities or use cases. | 1 / 3 |
Trigger Term Quality | The only potential trigger term is the technical identifier 'v3-integration-architect' and the invocation command. No natural keywords a user would say are present - terms like 'integration', 'API', 'architecture', or specific actions are missing. | 1 / 3 |
Distinctiveness Conflict Risk | While the specific agent name 'v3-integration-architect' is unique, the description is so vague that Claude cannot determine when to select this skill. The term 'integration' could overlap with many other skills without clearer context. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is excessively verbose and reads more like a project planning document than actionable agent instructions. It contains significant repetition (duplication analysis appears twice), pseudocode rather than executable examples, and lacks the progressive disclosure structure expected of a well-organized skill. The content would benefit from aggressive trimming and splitting into focused reference files.
Suggestions
Reduce content by 70%+ by removing repeated information (duplication analysis, performance targets) and explanatory prose that Claude doesn't need
Convert pseudocode interfaces to executable code examples with actual implementation logic, or remove them entirely if they're just illustrative
Split detailed content into reference files: MIGRATION_PLAN.md, PERFORMANCE_TARGETS.md, INTEGRATION_APIS.md - keep SKILL.md as a concise overview with links
Add explicit validation checkpoints within the migration workflow (e.g., 'Run integration tests before proceeding to Phase 2')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive ASCII diagrams, repetitive tables, and explanatory content that Claude doesn't need. The 'duplication analysis' table appears twice (in hooks and body), and performance targets are repeated multiple times across sections. | 1 / 3 |
Actionability | Contains TypeScript code examples but they are largely pseudocode/interface definitions rather than executable implementations. Methods like 'migrateSwarmCoordination()' show intent but lack actual implementation details - they describe what to do rather than how to do it. | 2 / 3 |
Workflow Clarity | Has a phased migration plan (Weeks 7-10) with clear sequence, but lacks explicit validation checkpoints between phases. The 'Success Metrics & Validation' section lists targets but doesn't integrate them as verification steps within the workflow itself. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including detailed implementation plans, benchmarks, risk tables, and coordination points that could be split into separate reference documents. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.