writing-user-outputs

CLI output formatting standards for worktrunk. Use when writing user-facing messages, error handling, progress output, hints, warnings, or working with the output system.

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/writing-user-outputs/SKILL.md

Quality

Discovery

89%

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 is a solid skill description that clearly identifies its scope (CLI output formatting for worktrunk) and provides an explicit 'Use when' clause with multiple relevant trigger scenarios. Its main weakness is that the capabilities listed are somewhat categorical rather than describing specific concrete actions. The project-specific scoping and good trigger term coverage make it effective for skill selection.

Suggestions

Add more concrete action verbs to increase specificity, e.g., 'Defines formatting patterns for status messages, styles error/warning output with consistent prefixes, and structures progress indicators' instead of just listing categories.

Dimension	Reasoning	Score
Specificity	Names the domain (CLI output formatting for worktrunk) and lists several areas (user-facing messages, error handling, progress output, hints, warnings, output system), but these are categories rather than concrete actions like 'format error messages with color codes' or 'display progress bars'.	2 / 3
Completeness	Clearly answers both 'what' (CLI output formatting standards for worktrunk) and 'when' (explicit 'Use when' clause listing specific trigger scenarios: writing user-facing messages, error handling, progress output, hints, warnings, or working with the output system).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms that a user/developer would actually use: 'CLI output', 'user-facing messages', 'error handling', 'progress output', 'hints', 'warnings', 'output system'. These cover a good range of variations for when someone is working on output formatting.	3 / 3
Distinctiveness Conflict Risk	Scoped specifically to CLI output formatting for a named project 'worktrunk', which creates a clear niche. The combination of CLI output formatting standards with the specific project name makes it unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

64%

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

This is a comprehensive and highly actionable reference for CLI output formatting in the worktrunk project, with excellent concrete examples showing good/bad patterns and specific Rust code. Its main weaknesses are its monolithic length (could benefit from splitting into focused sub-documents) and the lack of a clear top-level workflow guiding developers through the decision process of adding output to a new command. The content is project-specific and valuable, but its sheer volume works against quick reference use.

Suggestions

Add a quick-reference decision flowchart or checklist at the top (e.g., 'Adding output to a new command: 1. Decide stdout vs stderr, 2. Choose message type, 3. Apply styling, 4. Add snapshot test') to improve workflow clarity.

Split the document into focused sub-files (e.g., SHELL_INTEGRATION.md, MESSAGE_PATTERNS.md, STYLING_REFERENCE.md, ERROR_FORMATTING.md) with a concise overview in the main SKILL.md linking to each.

Consolidate repeated patterns — flag acknowledgment, parenthesized content styling, and command formatting appear in multiple sections and could be unified into a single 'Message Composition' section.

Dimension	Reasoning	Score
Conciseness	The content is extensive and mostly relevant, but includes some sections that could be tightened (e.g., the Windows compatibility explanation, the lengthy prompt spacing examples). Some patterns are repeated across sections (e.g., flag acknowledgment appears in multiple places). However, most content is project-specific knowledge Claude wouldn't have, which justifies its inclusion.	2 / 3
Actionability	The skill provides highly concrete, executable Rust code examples throughout, specific function names with their modules, exact symbol/color mappings in tables, and clear good/bad comparisons. Every pattern is illustrated with copy-paste ready code and specific crate paths like `worktrunk::styling` and `worktrunk::path`.	3 / 3
Workflow Clarity	While individual patterns are clearly explained with good/bad examples, the document lacks a clear sequential workflow or decision tree for 'how to add output to a new command.' The warning ordering section and prompt type decision table are well-structured, but the overall document reads more as a reference than a guided workflow. No validation checkpoints are provided for verifying output correctness beyond mentioning snapshot tests at the end.	2 / 3
Progressive Disclosure	The document is a monolithic wall of text at ~500+ lines with no references to external files for detailed subsections. Content like documentation examples, table column alignment, and snapshot testing patterns could be split into separate reference files. Some internal cross-references exist (e.g., 'See src/git/error.rs') but the main document tries to cover everything inline rather than providing an overview with links to detailed guides.	2 / 3
	Total	9 / 12 Passed

Validation

72%

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 — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (944 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	8 / 11 Passed

Repository: max-sixty/worktrunk
Commit: 65e58d3

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