workspace
Dynamic multi-repo and monorepo awareness for Claude Code. Analyze workspace topology, track API contracts, and maintain cross-repo context.
33
30%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/workspace/SKILL.mdQuality
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 clear domain (multi-repo and monorepo workspaces) and lists some relevant capabilities, but the actions remain abstract rather than concrete. The most significant weakness is the complete absence of a 'Use when...' clause, making it unclear when Claude should select this skill. The trigger terms lean technical and miss natural language variations users might employ.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user is working across multiple repositories, asks about dependencies between repos, or needs to understand how changes in one repo affect another.'
Replace abstract phrases like 'analyze workspace topology' and 'maintain cross-repo context' with concrete actions such as 'map inter-repo dependencies', 'detect breaking API changes across services', or 'resolve cross-repo import paths'.
Include natural language trigger terms users might say, such as 'multiple repositories', 'microservices', 'shared libraries', 'dependency graph', or 'breaking changes across repos'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (multi-repo/monorepo workspaces) and some actions ('analyze workspace topology', 'track API contracts', 'maintain cross-repo context'), but these are somewhat abstract rather than concrete, actionable operations like 'detect breaking changes' or 'map dependency graphs'. | 2 / 3 |
Completeness | Describes what it does (analyze topology, track contracts, maintain context) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also somewhat vague, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'multi-repo', 'monorepo', 'API contracts', and 'cross-repo', which are useful but somewhat technical. Missing common natural language variations users might say like 'multiple repositories', 'workspace', 'dependencies between repos', or 'microservices'. | 2 / 3 |
Distinctiveness Conflict Risk | The multi-repo/monorepo focus provides some distinctiveness, but terms like 'workspace awareness' and 'cross-repo context' are broad enough to potentially overlap with general project navigation or dependency management skills. | 2 / 3 |
Total | 7 / 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 extremely comprehensive in scope but severely undermined by its verbosity and monolithic structure. It attempts to document an entire workspace analysis system in a single file, resulting in ~600+ lines that would consume significant context window. The artifact format examples alone account for roughly half the content and should be extracted into reference files, with the main SKILL.md serving as a concise overview with pointers.
Suggestions
Extract all artifact format examples (TOPOLOGY.md, CONTRACTS.md, DEPENDENCY_GRAPH.md, KEY_FILES.md, CROSS_REPO_INDEX.md formats) into separate reference files like `templates/TOPOLOGY_TEMPLATE.md` and reference them from the main skill.
Move CI/CD integration, troubleshooting, and integration-with-other-skills sections into separate bundle files to reduce the main SKILL.md to under 150 lines.
Add the missing bundle files for commands/analyze-workspace.md and commands/sync-contracts.md that are referenced but don't exist.
Add explicit validation checkpoints between the four analysis phases (e.g., 'Verify topology detection found at least one module before proceeding to dependency graph').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines. Contains massive ASCII diagrams, exhaustive example outputs for every artifact format (TOPOLOGY.md, CONTRACTS.md, DEPENDENCY_GRAPH.md, KEY_FILES.md, CROSS_REPO_INDEX.md), lengthy tables, and explanatory content Claude doesn't need. The 'Problem' section explains obvious concepts. Most of the artifact format examples could be in separate reference files. | 1 / 3 |
Actionability | Contains concrete bash commands for detection and some executable CI/CD YAML, but the core analysis protocol is more of a conceptual framework than executable guidance. The 'phases' describe what to do at a high level with checklists rather than providing copy-paste-ready implementations. Commands reference external files (commands/analyze-workspace.md, commands/sync-contracts.md) that don't exist in the bundle. | 2 / 3 |
Workflow Clarity | The four-phase analysis protocol provides a clear sequence, and the contract freshness system has defined tiers. However, validation checkpoints are mostly implicit - there's no explicit 'verify this worked before proceeding' step between phases. The cross-repo change detection shows a nice ordered workflow but it's presented as a UI mockup rather than actionable steps with verification. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to support it. References to commands/analyze-workspace.md and commands/sync-contracts.md don't exist. The massive artifact format examples (TOPOLOGY.md, CONTRACTS.md, DEPENDENCY_GRAPH.md, KEY_FILES.md, CROSS_REPO_INDEX.md) should each be in separate reference files. The CI/CD integration, troubleshooting, and integration sections all belong in separate files. | 1 / 3 |
Total | 6 / 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 (972 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 | |
- Repository
- alinaqi/claude-bootstrap
- Commit
65efb33
- 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.