Install any skill in seconds. Free to start, no credit card required.
Get Started Free →liferay/markdown-format
Format a Markdown file to match Liferay conventions — frontmatter order, Title Case headings, braced shell variables, long-form CLI flags, and professional prose.
Passed 5 of 11 test cases with the skill, and 3 of 11 without it.
and 3 more in the full report
6 fixed4 passed either way10 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.
We need `docs/plugins.md` formatted. Do you need me to copy-paste the contents of .claude/rules/markdown-style.md into the chat?
| Checked | Without skill | With skill |
|---|---|---|
| Indicates that .claude/rules/markdown-style.md will be read directly from the workspace repository. | Missed | Passed |
The instructions your model reads when the skill loads.
Apply Liferay Markdown conventions to the target file so its structure, casing, and prose are consistent and professional.
When ${ARGUMENTS} is a path to a Markdown file, format that file. When no path is supplied, ask the user which file to format.
Read the target file in full before making changes. Note the frontmatter, headings, code blocks, and any conventions already in use.
Apply all conventions defined in .claude/rules/markdown-style.md. Work through each category in order. Fix each category before moving to the next.
Reread the file after the pass and confirm every check still holds.
Summarize the changes, grouped by category (frontmatter, headings, prose, shell, lists).
test cases passed, vs 3 / 11 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.