Name: poshi-shrink
Rating: 69.6 (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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

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

A dense, expert-level playbook with excellent actionability and token efficiency: exact paths, templates, commit formats, and explicit DO/DO NOT decision rules. The main gap is the absence of a verification step after destructive merges, and no defined source for the <TICKET> placeholder used in every commit message.

Suggestions

Add a validation checkpoint after each merge — e.g., re-parse or syntax-check the shrunk .testcase file before committing, and only commit when it passes — to satisfy the destructive/batch feedback-loop requirement.

Define where <TICKET> comes from (a required input, git branch name, or a prompt to the user) since it appears in every commit message format but is never resolved.

Consider moving the merge-signal catalogs (DO/DO NOT lists and common patterns) to a references/ file, keeping SKILL.md as the workflow overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence throughout — no explanation of what Poshi or Liferay is, no library background; every line is an instruction, a decision rule, or a concrete template. Nothing reads as padding.	5 / 5
Actionability	Fully concrete guidance: exact scan paths (portal-web/test/functional/com/liferay/portalweb/tests/enduser), a copy-ready plan template, exact commit message formats ("<TICKET> Rename test <Keeper> to <FinalName>"), and real assertion examples (AssertTextEquals.assertPartialText("web/<site-path>") vs AssertVisible value1="http://").	5 / 5
Workflow Clarity	The sequence is coherent with pre-operation checkpoints (clean-tree precondition, enumeration abort, plan-mode approval gate), but this is a destructive batch workflow — deleting test blocks and committing per operation — with no post-operation validation (e.g., syntax-check or run the shrunk .testcase file before/after committing), which caps it at 3 per the destructive/batch rule.	3 / 5
Progressive Disclosure	No bundle files exist, and the ~93-line body is well organized with clear headers (Preconditions, Input, Expected Output with plan template and DO/DO NOT signals, Summary). At this length the merge-signal catalogs and plan template would sit equally well in a one-level reference file, which keeps it just below the top anchor's structure.	4 / 5
	Total	17 / 20 Passed

Description

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

A tight, third-person description that states a concrete capability and an explicit trigger clause with natural user verbs. The only weakness is a handful of missing synonyms (deduplicate, consolidate, shrink) in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain precisely ("Liferay component's Poshi test suite") and several concrete actions — shrink, merge overlapping tests, plus reduce/clean up in the trigger clause — with minor gaps (rename and per-merge commit granularity are only visible in the body).	4 / 5
Completeness	Explicitly answers 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 rather than a weakly implied when.	5 / 5
Trigger Term Quality	"Use when the user asks to reduce, merge, or clean up Poshi tests" covers the natural verbs a user would say, but misses common synonyms like "deduplicate", "consolidate", or "shrink" itself as a trigger phrase.	4 / 5
Distinctiveness Conflict Risk	"Poshi" and "Liferay component" carve out a clear niche that no generic test-refactoring or cleanup skill would claim, and the @component-name trigger is unambiguous — minimal conflict risk.	5 / 5
	Total	18 / 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: 6047723

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.