alonso-skills/htmx
Implements HTMX interactions, configures swap behaviors, debugs hx-* requests, and builds hypermedia-driven UI components. Use when tasks involve hx-* attributes, HTMX AJAX requests, swap strategies, server-sent events, WebSockets, or hypermedia-driven UIs.
95
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, includes a comprehensive set of natural trigger terms that developers would actually use, has an explicit 'Use when...' clause, and targets a clearly distinct technology niche (HTMX) that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Implements HTMX interactions', 'configures swap behaviors', 'debugs hx-* requests', and 'builds hypermedia-driven UI components'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (implements interactions, configures swap behaviors, debugs requests, builds components) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would use: 'hx-* attributes', 'HTMX AJAX requests', 'swap strategies', 'server-sent events', 'WebSockets', 'hypermedia-driven UIs'. These are the exact terms developers would mention when working with HTMX. | 3 / 3 |
Distinctiveness Conflict Risk | HTMX is a very specific technology niche. The triggers like 'hx-* attributes', 'swap strategies', and 'hypermedia-driven UIs' are highly distinctive and unlikely to conflict with general frontend or backend skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong HTMX skill with excellent conciseness, actionability, and progressive disclosure. The critical rules section is particularly valuable, containing dense, non-obvious guidance that Claude wouldn't inherently know. The main weakness is the workflow clarity around validation and debugging — the skill could benefit from a slightly more explicit verification step for common failure modes.
Suggestions
Strengthen the validation step in Quick Start with a concrete check, e.g., 'Verify the response Content-Type is text/html and contains no <html>/<body> wrappers — use the htmx:afterRequest event or browser devtools Network tab to inspect.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what HTMX is or how HTML works, assumes Claude's competence, and every section serves a clear purpose. The critical rules are dense with non-obvious, actionable information (e.g., HTTP 286 for polling, non-inherited attributes, htmx:beforeSwap for error swaps). | 3 / 3 |
Actionability | Provides a fully executable HTML example with both client-side markup and expected server response. The critical rules contain specific, concrete guidance (exact attribute names, status codes, header names) rather than vague descriptions. The quick start is copy-paste ready. | 3 / 3 |
Workflow Clarity | The quick start provides a 4-step sequence, but the validation step ('Validate that server responses return HTML fragments, not JSON') is vague — it doesn't specify how to validate (e.g., check Content-Type header, inspect response in browser devtools, use htmx:afterRequest event). For a skill involving server-client interactions where debugging is common, a more explicit validation/debugging checkpoint would strengthen this. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview, concise quick start, and well-organized reference map with one-level-deep references. The task routing section provides clear navigation for different use cases, making it easy to find the right reference file without chain-following. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents