speckit-constitution

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

1.61x

Quality

63%

Does it follow best practices?

Impact

76%

1.61x

Average score across 3 eval scenarios

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

77%

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

A strong, highly actionable instruction-only skill with a clear sequenced workflow and explicit validation. The main weaknesses are duplicated hook-handling prose hurting conciseness and a monolithic structure with no progressive disclosure via reference files.

Suggestions

De-duplicate the pre- and post-execution hook blocks into a single shared procedure referenced by both checkpoints to recover token budget.

Extract the hook-handling rules (extensions.yml parsing, enabled/optional/condition handling, slash-command dot-to-hyphen conversion) into a reference file referenced one level deep, keeping SKILL.md as an overview.

Consider moving the detailed template-filling and consistency-propagation checklist into a separate reference so the main body reads as a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly procedural and actionable without padding concepts Claude already knows, but the pre- and post-execution hook blocks are near-verbatim duplicates, which wastes tokens and could be tightened by referencing a single shared procedure.	2 / 3
Actionability	Provides concrete file paths, placeholder token forms, semantic-versioning rules, a literal Sync Impact Report structure, hook output templates, and a suggested commit message format — copy-paste ready guidance throughout.	3 / 3
Workflow Clarity	An eight-step sequenced workflow with an explicit validation checkpoint (step 6), a consistency-propagation checklist (step 4), version-bump reasoning, and feedback loops for ambiguous versions and missing critical info.	3 / 3
Progressive Disclosure	Content is well-organized into sections (User Input, Pre/Post-Execution Checks, Outline), but at ~145 lines with no bundle files the hook-handling and template-filling logic is inline monolithically rather than split into one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 conveys a clear domain and core actions but is missing an explicit use-when trigger clause, leaving all dimensions at the mid-level. Adding natural trigger terms and a 'Use when...' clause would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when creating or amending the project constitution, defining project principles, or syncing dependent spec-kit templates').

Broaden natural trigger terms to include variations a user would actually say, such as 'governance', 'project principles', 'amend constitution', or 'ratify'.

List more concrete distinct actions (e.g., 'fill constitution template placeholders, bump the constitution version, propagate amendments to plan/spec/tasks templates') to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('project constitution') and actions ('Create or update', 'ensuring all dependent templates stay in sync'), but the action set is limited to create/update plus a secondary sync outcome rather than a comprehensive list of concrete actions.	2 / 3
Completeness	Clearly answers 'what' (create/update constitution, sync dependent templates) but the 'when' is missing with no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Contains some relevant natural terms ('constitution', 'principle inputs'), but 'interactive or provided principle inputs' is somewhat technical and there is no explicit trigger phrase or coverage of common variations users would say.	2 / 3
Distinctiveness Conflict Risk	The project constitution niche is fairly distinct, but the absence of explicit distinct triggers and the generic reference to 'dependent templates' means it could still overlap with other spec-kit template-management skills.	2 / 3
	Total	8 / 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
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: unoplatform/uno
Path: .claude/skills/speckit-constitution/SKILL.md
Commit: 5927220

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