Name: poshi-shrink
Rating: 68 (1 reviews)
Author: liferay

poshi-shrink

Shrink a Liferay component's Poshi test suite by merging overlapping tests. Use when the user asks to reduce, merge, or clean up Poshi tests for a @component-name.

Quality

82%

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

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

This is a tightly written, highly actionable playbook with a clear gated workflow and concrete templates for a destructive batch operation. The main gaps are a missing post-apply verification checkpoint and a large catalog of inline reference-style content that could be externalized.

Suggestions

Add an explicit post-merge verification step (e.g., run the shrunk Poshi suite and abort/fix on failures) to close the validation gap and lift workflow_clarity toward 5.

Move the 'Common merge-worthy signals' catalog and/or the full Shrink Plan template into a references file linked from the body to improve progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence without explaining Poshi/Liferay basics, with nearly every line carrying domain-specific guidance; it is not level 5 because the merge-signals catalog and plan template add length that could be trimmed or split out.	4 / 5
Actionability	Concrete, copy-paste-ready guidance is given throughout: enumeration paths, an exact markdown plan template, keeper-selection rule, and per-operation commit message templates covering the common rename/merge/cleanup cases, matching the level-5 anchor.	5 / 5
Workflow Clarity	A clear sequence runs Preconditions -> Input/verify -> Plan -> approval gate -> apply-and-commit per operation -> Summary, with explicit checkpoints (clean-tree abort, no-match abort, ExitPlanMode approval); it is not level 5 because there is no explicit post-merge verification that the suite still passes, leaving a minor validation gap.	4 / 5
Progressive Disclosure	The single SKILL.md is well organized into labeled sections with no nested references and no bundle files, fitting the level-4 anchor; it is not level 5 because the inline merge-signals catalog and plan template read like reference material that could be split into a separate file.	4 / 5
	Total	17 / 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.

The description cleanly answers both what and when with concrete, natural trigger phrases tied to a narrow, distinctive niche. It is slightly light on breadth of actions and on synonyms/file extensions, which keeps specificity and trigger_term_quality from the top band.

Suggestions

Add a couple more concrete actions (e.g., 'deletes redundant tests, renames the keeper, commits each change separately') to lift specificity toward level 4-5.

Include a natural synonym or file extension such as '.testcase files' to broaden trigger_term_quality.

Dimension	Reasoning	Score
Specificity	Names the domain ("Liferay component's Poshi test suite") and a concrete action ("shrink ... by merging overlapping tests"), giving 1-2 concrete actions without comprehensive coverage, matching the level-3 anchor; it is not level 4 because it does not list several distinct actions.	3 / 5
Completeness	It explicitly states both what ("Shrink a Liferay component's Poshi test suite by merging overlapping tests") and when ("Use when the user asks to reduce, merge, or clean up Poshi tests for a @component-name") with concrete trigger phrases, matching the level-5 anchor.	5 / 5
Trigger Term Quality	Natural user phrasings appear ("reduce, merge, or clean up Poshi tests") alongside the domain term "Poshi", giving good keyword coverage; not level 5 because synonyms and file extensions like .testcase are absent.	4 / 5
Distinctiveness Conflict Risk	The Liferay/Poshi test-shrinking niche is highly specific with distinct triggers, making conflict with other skills minimal, matching the level-5 anchor.	5 / 5
	Total	17 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: liferay/liferay-portal
Path: .claude/skills/poshi-shrink/SKILL.md
Commit: f7a0dfa

Reviewed: 37 minutes 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.