agent-repo-architect
Agent skill for repo-architect - invoke with $agent-repo-architect
39
7%
Does it follow best practices?
Impact
94%
4.94xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-repo-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 is an extremely weak description that fails on every dimension. It provides no information about what the skill does, when it should be used, or what triggers should activate it. It reads more like a label than a functional description, making it nearly impossible for Claude to correctly select this skill from a pool of available options.
Suggestions
Add concrete actions describing what repo-architect does, e.g., 'Analyzes repository structure, generates architecture diagrams, suggests directory organization, and reviews project layout.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about repository structure, project architecture, directory organization, codebase layout, or folder structure.'
Remove the invocation instruction ('invoke with $agent-repo-architect') from the description, as this is operational detail that doesn't help with skill selection, and replace it with domain-specific keywords users would naturally use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for repo-architect' is entirely vague and does not describe what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an agent skill and how to invoke it, providing no functional or contextual information. | 1 / 3 |
Trigger Term Quality | The only potentially relevant term is 'repo-architect', which is a tool name rather than a natural keyword a user would say. There are no natural language trigger terms like 'repository structure', 'project layout', 'architecture', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish it from other skills. 'Agent skill' is completely generic and 'repo-architect' gives only a faint hint at the domain without any specificity. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
14%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 poorly structured, combining a massive amount of content into a single monolithic file without validation steps or progressive disclosure. While it demonstrates some concrete tool usage patterns, the code examples are not truly executable, contain hardcoded values, and lack any error handling or verification checkpoints. The best practices and monitoring sections are entirely generic filler that waste token budget.
Suggestions
Remove the generic 'Best Practices', 'Monitoring and Analysis', and 'Integration with Development Workflow' sections entirely — they contain no actionable information Claude doesn't already know.
Add explicit validation checkpoints after destructive operations (repo creation, file pushing) such as verifying the push succeeded before proceeding, and add error recovery guidance.
Split content into separate files: keep SKILL.md as a concise overview with links to PATTERNS.md (architecture patterns), TEMPLATES.md (template creation), and SYNC.md (cross-repo synchronization).
Make code examples truly executable by replacing placeholder content like '[GitHub modes template]' with actual minimal content, and remove hardcoded user/repo references in favor of parameterized examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines with significant redundancy. Includes extensive boilerplate explanations, bullet-point lists of vague best practices Claude already knows (e.g., 'Clear separation of concerns', 'Maintainable and up-to-date documentation'), and repeated patterns. The 'Monitoring and Analysis', 'Best Practices', and 'Integration with Development Workflow' sections are almost entirely filler with no actionable content. | 1 / 3 |
Actionability | Contains concrete code examples with specific MCP tool calls and file structures, but the code is pseudocode-like JavaScript that isn't directly executable (e.g., `repositories.forEach` calling MCP tools as functions, placeholder content like '[GitHub modes template]'). Many examples are illustrative rather than copy-paste ready, and hardcoded to specific user/repo names (ruvnet) limiting reusability. | 2 / 3 |
Workflow Clarity | Despite showing multi-step processes, there are no validation checkpoints or error recovery steps anywhere. Batch architecture operations involve destructive changes (pushing files, creating repos) with no verification steps. The 'Complete Repository Architecture Optimization' section marks todos as 'completed' before they could actually be verified. No feedback loops for any operation. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inline. No references to external files for detailed content. The architecture patterns, batch operations, and best practices sections could all be separate files. The skill tries to cover too much in a single document with no navigation structure or cross-references to supplementary materials. | 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
0f7c750
- 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.