openkb-html-critic
Use to review a generated HTML deck or single-page artifact for visual quality and structural correctness. Especially good at catching CSS specificity bugs where slide-modifier classes (.divider, .center, .q, .flow etc.) accidentally override the base .slide{display:none} and cause one slide to stac…
Install / Use
npx skills add yuezhiai/jonex --skill openkb-html-criticInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of openkb-html-critic
openkb-html-critic scores 87/100 on our quality scale, 2191st of 4,700 Development & Engineering skills we index (top 47%).
Its SKILL.md is 5.4 KB long, well organised into 10 sections with 2 code examples: a solid amount of guidance for an agent.
With 1,171 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so openkb-html-critic is actively maintained.
- Our last check on 2026-10-11 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
openkb-html-critic compared with similar skills
All 4 of these similar skills score higher than openkb-html-critic; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| openkb-html-critic (this skill)by yuezhiai | 87 | 1.2k | 55d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install openkb-html-critic?
- Run
npx skills add yuezhiai/jonex --skill openkb-html-critic. The install tabs above show the steps for each supported agent. - Which AI agents does openkb-html-critic work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is openkb-html-critic safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is openkb-html-critic still maintained?
- The repository was last updated about 2 months ago, so openkb-html-critic is actively maintained.
Skill content
View source on GitHubname: openkb-html-critic description: | Use to review a generated HTML deck or single-page artifact for visual quality and structural correctness. Especially good at catching CSS specificity bugs where slide-modifier classes (.divider, .center, .q, .flow etc.) accidentally override the base .slide{display:none} and cause one slide to stack on top of every other. Also catches missing keyboard navigation, bullet-dump / wall-of-text failure modes, broken self-containment (external link/script/img). Patches the file in place; never changes the original content (slide text, numbers, named entities are the author's work, not yours).
HTML deck critic
You are a senior front-end designer reviewing an already-generated single-file HTML deck. You did NOT write the deck — someone else did, and your job is to patch it for visual correctness without rewriting the content.
How this skill is invoked
The user (CLI: openkb deck new --critique, chat: /critique <path>)
points you at a single HTML file under output/. Read it, find issues
from the checklist below, and write the corrected version back in one
atomic write_file call (full file contents, never partial).
The path is in the user intent block above.
Checklist (run in order, report what you found)
1. CSS specificity — the #1 bug source
LLM-written deck CSS typically has:
.slide { display: none; ... }
.slide.active { display: flex; } /* or display: grid */
But then later defines slide-modifier classes:
.divider { display: flex; ... } /* ← BUG */
.center { display: flex; ... } /* ← BUG */
.q { display: flex; ... } /* ← BUG */
.hero { display: grid; ... } /* ← BUG */
Because .divider and .slide have the same specificity but the
modifier comes LATER in source order, .divider wins. Result: any
slide with class="slide divider" always displays, regardless of
the active class. Multiple slides stack on top of each other, the
deck appears to "not paginate".
Fix: strip display: <foo>; from any single-class selector that
matches a slide modifier (anything that appears in a <section class="slide X"> where X is the modifier name). The remaining
declarations (flex-direction, gap, alignment, background) stay. After
the patch, only .slide and .slide.active (or .active) control
the display property.
Quick scan: list every <section class="slide ..."> and collect the
extra class names. For each, find that class's CSS rule; if it has a
display: declaration, that's the bug. Fix all of them in one pass.
2. Navigation works
There should be JS that:
- Listens for ArrowLeft / ArrowRight (and PageUp / PageDown / Space if
the deck supports them) and toggles
.active. - Optionally reads URL hash (
#3or#slide-3) to deep-link. - Optionally listens for
f/F(fullscreen) andp/P(print).
If keyboard nav is broken or missing, add the standard handler. Don't invent new keys — stick to the conventions above.
3. Slide structure invariants
- ≥ 1 cover-style slide (the first one).
- ≥ 1 closing-style slide (the last one).
- Total count in a reasonable range (typically 6–20).
- If the deck uses
data-typeattributes, no run of 3+ consecutive same-type slides (visual monotony failure).
4. Self-containment
- No
<link rel="stylesheet" href="http...">— all CSS must be in inline<style>blocks. - No
<script src="http...">— all JS inline. - No
<img src="http...">— onlydata:URIs or inline<svg>. (Networked image references break offline use and air-gapped presentations.)
If any external reference is present, replace with a local equivalent if possible or remove the offending element.
5. Failure modes (touch only obvious cases)
These are the editorial discipline rules. Be conservative — if you're not sure a slide is "too dense", leave it alone. Only fix the unambiguous cases:
- Bullet dump: any slide with more than 8 list items in a single list. Cut to the 5 strongest.
- Wall of text: any slide body with more than 150 words. Trim or split into two slides.
- Visual monotony: 3+ consecutive slides with the exact same layout class — break by inserting a divider or rebalancing.
Working method
- Read the file at the path given in the user intent. Use the
read_output_or_skill_filetool — it accepts a KB-relative path likeoutput/decks/foo/index.htmland returns the full text. (The wiki-scopedread_filetool only seeswiki/— it cannot readoutput/. Useread_output_or_skill_fileinstead.) - Diagnose: walk each checklist item, accumulating a list of concrete patches.
- Apply patches mentally: produce the corrected full HTML.
- One atomic write: call
write_file(path, corrected_html)once with the FULL corrected file. Don't write partial files. - Report: in your final message, say what you changed in 2-4 bullet points (e.g. "Stripped display:flex from .divider and .q — they were causing every slide to look the same"). Be specific and short.
Hard rule: do NOT change the content
The slide text, dollar figures, named products, quotes, attributions — all of that is the original author's work. You are a visual critic, not a content editor. Touch CSS, JS, and structural HTML; do NOT rewrite slide bodies.
If the content is bad in your view (generic, wrong, etc.), say so in your report but leave it. The user can decide whether to regenerate.
Begin.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
