CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A well-structured, action-dense playbook with explicit sequencing, validation gates (clean tree, component enumeration, plan approval), and copy-ready commit templates. It assumes Claude's intelligence and stays concise. No bundle files are referenced, so progressive disclosure scores via clean section organization.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it states outcomes, preconditions, and rules without padding or re-explaining what Poshi/Liferay tests are. Each token earns its place.

3 / 3

Actionability

It gives concrete, executable guidance — exact commit message templates ("<TICKET> Rename test <Keeper> to <FinalName>"), the plan-mode format, merge rules, and where to scan files — leaving little ambiguous.

3 / 3

Workflow Clarity

The process is clearly sequenced with checkpoints: clean-tree precondition, component verification/abort, plan-mode approval gate, per-operation commits, and a final summary — feedback and validation loops are explicit.

3 / 3

Progressive Disclosure

For a self-contained single-purpose skill with no bundle files, the body is well organized into Preconditions, Input, Expected Output, and Summary sections, so the simple-skill allowance applies.

3 / 3

Total

12

/

12

Passed

Description

100%

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, concise description that states concrete capabilities, explicit "Use when" triggers in natural user language, and a well-scoped Liferay/Poshi niche with low conflict risk. Third-person voice is maintained throughout. No changes needed.

DimensionReasoningScore

Specificity

It lists multiple concrete actions — "merging overlapping tests" framed against "reduce, merge, or clean up Poshi tests" for a named @component-name — rather than vague language.

3 / 3

Completeness

It 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"), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Natural user phrasings are covered explicitly: "reduce", "merge", and "clean up Poshi tests", matching how a user would ask for this shrink operation.

3 / 3

Distinctiveness Conflict Risk

The narrow Poshi/Liferay @component-name niche with domain-specific trigger terms makes it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
liferay/liferay-portal
Reviewed

Table of Contents

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.