CtrlK
BlogDocsLog inGet started
Tessl Logo

monorepo-architect

Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,

44

Quality

45%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/monorepo-architect/SKILL.md

The canonical home for this skill is monorepo-architect in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

35%Weight 40%Scale 1-5

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

The body is a generic, boilerplate-heavy template with no executable guidance: it lists abstract workflow steps and capabilities but provides no code, commands, or a working reference file.

Suggestions

Replace abstract workflow steps with concrete, executable commands or config snippets for each tool (Nx, Turborepo, Bazel, Lerna).

Fix or remove the broken reference: the path 'resources/implementation-playbook.md' does not exist and the bundle directory is named 'references/', not 'resources/'.

Delete the empty 'Do not use this skill when' section and generic 'Instructions' filler that add no actionable information.

DimensionReasoningScore

Conciseness

The body is mostly lean with no concept over-explanation, but it is padded with generic boilerplate such as the 'Do not use this skill when' section and abstract 'Instructions' that add no signal.

3 / 5

Actionability

There is no concrete code, command, or specific example anywhere; steps like 'Select appropriate monorepo tooling' and 'Apply relevant best practices' only describe intent rather than instruct executable actions.

1 / 5

Workflow Clarity

An eight-step sequence is present and ordered, but it lacks validation checkpoints or feedback loops and steps are high-level with no commands to verify each stage.

3 / 5

Progressive Disclosure

Content is organized into labeled sections, but the only detailed reference ('resources/implementation-playbook.md') is mispathed and the referenced bundle file does not exist, so navigation is not actually functional.

3 / 5

Total

10

/

20

Passed

Description

56%Weight 40%Scale 1-5

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 targets a clear, well-scoped niche with strong natural trigger terms, but it suffers from a truncated 'Use when' clause and generic expertise wording instead of concrete actions.

Suggestions

Complete the truncated 'Use when' clause (e.g., 'Use when setting up a new monorepo, migrating from polyrepo, optimizing CI, or managing cross-project dependencies').

Replace generic expertise claims ('Expert in', 'Masters') with concrete actions ('Set up, migrate, and optimize monorepos').

Add common synonyms or file/extension cues to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and concrete tools (Nx, Turborepo, Bazel, Lerna) but the actions are generic expertise claims ('Expert in', 'Masters') rather than specific actions like setup, migrate, or optimize.

2 / 5

Completeness

The 'what' is clearly stated, but the 'when' clause is truncated mid-phrase ('Use PROACTIVELY for monorepo setup,'), leaving the trigger guidance incomplete and weakly specified.

3 / 5

Trigger Term Quality

Includes natural user-facing terms ('monorepo', 'monorepo setup') and the named tools (Nx, Turborepo, Bazel, Lerna) that users would say, with a 'Use PROACTIVELY for' trigger clause, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (monorepo architecture) with distinct tool-name triggers that minimize conflict risk, though the broad 'monorepo setup' phrasing leaves minor overlap with general tooling skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.