Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/htmx-js-api
Use the htmx JavaScript API for imperative integration in server-rendered apps.
Passed 23 of 23 test cases with the skill, and 21 of 23 without it.
2 fixed21 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
After finishing a local debugging session where verbose console output was enabled in htmx, what htmx API function should be invoked to turn off all htmx logging before pushing code to production?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends using htmx.logNone to turn off logging. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when declarative attributes are not enough. Prefer attributes first; reach for the JavaScript API to integrate with third-party widgets, dynamically injected markup, instrumentation, or programmatic request flows.
Use htmx attributes when the behavior is visible in the HTML and tied to one element. Use the JS API when:
Set global config once before relying on htmx behavior. Common examples:
htmx-security.Keep config close to where htmx is loaded so there is one source of truth.
Use htmx DOM helpers for concise integration code:
| Need | Methods |
|---|---|
| Find one element | htmx.find, htmx.closest |
| Find many elements | htmx.findAll |
| Remove an element | htmx.remove |
| Add a class | htmx.addClass |
| Remove a class | htmx.removeClass |
| Toggle a class | htmx.toggleClass |
| Make one element selected | htmx.takeClass |
test cases passed, vs 21 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.