Tool Integrations Average 6.45. Methodology Skills Average 8.45.
The clearest split in the new batch is not by category. It is by what kind of skill the file is trying to be.
We grouped the forty new skills into two rough types.
Tool integrations are files whose job is to operate an external service: Gmail, Google Calendar, Google Docs, Google Sheets, Google Slides, Asana, ClickUp, Shopify, Zendesk, Jira. Thirteen skills.
Methodology skills are files whose job is to encode a way of making a decision: K-12 lesson planning, sales qualification, revenue operations, HR screening, e-commerce pricing. Eighteen skills.
| Group | Skills | Mean score | Trigger | Workflow | Engineering |
|---|---|---|---|---|---|
| Tool integrations | 13 | 6.45 | 5.31 | 4.27 | 6.73 |
| Methodology | 18 | 8.45 | 8.04 | 7.96 | 8.10 |
The methodology group scores two points higher overall, and nearly four points higher on workflow.
The exceptions
The split is not absolute. jira is a tool integration and scores 9.5, because it treats the tool as a system to be discovered, routed, and gated rather than a list of endpoints. google-calendar scores 8.3 for the same reason: it describes calendar operations as tasks with inputs and checks.
At the other end, asana-automation scores 4.9, clickup-automation 5.5, and calendar-automation 4.9. These files describe the existence of an API and leave the procedure implicit.
Why the gap exists
A methodology skill has to answer: what decision is being made, what inputs are required, what gates must be passed, and what the output looks like. That structure is naturally a workflow.
A thin tool integration often answers a different question: what calls are available. That is useful reference material, but it is not a procedure. The agent still has to invent the sequence, the validation, and the failure handling.
The lesson is not "avoid tool skills". It is that a tool skill needs the same discipline as a methodology skill: a trigger, a sequence, a verification step, and a stop condition. The best example in this batch is jira; the weakest are the wrappers that stop at the endpoint list.