agent-v3-integration-architect
Agent skill for v3-integration-architect - invoke with $agent-v3-integration-architect
38
6%
Does it follow best practices?
Impact
93%
4.42xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-v3-integration-architect/SKILL.mdQuality
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 provides no information about what the skill does, when it should be used, or what domain it operates in. It reads as a placeholder or auto-generated stub rather than a functional skill description.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Designs and implements v3 API integrations, maps data schemas between systems, and configures authentication flows.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs help with v3 API integration, system architecture, data mapping, or connecting services.'
Remove the invocation instruction from the description (it's not useful for skill selection) and replace with domain-specific keywords users would naturally use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it's an 'agent skill' and provides an invocation command, with no indication of what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description is essentially just an invocation instruction with no functional or contextual information. | 1 / 3 |
Trigger Term Quality | There are no natural keywords a user would say. 'v3-integration-architect' is technical jargon that doesn't map to any user intent or natural language query. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it provides no distinguishing characteristics. 'Integration architect' could overlap with countless integration, architecture, or API-related skills without any way to differentiate. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an aspirational architecture document rather than an actionable skill. It contains extensive non-executable TypeScript pseudocode referencing fictional APIs, repeats performance metrics multiple times, and provides no concrete commands or steps Claude could actually execute. The content would benefit enormously from being condensed to a concise overview with actual executable guidance and splitting detailed plans into referenced sub-documents.
Suggestions
Replace fictional TypeScript pseudocode with actual executable commands or real code that Claude can run—if the APIs don't exist yet, focus on the concrete file operations and refactoring steps instead.
Eliminate repeated performance numbers (2.49x-7.47x, 150x-12,500x, <0.05ms appear 2-3 times each) and consolidate into a single metrics table.
Split the monolithic content into separate files (e.g., MIGRATION-PLAN.md, PERFORMANCE-TARGETS.md, INTEGRATION-APIS.md) and reference them from a concise overview.
Add explicit validation checkpoints between migration phases with concrete commands to verify success before proceeding (e.g., run specific tests, check line counts, verify API compatibility).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 300+ lines. Massive amounts of illustrative TypeScript that is not executable (pseudo-API calls to non-existent methods). Repeats the same performance numbers (2.49x-7.47x, 150x-12,500x, <0.05ms) multiple times across sections. The duplication analysis table duplicates information already in the hooks. Claude doesn't need explanations of what RL algorithms are or what Flash Attention is. | 1 / 3 |
Actionability | Despite containing extensive TypeScript code blocks, none of it is executable—it references fictional APIs (agentic-flow@alpha's Swarm, SONA, AgentDB, etc.) with made-up method signatures. There are no real commands to run, no actual file paths to edit, and no concrete steps Claude could follow. The code is aspirational pseudocode dressed up as TypeScript. | 1 / 3 |
Workflow Clarity | There is a phased migration plan (Phase 1-3 with week targets) and a backward compatibility strategy with sequential steps. However, there are no validation checkpoints between phases, no error recovery steps, and no concrete criteria for when to proceed from one phase to the next. The checklist at the end is useful but disconnected from the workflow steps. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. All content—integration architecture, migration plan, performance targets, risk mitigation—is inlined in a single massive document. Content like the detailed TypeScript examples for each integration point, the risk table, and coordination points could easily be split into separate referenced files. | 1 / 3 |
Total | 5 / 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.
- Repository
- ruvnet/ruflo
- Commit
ccb062f
- 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.