CtrlK
BlogDocsLog inGet started
Tessl Logo

megacave

Caveman in Classical Chinese: 文言文 register, far fewer characters, technical terms verbatim. Invoke only with /megacave or /caveman wenyan. Stays on until "stop caveman" or "normal mode".

76

Quality

95%

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

100%Weight 40%Scale 1-5

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

An exemplary instruction-only skill body: maximal information density, concrete before/after examples in the target register, explicit exception handling, and a pre-send checklist that serves as a validation step. There is no wasted content and no missing structure for a skill of this scope.

DimensionReasoningScore

Conciseness

The ~54-line body is pure rules and examples with zero padding — no concept explanations Claude already knows, and even meta-guidance ("Token savings are small and noisy; never claim them") earns its place. Every token earns its place.

5 / 5

Actionability

Concrete Bad/Good example pairs in real 文言 (e.g. "每繪新生對象參照,故重繪;以 `useMemo` 包之則免"), explicit floors (negation characters, Arabic numerals, verbatim identifiers), and a literal pre-send checklist give fully actionable guidance; per the rubric's code-vs-instruction note, an instruction-only skill needs no code when guidance is this concrete.

5 / 5

Workflow Clarity

A single-action skill whose action is unambiguous: persistence semantics ("Unsure? Still on."), status-command behavior, escape hatches ("When to break the rules"), and a pre-send validation check. It is not a destructive or batch skill, so no validation cap applies and the simple-skill exception holds.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clear sections (Persistence, Floor, Rules, When to break the rules, Pre-send check); no bundle files exist and nothing is inlined that belongs in a separate file, matching the rubric's simple-skill guidance for short skills needing no external references.

5 / 5

Total

20

/

20

Passed

Description

87%Weight 40%Scale 1-5

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

A strong description: it states precisely what the skill does, how to invoke and terminate it, and stays lean with no buzzwords. Trigger and what/when coverage are explicit; only synonym breadth and multi-action enumeration keep two dimensions at 4.

DimensionReasoningScore

Specificity

"文言文 register, far fewer characters, technical terms verbatim" names several concrete behaviors of the output rather than vague filler, but the skill performs one transformation rather than a list of distinct actions, leaving minor coverage gaps.

4 / 5

Completeness

The "what" (文言 register, fewer characters, technical terms verbatim) and the "when" ("Invoke only with /megacave or /caveman wenyan") are both explicitly stated with concrete trigger phrases, plus termination conditions, matching the top anchor.

5 / 5

Trigger Term Quality

Natural terms a user would say are present ("caveman", "Classical Chinese", "文言文", "wenyan") alongside explicit commands ("/megacave", "/caveman wenyan", "stop caveman", "normal mode"), though a few obvious synonyms (e.g. "文言" alone) are missing.

4 / 5

Distinctiveness Conflict Risk

A caveman-in-Classical-Chinese register mode gated to explicit slash commands occupies a clear niche with essentially no overlap risk against other skills.

5 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
JuliusBrussee/caveman
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.