Install any skill in seconds. Free to start, no credit card required.
Get Started Free →liferay/jira-bug
Create a Jira bug ticket in the LPD project through the REST API.
Passed 7 of 18 test cases with the skill, and 3 of 18 without it.
and 6 more in the full report
8 fixed1 passed either way10 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm creating a bug ticket for LPD where the staging site publishing hangs indefinitely. What numeric ID corresponds to the default Master Affects Version?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies 16660 as the ID for Master. | Missed | Passed |
The instructions your model reads when the skill loads.
Create a bug ticket in the LPD Jira project through the REST API.
When ${ARGUMENTS} is a commit hash, inspect the commit with git show to understand the fix and infer the bug it addresses. When ${ARGUMENTS} is a free-form description, use it directly.
Request any missing details from the user:
The LPD project requires the following fields. Apply these defaults unless the user specifies otherwise:
Master (ID: 16660).customfield_10979): None (ID: 14468).Create the issue in the LPD project with the gathered summary, description, and required fields. Author the description in Atlassian Document Format (ADF) with the following sections, in order: Description, Steps to Reproduce, Expected Behavior, Actual Behavior. Append a Fix section when a commit is referenced.
The ticket key and the browse URL: https://liferay.atlassian.net/browse/<KEY>.
test cases passed, vs 3 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.