Install any skill in seconds. Free to start, no credit card required.
Get Started Free →liferay/jira-task
Create a Jira task in the LPD project through the REST API.
Passed 12 of 17 test cases with the skill, and 9 of 17 without it.
and 4 more in the full report
7 fixed9 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
When returning the browse link for a newly created LPD task ticket, which base URL domain structure must be used instead of standard jira.company.com?
| Checked | Without skill | With skill |
|---|---|---|
| The base URL domain is liferay.atlassian.net. | Missed | Passed |
The instructions your model reads when the skill loads.
Create a task 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 work and infer the task. 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:
Task (ID: 10002).Note: Unlike bugs, tasks do not require the Affects Version or Cross Cutting Properties fields.
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, Acceptance Criteria (when applicable). Append a Reference section when a commit is referenced.
The ticket key and the browse URL: https://liferay.atlassian.net/browse/<KEY>.
test cases passed, vs 9 / 17 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.