Name: poshi-migrate
Rating: 72 (1 reviews)
Author: liferay

poshi-migrate

Migrate a Liferay Poshi .testcase file to its modern test layer (Playwright, Jest, JUnit unit, Java integration). Routes each test to the right layer, consolidates compatible tests at write time, and follows existing Playwright patterns from a configurable reference folder. Use when the user asks to migrate, port, or convert a Poshi .testcase to Playwright, Jest, or JUnit.

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

85%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 content is a thorough, actionable playbook with strong sequencing and validation for destructive operations. Its main weakness is progressive disclosure: everything lives in one monolithic file with no reference files to absorb the plan template and detailed mapping tables.

Suggestions

Move the multi-section plan template (## Source through ## Commits) into a references/PLAN_TEMPLATE.md and reference it from the Plan phase, keeping only the phase intent inline.

Extract the Playwright setup mappings (Content page / Midtest login / Site / User) and the API First Setup decision tree into references/playwright-setup-mapping.md to reduce inline bulk.

Consider a references/ directory entry for the feasibility blocker list and routing layer table so the SKILL.md overview stays a concise routing guide.

Dimension	Reasoning	Score
Conciseness	Generally lean and assumes Claude's competence, avoiding basic explanations of Poshi/JUnit, though a few dense prose passages (e.g. feasibility rationale) could be tightened slightly.	4 / 5
Actionability	Provides concrete executable guidance throughout: git log --grep commands, a copy-paste TypeScript mergeTests fixture, yarn test --repeat-each=10 flake check, and a precise API-helper decision tree with file paths.	5 / 5
Workflow Clarity	Five gated phases with explicit validation checkpoints (feasibility screening, live-backend validation, flake check, commit ordering for destructive drops) and an error-recovery protocol for failed specs.	5 / 5
Progressive Disclosure	No bundle files exist and all ~400 lines are inlined in SKILL.md; the plan template, setup-mapping tables, and API-substitution decision tree are candidates to offload into reference files, though the existing one-level pointers to .claude/rules/playwright.md are well signaled.	3 / 5
	Total	17 / 20 Passed

Description

92%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 is strong: it names concrete actions, four target layers, and an explicit 'Use when...' trigger tied to natural user phrasing. It is distinct within its niche and free of vague fluff. Minor room to add a couple more synonyms, but otherwise exemplary.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — migrating, routing each test to one of four named layers, consolidating compatible tests, and following reference-folder patterns — giving comprehensive coverage of the skill's behavior.	5 / 5
Completeness	Explicitly answers 'what' (migrate/route/consolidate/follow patterns) and 'when' via a clear 'Use when the user asks to migrate, port, or convert a Poshi .testcase...' clause.	5 / 5
Trigger Term Quality	Includes natural user verbs (migrate, port, convert) plus the .testcase extension and target layer names, but lacks a few common synonyms a user might say beyond 'convert'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Liferay Poshi migration) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	19 / 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-migrate/SKILL.md
Commit: f7a0dfa

Reviewed: ~2 hours 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.