We've seen the same pattern on smaller solo projects too. Authoring skill N+3 three weeks after skill N-1 with no PR review is exactly the failure mode.
We'd copy the 110-line cap straight across. A number the agent can't talk past does more enforcement work than a written rule.
Out of interest - how did you settle on 110 specifically?
Hi Adam,
Honestly, it came from observation more than theory.
After building SMRITI, skills were changing almost daily — each iteration adding a few lines here, a new step there. Token usage kept climbing because every invocation loads the full skill file. At the same time, skills that grew too fast became harder to reason about.
We looked at where all the existing skills actually landed and 100–110 was the natural sweet spot — tight enough to keep costs predictable, generous enough that nothing needed an emergency rewrite. So we just drew the line there.
That makes sense, an observed cap is more defensible than one picked up front because it comes from what the skills actually needed. And the number matters less than the fact that hitting it makes you stop and check whether the skill has quietly taken on a second job. Cheers for the detail.
Adam Lewis
Product Engineer/Architect navigating the AI revolution
We've seen the same pattern on smaller solo projects too. Authoring skill N+3 three weeks after skill N-1 with no PR review is exactly the failure mode.
We'd copy the 110-line cap straight across. A number the agent can't talk past does more enforcement work than a written rule.
Out of interest - how did you settle on 110 specifically?