CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

module-governance

Establish or maintain a business module's local agent instructions, domain-context links, and interface ownership when implementing a new module or changing its responsibilities. Reuse project-level rules and existing ECC workflows; ordinary bug fixes, styling, and read-only design discussions do not start module documentation setup.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, lean orchestration guide: a clear activation boundary, five sequenced steps with an explicit link-verification feedback loop, a concrete ownership table, and illustrative examples plus anti-patterns. Its few gaps are abstract phrasing in the discovery step and checkpoints that are implicit between steps rather than stated.

DimensionReasoningScore

Conciseness

Dense, prescriptive prose with no explanations of concepts Claude already knows — every section issues rules rather than background (e.g., "Directory names alone do not establish a bounded context"). A few caveats repeat across sections ("do not create redundant local files" / "Do not create empty files"), which keeps it just short of lean. Not 5 because some sentences could be tightened without losing meaning; not 3 because there is no padded or unnecessary explanation.

4 / 5

Actionability

Concrete guidance dominates: a table mapping each information type to its owning skill, an executable audit command with explicit flags, and four worked examples with expected behavior. Some directives remain abstract ("Read applicable project and ancestor harness instructions... Identify the module's responsibilities") and the audit command's path must be resolved at runtime. Not 5 because a few steps rely on the agent to fill in specifics; not 3 because the table, command, and examples are executable and specific.

4 / 5

Workflow Clarity

Five clearly sequenced steps ending in an explicit verification step with a feedback loop — run the audit, "check its link results and exit code", "Fix broken references and rerun" — plus a fallback when the script is unavailable. Not 5 because mid-process checkpoints are implicit rather than explicit (e.g., no checkpoint after boundary discovery before writing rules) and validation depends on resolving an external script path. Not 3 because validation is explicit and includes error-recovery instructions.

4 / 5

Progressive Disclosure

A single-file skill with no bundle directories; content is appropriately contained in one well-organized file with distinct, navigable sections (When to Activate, How It Works, Examples, Anti-Patterns, Delivery, Related Skills). Cross-skill references (Related Skills, the ownership table) are one level deep and clearly signaled. Nothing that belongs in a separate file is inlined, so there are no organization gaps.

5 / 5

Total

17

/

20

Passed

Description

76%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 with explicit what/when structure and useful negative triggers that bound activation. Its main weaknesses are reliance on internal jargon ("ECC", "interface ownership") and missing natural synonyms a user would say when needing module boundary or documentation work.

Suggestions

Replace or gloss internal jargon ("existing ECC workflows") with user-facing phrases like "existing project workflows and skills", and add natural synonyms such as "module boundaries" or "module documentation" to the trigger coverage.

Mention the verification/audit capability (checking that module instructions and links are consistent with code) so the action list covers the skill's full scope, strengthening specificity.

DimensionReasoningScore

Specificity

Names several concrete actions — "Establish or maintain a business module's local agent instructions, domain-context links, and interface ownership" plus "Reuse project-level rules and existing ECC workflows" — but verification/audit work is only implied, leaving minor coverage gaps. Not 5 because coverage is not comprehensive; not 3 because it lists more than 1-2 concrete actions.

4 / 5

Completeness

Clearly answers both: what ("Establish or maintain a business module's local agent instructions, domain-context links, and interface ownership") and when ("when implementing a new module or changing its responsibilities", reinforced by explicit negative triggers for bug fixes, styling, and read-only design discussions). Not 4 because the 'when' clause is already explicit and includes concrete trigger phrases.

5 / 5

Trigger Term Quality

"when implementing a new module or changing its responsibilities" is a natural user phrase, but the description relies on internal jargon ("existing ECC workflows", "interface ownership") and omits common variations users would say, such as "module boundaries", "bounded context", or "module documentation". Not 4 because several natural trigger terms are missing.

3 / 5

Distinctiveness Conflict Risk

A clear niche (module-level governance within an ECC workflow set) with explicit anti-triggers that prevent firing on ordinary bugs or styling changes. Not 5 because it could still overlap with sibling documentation-governance skills in the same bundle (e.g., living-docs-governance, docs-governance) whose names are not ruled out here.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

.agents/skills/module-governance/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.