agent-repo-architect

Agent skill for repo-architect - invoke with $agent-repo-architect

4.94x

Quality

Does it follow best practices?

Impact

94%

4.94x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-repo-architect/SKILL.md

Quality

Discovery

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 all dimensions. 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

Describe the concrete actions this skill performs, e.g., 'Analyzes repository structure, generates architecture diagrams, suggests directory organization, and scaffolds new project layouts.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about repository structure, project architecture, directory layout, codebase organization, or scaffolding a new project.'

Remove the invocation instruction ('invoke with $agent-repo-architect') from the description, as it is operational detail that does not help with skill selection, and replace it with domain-specific keywords.

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', etc.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it provides no distinguishing characteristics. 'Agent skill' is entirely generic and 'repo-architect' gives only a 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, mixing generic architectural advice with user-specific hardcoded paths and placeholder content. It lacks validation steps for destructive batch operations (pushing files across multiple repos), and the code examples blend pseudocode with MCP tool syntax in ways that aren't directly executable. The monolithic structure with no external references or bundle files makes it difficult to navigate.

Suggestions

Add explicit validation checkpoints after each batch operation (e.g., verify repository creation succeeded before pushing files, validate pushed file contents)

Remove generic best practices sections ('Structure Optimization', 'Documentation Architecture', 'Monitoring and Analysis') that don't provide actionable, Claude-specific guidance

Replace placeholder content like '[GitHub modes template]' with actual executable content or remove those examples entirely

Split the monolithic content into separate files: a concise SKILL.md overview with references to PATTERNS.md, TEMPLATES.md, and WORKFLOWS.md for detailed content

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~250+ lines with significant redundancy. Explains high-level concepts Claude already knows (what monorepo structure is, what 'separation of concerns' means), includes lengthy best practices bullet points that are generic platitudes, and the 'Monitoring and Analysis' and 'Integration with Development Workflow' sections are vague filler. The code examples are bloated with hardcoded user-specific paths and placeholder content like '[Integration issue template]'.	1 / 3
Actionability	Contains concrete tool invocations and code blocks with specific MCP tool calls, but much of the code is pseudocode-like JavaScript that isn't directly executable (e.g., `repositories.forEach` calling MCP tools as if they were JS functions, `Date.now()` in JSON-like MCP calls). Placeholder content like '[GitHub modes template]' and '[Architecture documentation]' reduces copy-paste readiness significantly.	2 / 3
Workflow Clarity	Despite being a skill involving destructive/batch operations (pushing files to repos, creating repositories, cross-repo synchronization), there are no validation checkpoints, no error handling, no feedback loops, and no verification steps. The 'Complete Repository Architecture Optimization' batch operation pushes files and marks todos as completed without any validation that the operations succeeded.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files and no bundle files to support it. All content—patterns, examples, best practices, monitoring—is inlined in a single massive document. The directory structure patterns, integration patterns, and best practices sections could easily be separate reference files.	1 / 3
	Total	5 / 12 Passed

Validation

100%

Warnings & errors only

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/claude-flow
Commit: 9d4a9ea

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.