CtrlK
BlogDocsLog inGet started
Tessl Logo

speckit-constitution

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

67

1.61x
Quality

58%

Does it follow best practices?

Impact

76%

1.61x

Average score across 3 eval scenarios

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/speckit-constitution/SKILL.md

The canonical home for this skill is speckit-constitution in unoplatform/uno

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 content is a well-sequenced, actionable instruction set with explicit validation and checklists, making it strong on actionability and workflow clarity. It loses points for verbosity (semver re-explanation, duplicated hook sections) and for keeping all detail inline with no progressive disclosure.

Suggestions

Externalize the shared hook-handling logic into a reference file and reference it once from both Pre- and Post-Execution Checks to remove the verbatim duplication.

Replace the MAJOR/MINOR/PATCH semantic-versioning explanation with a brief pointer (e.g., "bump CONSTITUTION_VERSION per semver") since Claude already knows semver.

Add an explicit "if validation fails, fix and re-run from step 3" feedback loop in step 6 to reach full workflow-clarity maturity.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but it explains semantic-versioning rules Claude already knows and duplicates the Pre-Execution and Post-Execution hook handling sections almost verbatim, adding padding.

3 / 5

Actionability

Concrete file paths (`.specify/memory/constitution.md`), exact placeholder tokens, copy-paste hook output templates, and a specific validation checklist make the guidance mostly executable with only minor gaps.

4 / 5

Workflow Clarity

A clear 8-step sequence with an explicit validation step (step 6) and consistency-propagation checklist is present; the error-recovery feedback loop (fix and re-validate) is less explicit than ideal, keeping it below 5.

4 / 5

Progressive Disclosure

Section headers are clear, but the skill is over 50 lines with no external references and inlines the bulky, duplicated hook-handling machinery that would fit better in a separate reference file.

3 / 5

Total

14

/

20

Passed

Description

53%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 clearly states what the skill does and occupies a distinct niche, but it lacks an explicit "Use when..." trigger clause and is missing natural keyword synonyms, which together cap its completeness and trigger-term quality. Specificity is adequate but not comprehensive.

Suggestions

Add an explicit "Use when..." clause stating when Claude should invoke this skill (e.g., when the user asks to create, amend, or sync the project constitution/principles).

Include natural trigger synonyms such as "governance", "values", "charter", or "guidelines" so the description matches varied user phrasings.

Tighten the sync clause into a more concrete action (e.g., "propagates amendments to plan, spec, and task templates") to lift specificity.

DimensionReasoningScore

Specificity

"Create or update the project constitution" and "ensuring all dependent templates stay in sync" name the domain and a couple concrete actions, but the sync clause is somewhat abstract and coverage is not comprehensive.

3 / 5

Completeness

The "what" is clear (create/update constitution, sync templates) but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3.

3 / 5

Trigger Term Quality

"constitution", "principle", and "templates" are relevant keywords, but common variations users might say (governance, values, charter, guidelines) are missing.

3 / 5

Distinctiveness Conflict Risk

"project constitution" plus "dependent templates" defines a clear niche that is mostly distinct, with only minor overlap risk against closely related spec-kit skills.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
mixpanel/mixpanel-headless
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.