CtrlK
BlogDocsLog inGet started
Tessl Logo

engram-dashboard-htmx

HTMX and templ interaction rules for the Engram dashboard. Trigger: Any change to htmx attributes, partial updates, forms, or server-rendered browser UI.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, well-organized ruleset that respects token budget and needs no external references. Its weakness is actionability and workflow clarity: rules are stated as principles without executable examples or validation/verification steps for state-mutating operations.

Suggestions

Add a short concrete example showing the expected htmx pattern (e.g., a form using hx-post with hx-swap) to move actionability from 2 to 3.

Add a verification step for state-mutating forms (e.g., 'confirm the endpoint still accepts a plain POST and returns meaningful HTML') to support workflow clarity.

Keep the terse imperative style and section structure; they already support conciseness and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is short and lean, listing rules as terse imperatives ('Server-rendered HTML is the product; htmx enhances it, it does not replace it.') without explaining concepts Claude already knows, matching the score-3 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Rules are prescriptive but abstract (e.g., 'Prefer simple hx-get and hx-include over custom client-side state') without executable code or copy-paste examples, so it instructs at the principle level rather than providing concrete guidance, fitting the score-2 anchor of 'some concrete guidance but incomplete'.

2 / 3

Workflow Clarity

There is no multi-step workflow with sequenced steps or validation checkpoints; content is a flat list of rules. Per the simple-skills note the single-action nature is clear, but the absence of any validation guidance for state-mutating forms ('Forms that mutate system state must still work as normal HTTP posts') keeps it at 2 rather than 3.

2 / 3

Progressive Disclosure

The skill is under 50 lines with no external references, organized into clearly labeled sections ('When to Use', 'HTMX Rules', 'Interaction Rules'), which per the simple-skills guideline lets progressive disclosure score 3 with well-organized sections alone.

3 / 3

Total

10

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and clearly scoped to its niche with explicit trigger guidance, scoring well on trigger quality, completeness, and distinctiveness. Its main weakness is specificity, since it describes the domain and rules rather than enumerating concrete actions.

Suggestions

Add 1-2 concrete actions to the description (e.g., 'add htmx partial loading and filter controls, wire forms and toggles') to lift specificity from 2 to 3.

Keep the explicit trigger clause as-is; it already satisfies the 'Use when' requirement for completeness.

DimensionReasoningScore

Specificity

Names the domain (htmx/templ Engram dashboard) and implies actions (interaction rules) but does not list multiple concrete actions like the score-3 anchor requires; phrases like 'interaction rules' and 'partial updates' are general rather than enumerating specific operations.

2 / 3

Completeness

It states what the skill does ('HTMX and templ interaction rules for the Engram dashboard') and explicitly when to use it ('Trigger: Any change to htmx attributes, partial updates, forms, or server-rendered browser UI'), satisfying both what and when as required for a 3.

3 / 3

Trigger Term Quality

Natural trigger terms users would actually say ('htmx attributes', 'partial updates', 'forms', 'server-rendered browser UI') are well covered and read like genuine user requests, matching the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

The niche is clearly scoped to htmx/templ within the specific Engram dashboard, with distinct triggers unlikely to fire for unrelated skills, matching the score-3 'clear niche with distinct triggers' anchor.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Gentleman-Programming/engram
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.