Load to add, tune, or debug document byte ceilings and DOC_LIMITS_* settings.
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/doc-limits/SKILL.mdProblems with a kendex-owned skill go through kendex report; check ownership in the file first.
Run the document byte-ceiling check before review and in CI. The commit-guards pre-commit chain uses the staged mode.
.agents/skills/doc-limits/scripts/doc-limits
.agents/skills/doc-limits/scripts/doc-limits --stagedThe check measures AGENTS.md, CLAUDE.md, GEMINI.md and SKILL.md, at the root and at any depth, and no other file. A document over its limit fails the check. Bring it under its limit in this order: cut restated content first, split only at a real subject boundary, and never delete a rule to fit. references/policy.md § Path classes says how a class sets a ceiling among those files.
A document that must stay whole gets a row in the configured excludes file with its reason. Class selection and the exclusion format are references/policy.md. Flags, settings and exit codes are in doc-limits --help.
vanillagreencom/kendex
3a2f84c
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.