workspace

Dynamic multi-repo and monorepo awareness for Claude Code. Analyze workspace topology, track API contracts, and maintain cross-repo context.

Quality

30%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/workspace/SKILL.md

Quality

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 management) but relies on abstract, buzzword-heavy language ('dynamic awareness', 'workspace topology') rather than concrete actions. The complete absence of a 'Use when...' clause is a significant weakness, as Claude would struggle to know when to select this skill from a large pool. The trigger terms are relevant but incomplete.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user is working across multiple repositories, asks about cross-repo dependencies, or needs to understand how services in a monorepo interact.'

Replace abstract phrases like 'dynamic multi-repo awareness' and 'workspace topology' with concrete actions such as 'detect shared dependencies between repos', 'map service boundaries', 'identify breaking API changes across packages'.

Include more natural user trigger terms like 'multiple repositories', 'microservices', 'shared libraries', 'dependency graph', 'breaking changes'.

Dimension	Reasoning	Score
Specificity	Names the domain (multi-repo/monorepo) 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 shared dependencies' or 'map service boundaries'.	2 / 3
Completeness	Describes what it does (analyze workspace topology, track API contracts, maintain cross-repo 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', 'cross-repo', and 'workspace topology', but misses common user phrasings like 'multiple repositories', 'microservices', 'shared libraries', 'dependency tracking', or 'repo structure'.	2 / 3
Distinctiveness Conflict Risk	The multi-repo/monorepo focus provides some distinctiveness, but 'workspace awareness' and 'cross-repo context' are broad enough to potentially overlap with general project navigation or code analysis 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 comprehensive in scope but severely undermined by its verbosity — it's essentially a full specification document rather than a concise skill file. The inline artifact format examples alone consume more tokens than many entire skills, and much of this content should be split into referenced files. While the detection patterns and bash commands provide some actionable guidance, the core commands delegate to missing external files.

Suggestions

Move all artifact format examples (TOPOLOGY.md, CONTRACTS.md, DEPENDENCY_GRAPH.md, KEY_FILES.md, CROSS_REPO_INDEX.md) into separate reference files and link to them from a concise overview section.

Remove the 'Problem' section entirely — Claude understands cross-repo challenges — and condense the solution overview to under 20 lines.

Provide the referenced command files (commands/analyze-workspace.md, commands/sync-contracts.md) as bundle files, or inline their core logic concisely.

Add explicit validation checkpoints within the analysis workflow phases (e.g., 'Verify module count matches expected before proceeding to Phase 2').

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~600+ lines. Contains extensive example output templates (TOPOLOGY.md, CONTRACTS.md, DEPENDENCY_GRAPH.md, KEY_FILES.md, CROSS_REPO_INDEX.md) that are illustrative but massively inflate token count. The 'Problem' section explains things Claude already understands. ASCII box diagrams are repeated throughout. Much content could be in referenced files rather than inline.	1 / 3
Actionability	Contains concrete bash commands for detection and grep patterns for dependency analysis, plus executable CI/CD YAML and hook scripts. However, the core workflow relies on commands (/analyze-workspace, /sync-contracts) that reference external files ('See commands/analyze-workspace.md for full specification') without providing them. The artifact format examples are templates rather than executable instructions for Claude to follow.	2 / 3
Workflow Clarity	The four-phase analysis protocol (Topology → Dependency Graph → Contract Extraction → Key File Identification) provides clear sequencing with time estimates. However, validation checkpoints are weak — the freshness system describes tiers but doesn't provide explicit 'validate then proceed' gates within the analysis workflow itself. The cross-repo change detection shows a nice impact analysis pattern but lacks concrete error recovery steps.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with all content inline. The generated artifact format examples (TOPOLOGY.md, CONTRACTS.md, DEPENDENCY_GRAPH.md, KEY_FILES.md, CROSS_REPO_INDEX.md) consume hundreds of lines that should be in separate reference files. References to 'commands/analyze-workspace.md' and 'commands/sync-contracts.md' are made but no bundle files are provided. The skill tries to be both overview and complete reference simultaneously.	1 / 3
	Total	6 / 12 Passed

Validation

81%

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 — 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: 7e5f7a2

Reviewed: 3 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.