workspace

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

47%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body has strong workflow sequencing and concrete detection commands but is far too verbose, inlining full mock artifact examples and restating known concepts, and it references bundle files that do not exist.

Suggestions

Move the full TOPOLOGY.md/CONTRACTS.md/DEPENDENCY_GRAPH.md mock contents out of SKILL.md into reference files and link to them, keeping only concise format summaries inline.

Cut the "The Problem" framing and ASCII-art boxes; assume Claude understands multi-repo concepts and keep only the actionable detection/analysis steps.

Either create the referenced command and skill files (commands/analyze-workspace.md, etc.) or remove the cross-references so progressive disclosure points to real bundles.

Dimension	Reasoning	Score
Conciseness	The ~970-line body is heavily padded with ASCII-art diagrams, restated "Problem" framing Claude already knows, and inline mock artifact dumps; time-sensitive specifics like "Generated: 2026-01-20T14:32:00Z" appear outside any deprecated section.	1 / 3
Actionability	Concrete, executable detection commands (grep/find/ls) and hook/workflow YAML are present, but the core artifact-generation logic is delegated to referenced files ("See commands/analyze-workspace.md") that are not shown, leaving guidance incomplete.	2 / 3
Workflow Clarity	The analysis protocol is explicitly sequenced (Phase 1-4 with checklists) and includes validation checkpoints, freshness tiers, and feedback loops (sync -> validate -> re-validate).	3 / 3
Progressive Disclosure	References are signaled (commands/*.md, existing-repo.md) but no bundle files exist to back them, and large mock artifact contents that should live in separate files are inlined, making the body monolithic.	2 / 3
	Total	8 / 12 Passed

Description

82%

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 is specific, well-triggered, and distinct, but omits an explicit "when to use" clause inside the description field itself, which caps its completeness at 2.

Suggestions

Add a "Use when..." clause to the description (e.g., "Use when working across multiple repos or in a monorepo with shared dependencies") so both what and when are explicit in one field.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Analyze workspace topology, track API contracts, and maintain cross-repo context" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Answers "what" clearly but the description field itself lacks a "Use when..." clause; the when guidance lives only in the separate when-to-use field, capping completeness per the rubric guideline.	2 / 3
Trigger Term Quality	Natural terms a user would say are well covered: "multi-repo", "monorepo", "API contracts", "workspace topology", "cross-repo context".	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (multi-repo/monorepo workspace analysis) with distinct triggers unlikely to overlap with single-repo skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: 9dacc46

Reviewed: about 5 hours 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.