write-vibe-adr

Create or update Architecture Decision Records for the Mistral Vibe Python CLI. Use when a design discussion creates a new architectural constraint, when an undocumented convention causes confusion or review feedback, or when architecture guidance in docs/adr or AGENTS.md must be changed.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

90%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 tight, highly actionable instruction skill with a clear multi-step workflow, concrete templates, and a helpful mistakes checklist. It is concise and well-structured, with only minor room to add an explicit verification checkpoint and avoid hardcoding the ADR index.

Suggestions

Add an explicit validation checkpoint in the workflow (e.g., after step 4, verify the AGENTS.md row resolves to the new file and the ADR matches the 20-50 line style) to close the feedback-loop gap.

Replace the hardcoded existing-ADR list (0001-0008) with guidance to derive it from `ls docs/adr/` to avoid stale content as the ADR set grows.

Consider a brief "split vs. single ADR" decision rule with one concrete example to make the scope step more executable.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive ("Keep ADRs concise. Match the existing 20-50 line style. Do not add a status field.") with no padding or explanation of concepts Claude already knows; every section earns its tokens.	5 / 5
Actionability	It provides copy-paste-ready guidance: a concrete command (`ls docs/adr/`), an exact filename pattern (`0009-my-decision.md`), a full ADR markdown template, a table-row format for AGENTS.md, and good/bad trigger examples.	5 / 5
Workflow Clarity	A clear four-step sequence (confirm scope, determine number, write, register) is present with the `ls` check as a checkpoint and a Common Mistakes table acting as a review checklist, but there is no explicit validate-then-fix feedback loop.	4 / 5
Progressive Disclosure	Single SKILL.md with well-organized sections (When To Create, Steps, Common Mistakes) and no unnecessary external references; the hardcoded existing-ADR list (0001-0008) is inline content that could go stale, keeping it just short of the top anchor.	4 / 5
	Total	18 / 20 Passed

Description

82%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, third-person description that clearly states a specific capability and pairs it with explicit, concrete trigger conditions tied to a well-scoped niche. It answers both what and when without verbosity or over-claiming.

Dimension	Reasoning	Score
Specificity	"Create or update Architecture Decision Records" names two concrete actions within a specific domain; it lists a couple specific actions rather than several, but they are concrete and domain-bound so it sits noticeably above the 1-2 action anchor.	4 / 5
Completeness	It explicitly answers both what ("Create or update Architecture Decision Records for the Mistral Vibe Python CLI") and when (an explicit "Use when" clause with three concrete trigger scenarios), matching the top anchor.	5 / 5
Trigger Term Quality	The "Use when" clause surfaces natural phrases like "design discussion creates a new architectural constraint", "undocumented convention causes confusion or review feedback", and "architecture guidance in docs/adr or AGENTS.md must be changed" — good keyword coverage with only minor synonyms missing.	4 / 5
Distinctiveness Conflict Risk	The niche is tightly scoped to ADRs for the Mistral Vibe Python CLI with distinct triggers referencing docs/adr and AGENTS.md, giving minimal overlap with other skills.	5 / 5
	Total	18 / 20 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
relative_links	Relative link issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: mistralai/mistral-vibe
Path: .vibe/skills/write-vibe-adr/SKILL.md
Commit: a84be03

Reviewed: 5 days 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.