packmind-cli-list-commands

Reference for Packmind CLI listing commands. This skill should be used when an agent needs to discover available standards, commands, or skills in the Packmind organization.

Quality

81%

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

100%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.

The body is an exemplary lean, single-purpose CLI skill: concrete commands, an explicit auth checkpoint, and precise output-format requirements with an example. Nothing is inlined that belongs in a separate file and no padding exists.

Dimension	Reasoning	Score
Conciseness	The ~49-line body is lean and assumes Claude's competence: no conceptual explanation, just output-format rules, a 4-row command table, and a two-command auth check. Every section earns its place, matching 'lean and efficient; every token earns its place'.	5 / 5
Actionability	Fully executable, copy-paste ready guidance: four concrete list commands, 'packmind-cli whoami' as an auth check, 'packmind-cli login' as the remediation, and a concrete output template showing slug, name, and full URL. This matches the top anchor.	5 / 5
Workflow Clarity	This is a simple single-purpose skill whose action is unambiguous: verify auth (whoami → login if needed), run the list command, present results in the required format. The auth prerequisite serves as an explicit validation checkpoint, and the operation is read-only so no validation cap applies.	5 / 5
Progressive Disclosure	Under 50 lines with no external references needed (no references/, scripts/, or assets/ files exist), and the content is well-organized into Output Requirements, Commands Reference, and Prerequisites sections. Per the simple-skill guideline, this earns the top score.	5 / 5
	Total	20 / 20 Passed

Description

62%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.

The description clearly answers both what the skill does and when to use it, and the Packmind scoping keeps conflict risk low. It is held back by limited action coverage and missing natural trigger phrasings that would make discovery more reliable.

Suggestions

Enumerate the concrete actions more fully, e.g. 'List coding standards, reusable commands, skills, and packages available in the Packmind organization via packmind-cli, with clickable webapp links for each item.'

Add natural trigger phrasings users would actually say, such as 'Use when the user asks to list, show, or discover Packmind standards, commands, skills, or packages, or wonders what is available in the organization.'

Make the 'when' clause scenario-specific rather than capability-generic, e.g. 'Use when preparing to apply an organizational standard or deciding which existing skill/command to reuse.'

Dimension	Reasoning	Score
Specificity	"Reference for Packmind CLI listing commands" names the domain and pairs it with 1-2 concrete actions ("discover available standards, commands, or skills"), but coverage is not comprehensive. It fits the 'names domain and 1-2 concrete actions' anchor — above the bare-domain level 2, below the 'several specific actions' level 4.	3 / 5
Completeness	Both parts are present: a 'what' ("Reference for Packmind CLI listing commands") and an explicit 'when' ("This skill should be used when an agent needs to discover available standards, commands, or skills"). The 'what' is somewhat thin and the 'when' lacks concrete trigger phrases, so it sits at 'both present but could be more explicit', not the fully explicit level 5.	4 / 5
Trigger Term Quality	Relevant keywords exist ("listing commands", "standards, commands, or skills", "Packmind organization") but common natural phrasings users would say ("show available skills", "what standards exist", "list our commands") and synonyms are missing. This matches 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	"Packmind" carves out a clear niche with distinct triggers, but the generic terms "commands" and "skills" leave minor overlap risk with other listing/discovery skills. It matches 'mostly distinct; minor overlap risk', short of the minimal-conflict level 5.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: cteyton/packmind
Path: skills/skills/packmind-cli-list-commands/SKILL.md
Commit: e198635

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.