packmind-create-standard

Guide for creating coding standards via the Packmind CLI. This skill should be used when users want to create a new coding standard (or add rules to an existing standard) that captures team conventions, best practices, or coding guidelines for distribution to Claude.

Install with Tessl CLI

npx tessl i github:cteyton/packmind --skill packmind-create-standard

What are skills?

Review — 76%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 14 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description effectively communicates when to use the skill with explicit trigger conditions and has a distinct niche due to the Packmind CLI focus. However, it could benefit from more specific concrete actions (what exactly does creating a standard involve?) and broader trigger term coverage to catch more natural user phrasings.

Suggestions

Add more specific concrete actions like 'define naming conventions, document code patterns, specify formatting rules, export standards'

Expand trigger terms to include variations like 'style guide', 'code rules', 'team standards', 'linting', or 'code conventions'

Dimension	Reasoning	Score
Specificity	Names the domain (coding standards via Packmind CLI) and mentions actions like 'creating' and 'add rules', but lacks comprehensive concrete actions like specific operations or outputs.	2 / 3
Completeness	Clearly answers both what ('creating coding standards via Packmind CLI') and when ('when users want to create a new coding standard or add rules to an existing standard'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes relevant terms like 'coding standard', 'rules', 'conventions', 'best practices', 'coding guidelines', but misses common variations users might say like 'style guide', 'code rules', 'linting rules', or 'team standards'.	2 / 3
Distinctiveness Conflict Risk	The specific mention of 'Packmind CLI' and the focus on 'coding standards for distribution to Claude' creates a clear niche that is unlikely to conflict with general coding or documentation skills.	3 / 3
	Total	10 / 12 Passed

Implementation

77%

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

This is a well-structured, highly actionable skill with excellent workflow clarity including validation checkpoints and user approval gates. The main weakness is verbosity - the introductory sections explaining what standards are and their benefits add ~100 lines that Claude doesn't need. The content would benefit from splitting reference material (JSON schema, language values, field descriptions) into a separate file.

Suggestions

Remove or drastically shorten the 'About Coding Standards' and 'What Standards Provide' sections - Claude understands these concepts

Move the JSON schema reference, valid language values list, and Quick Reference table to a separate REFERENCE.md file

Consolidate the duplicate 'Valid language values' lists (appears in both Step 3 and Step 4) into a single reference

Dimension	Reasoning	Score
Conciseness	The skill contains some unnecessary explanations (e.g., 'What Standards Provide' section explaining benefits Claude already understands, verbose 'About Coding Standards' intro). The content could be tightened significantly while preserving all actionable guidance.	2 / 3
Actionability	Provides fully executable commands, complete JSON schemas, concrete examples with valid/invalid patterns, and copy-paste ready CLI commands. The complete example at the end demonstrates exactly what to produce.	3 / 3
Workflow Clarity	Excellent 8-step workflow with explicit validation checkpoints (Step 5 requires user approval, Step 6 re-reads and compares files, cleanup only on success). Includes clear feedback loops for error recovery and troubleshooting section.	3 / 3
Progressive Disclosure	Content is well-structured with clear sections, but the skill is monolithic (~400 lines) with no references to external files. The 'About Coding Standards' and 'Standard Structure' sections could be moved to a reference file, keeping SKILL.md focused on the workflow.	2 / 3
	Total	10 / 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
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning

	Total	14 / 16 Passed

Reviewed: 22 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.