CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

doc-limits

Load to add, tune, or debug document byte ceilings and DOC_LIMITS_* settings.

Quality

84%

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

93%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 lean skill body: executable commands, a clear failure-remediation workflow, and proper progressive disclosure that pushes class policy and exclusion format into references/policy.md. The only minor gap is that the verify-after-fix re-run step is implicit.

DimensionReasoningScore

Conciseness

Every sentence carries skill-specific policy ("at the root and at any depth, and no other file", "cut restated content first... never delete a rule to fit") with no padding and no explanation of concepts Claude already knows. Lean and efficient; every token earns its place.

5 / 5

Actionability

Two copy-paste-ready commands with both invocation modes, a concrete ordered remediation strategy for over-limit documents, and an explicit pointer for where exclusion rows go. The guidance is fully executable and covers the common cases.

5 / 5

Workflow Clarity

The sequence is clear: run the check (mode selection stated, including the pre-commit staged mode), then a decision path for failures with an ordered fix strategy and an exclusion escape hatch. Not 5 because the re-run-to-verify loop after a fix is implied rather than an explicit step, though the check itself is non-destructive so no validation cap applies.

4 / 5

Progressive Disclosure

A short overview body with a well-signaled, one-level-deep reference ([references/policy.md](references/policy.md), verified to exist) linked twice with a section anchor, while flags and exit codes are delegated to `doc-limits --help`. Content is appropriately split with easy navigation and no nested doc references.

5 / 5

Total

19

/

20

Passed

Description

71%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 lean, third-person description with concrete verbs and a highly distinctive trigger (the DOC_LIMITS_* namespace), but its natural-language trigger coverage is thin and the 'when' guidance, while explicit, is minimal. Adding a 'Use when...' clause with user-facing phrases would strengthen it.

Suggestions

Add a 'Use when...' clause naming natural user phrasings, e.g. "Use when a CLAUDE.md, AGENTS.md, GEMINI.md or SKILL.md is over its byte limit or the user mentions document size limits."

Include common synonyms and the measured file names (CLAUDE.md, AGENTS.md) so the description triggers on the phrases users actually say.

Mention the exclusion-list capability (keeping a must-stay-whole document out of the check) to round out coverage of what the skill does.

DimensionReasoningScore

Specificity

"add, tune, or debug" names three concrete actions on a specific target ("document byte ceilings and DOC_LIMITS_* settings"), matching the several-specific-actions-with-minor-gaps anchor. It falls short of 5 because it omits capabilities like excluding files or running the check, and exceeds 3 because it lists more than 1-2 actions.

4 / 5

Completeness

"Load to add, tune, or debug..." gives a clear 'what' plus explicit (if terse) trigger guidance equivalent to a 'Use when' clause, so both parts are answered. Not 5 because the 'when' lacks concrete trigger phrases like "when a CLAUDE.md exceeds its limit".

4 / 5

Trigger Term Quality

"document byte ceilings" and "DOC_LIMITS_*" are relevant keywords, but common natural phrasings users would say — "file size limit", "too large", or the measured file names (CLAUDE.md, AGENTS.md) — are absent. Not 4 because keyword coverage is narrow rather than good-with-a-few-missing.

3 / 5

Distinctiveness Conflict Risk

"DOC_LIMITS_* settings" is a unique settings namespace and "document byte ceilings" a narrow niche, giving distinct triggers with minimal conflict risk against other skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

vanillagreencom/kendex

Path

skills/doc-limits/SKILL.md

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.