cli-logging-ux

Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (_rich_success, _rich_warning, _rich_error, _rich_info, _rich_echo), DiagnosticCollector, STATUS_SYMBOLS, CommandLogger, or any user-facing terminal output — even if the user doesn't mention "logging" or "UX" explicitly.

Quality

88%

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

77%Weight 40%Scale 1-3

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

A highly actionable, well-structured skill body packed with codebase-specific knowledge and executable patterns. Its main weaknesses are repetition of a few rules/structures and a large inline reference section that would benefit from offloading to bundle files.

Suggestions

Deduplicate the no-emoji rule (currently stated at lines 100, 320, and via symbols at 322) into a single authoritative statement and cross-reference it elsewhere.

Merge the duplicate multi-package tree diagrams ("Output structure pattern" and "Visual hierarchy contract") into one canonical example to recover tokens.

Move the CommandLogger/InstallLogger method reference tables into a references/ file (e.g. COMMAND_LOGGER_API.md) and keep SKILL.md as a concise overview with a clearly signaled one-level-deep link.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and project-specific (no generic CLI basics padding), but it repeats itself: the no-emoji rule appears three times and the multi-package tree structure appears twice ("Output structure pattern" and "Visual hierarchy contract"), so it could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready guidance: exact import statements, helper signatures, a CommandLogger instantiation example, and method tables with concrete rendered outputs.	3 / 3
Workflow Clarity	The three-test decision framework ("So What?", Traffic Light, Newspaper) is a clearly sequenced evaluation process with explicit pass/fail criteria ("If a message fails any test, redesign it"), and "When to add a new logger method" gives concrete decision signals.	3 / 3
Progressive Disclosure	Sections are well organized, but the ~160-line CommandLogger API reference is inline and no bundle files exist to offload it; the linked persona target (../../.apm/agents/cli-logging-expert.agent.md) is also absent, so reference material is not split out.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, specific description that clearly states capabilities, natural trigger terms, and explicit activation conditions scoped to a distinct codebase niche. It avoids vague fluff and over-claims entirely.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ("editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries") and enumerates specific code symbols (_rich_success, DiagnosticCollector, CommandLogger), going well beyond naming a domain.	3 / 3
Completeness	Explicitly answers both "what" (editing/creating CLI output, logging, warnings) and "when" via clear trigger clauses ("Use this skill when...", "Activate whenever code touches...").	3 / 3
Trigger Term Quality	Uses natural terms users would actually say ("CLI output", "logging", "warnings", "error messages") alongside explicit activation triggers, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to the APM codebase with distinctive codebase-specific symbols (CommandLogger, DiagnosticCollector, STATUS_SYMBOLS, _rich_* helpers), creating a clear niche unlikely to conflict with generic skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: microsoft/apm
Path: .agents/skills/cli-logging-ux/SKILL.md
Commit: 634f7b6

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