Platform bottleneck

• ◦keep skill files under 500 linesin 82 of 803, across 16 files
• ◦use imperative form in instructionsin 80 of 803, across 9 files
• ◦draft assertions while test runs are in progressin 75 of 803, across 9 files
• ◦create two to three realistic test promptsin 74 of 803, across 9 files
• ◦write skill descriptions to be pushyin 72 of 803, across 7 files
• ◦save test cases to evals jsonin 72 of 803, across 6 files
• ◦ask questions about edge cases and input formatsin 72 of 803, across 7 files
• ◦save timing data immediately when runs completein 70 of 803, across 5 files
• ◦include all trigger conditions in the skill descriptionin 69 of 803, across 3 files
• ◦launch all test runs in a single turnin 69 of 803, across 3 files
• ◦capture intent before writing a skillin 67 of 803, across 1 file
• ◦import directly instead of barrel filesin 52 of 803, across 15 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.