CtrlK
BlogDocsLog inGet started
Tessl Logo

openkb-deck-neon

Use when the user asks the openkb chat to make a deck / slide presentation / PPT / slides / 演示稿 / 幻灯片 from their compiled KB content AND wants a dark, high-tech, neon / glow / glassmorphism look (赛博 / 科技风 / 暗色 / 霓虹 / 炫酷). Generates a polished single-file HTML deck in the Aurora Glass visual direction (near-black background, teal/sky/magenta/amber neon accents, glassmorphism panels, aurora gradient atmosphere) — opened in a browser, full-screened, shared. For the warm, printed, serif look use openkb-deck-editorial instead. Does NOT apply to generating skills (`openkb skill new`), research reports, or scrolling long-form documents.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

The body is highly actionable and has a well-sequenced workflow with explicit self-check validation, but it is a long monolithic document with real duplication between its positive rules and negative checklist and no progressive disclosure into separate files.

Suggestions

Dedupe the failure-mode checklist against the positive sections: failure modes 11, 14, 15, and 16 restate the Frame/Composition rules — collapse them into brief cross-references (e.g. 'see §Frame') to cut ~30-40 lines.

Split the large CSS design-system block and/or the 16-item failure list into one-level-deep reference files (e.g. references/design-system.md, references/failure-modes.md) and surface them with clearly signaled links so SKILL.md reads as an overview.

Tighten repeated rationales inside rules (e.g. the SVG-text-explanation appears in both §Composition and failure mode 16) to a single statement plus a pointer.

DimensionReasoningScore

Conciseness

The body is skill-specific with no generic concept padding, but ~280 lines with notable duplication between the positive sections and the 16-item failure-mode checklist (letterbox, left-sliver, big-number, and SVG-label rules each appear twice), so it could be tightened.

2 / 3

Actionability

Provides copy-paste-ready CSS (:root vars, .slide{position:fixed;inset:0…}, exact clamp() values), an exact output path, exact keyboard nav, and concrete font stacks — fully executable guidance.

3 / 3

Workflow Clarity

The 8-step 'Working method' is clearly sequenced with explicit validation checkpoints (the 'Self-check' invariants and 'Revise against §Failure modes'), providing a clear feedback loop.

3 / 3

Progressive Disclosure

There are no bundle files and everything lives inline in one ~280-line file; it is well-sectioned and navigable, but monolithic — the detailed CSS and failure-mode content could be split into clearly-signaled one-level-deep references rather than fully inline.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 specific, trigger-rich in both languages, complete (explicit 'Use when' plus a clear 'what'), and sharply distinguished from the sibling editorial skill via explicit routing and exclusions. Third-person/imperative voice with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Generates a polished single-file HTML deck… opened in a browser, full-screened, shared" — plus concrete visual tokens (teal/sky/magenta/amber accents, glassmorphism panels), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (generates a single-file HTML deck in the Aurora Glass direction) and 'when' (an explicit 'Use when…' clause), matching the 'clearly answers both what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

Broad natural-term coverage in English ("deck / slide presentation / PPT / slides") and Chinese (演示稿 / 幻灯片 / 赛博 / 科技风 / 霓虹 / 炫酷), matching the 'good coverage of natural terms users would say' anchor.

3 / 3

Distinctiveness Conflict Risk

Explicitly routes the warm/serif look to openkb-deck-editorial and excludes skills, research reports, and long-form documents, giving a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
VectifyAI/OpenKB
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.