CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

enterprise-submodule

Set up, update and change the enterprise submodule (`.source/`) and the enterprise packages (`enterprise/packages/*`), including the matching packages-enterprise PR. Use when touching enterprise code or when the submodule needs to be initialized or updated.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A well-structured, highly actionable skill body: nearly every step is a concrete executable command, workflows are clearly sequenced with ordering rationale and a permission-failure fallback, and troubleshooting covers real error messages. Minor improvements are possible: the opening line duplicates the description, Key Points repeats Overview facts, and the multi-PR workflow lacks explicit verification checkpoints.

Suggestions

Remove the opening paragraph that restates the frontmatter description, and merge the 'Key Points' facts about `.source` and symlinks into the Overview to eliminate duplication.

Add explicit verification checkpoints in the 'Making Changes' workflow, e.g., confirm the submodule is on a branch (not detached HEAD) after pulling, and verify symlinks exist after `pnpm install:with-ee` before committing.

Consider moving the Troubleshooting section into a references file to keep SKILL.md focused on the core setup and change workflows.

DimensionReasoningScore

Conciseness

The body is dominated by lean, executable commands with little concept explanation, but the opening line ("Use this skill when making changes to the enterprise submodule...") duplicates the frontmatter description, and "Key Points" re-states Overview facts ("The `.source` directory contains the actual enterprise source code", symlink descriptions). These minor redundancies keep it at anchor 4 rather than 5.

4 / 5

Actionability

Guidance is fully executable and copy-paste ready: exact commands like `git submodule update --init --recursive`, `git config --global url."https://github.com/".insteadOf "git@github.com:"`, `pnpm install:with-ee`, and `gh pr create --repo novuhq/packages-enterprise --head <branch-name> --base next`, plus a concrete compare-URL fallback for permission failures. This matches anchor 5's complete, specific commands covering common cases.

5 / 5

Workflow Clarity

The "Making Changes in the Submodule" workflow is a clearly sequenced 9-step list with explicit ordering rationale ("Commit in the **submodule first**", "**Merge the submodule PR first**... to avoid broken builds") and a failure fallback, matching anchor 4. It falls short of anchor 5 because there are no explicit validate-then-proceed checkpoints (e.g., verifying the submodule is on a branch rather than detached HEAD after a pull is only a parenthetical note).

4 / 5

Progressive Disclosure

Well-organized sections (Overview, Initial Setup, Pulling Changes, Making Changes, Troubleshooting, Key Points) with all content directly relevant to the workflow and no external references needed. The body is ~84 lines — above the under-50-line simple-skill threshold that would justify a 5 — and sections like Troubleshooting could plausibly live in a reference file, so anchor 4 fits best.

4 / 5

Total

17

/

20

Passed

Description

87%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.

A strong description that clearly states concrete capabilities and an explicit 'Use when...' trigger clause tied to a well-defined niche. Trigger coverage is good though not exhaustive of synonyms (e.g., 'EE', 'enterprise edition').

DimensionReasoningScore

Specificity

Lists several concrete actions with named targets — "Set up, update and change the enterprise submodule (`.source/`)" and "including the matching packages-enterprise PR" — but coverage has minor gaps (e.g., troubleshooting, symlink handling, env configuration are not mentioned). It exceeds anchor 3 because more than 1-2 specific actions are named, but is not comprehensive enough for anchor 5.

4 / 5

Completeness

Explicitly answers both questions: the what ("Set up, update and change the enterprise submodule... and the enterprise packages... including the matching packages-enterprise PR") and the when ("Use when touching enterprise code or when the submodule needs to be initialized or updated"). This matches the anchor 5 pattern of a clear capability list followed by concrete trigger phrases, and clearly exceeds anchor 4's less-specific 'when'.

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms a contributor would say: "enterprise code", "enterprise submodule", "enterprise packages", "submodule needs to be initialized or updated". A few natural variants are missing (e.g., "EE", "enterprise edition", "private packages"), which keeps it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — Novu's `.source` submodule pointing to packages-enterprise and `enterprise/packages/*` — with distinct triggers that no generic skill would match. Conflict risk is minimal, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

novuhq/novu

Path

.agents/skills/enterprise-submodule/SKILL.md

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.