One skill per action looked like the safe boundary
I've been building an AI-assisted editorial pipeline in Cursor. Notion cards capture observations, skills score and schedule them, and agents draft markdown that eventually syncs to dev.to. In that setup, a skill is a markdown file the agent loads when you invoke a workflow: it defines what the agent may do, what it must not do, and how it routes between sub-steps. When I started, that model felt…
The article discusses the challenges and solutions encountered while building an AI-assisted editorial pipeline in Cursor. An initial approach of using one skill per action proved to be problematic as the system evolved. The author explains how they initially created an inbox skill that only created cards, but as more work was needed while a card was still in the Inbox, it became clear that this was three distinct jobs.
The skills needed to create, enrich, and reclassify cards within the Inbox. However, trying to separate these into three different skills led to issues such as ownership conflicts and unclear routing.
Ultimately, the author concluded that consolidating these operations into a single skill was the better solution. The inbox skill now handles create, enrich, and reclassify actions while the card remains in the Inbox. The skill internally routes commands, allowing the user to invoke a single skill and the routing rules deciding the appropriate actions. This consolidation simplifies the system by providing one place owning the Inbox normalization, a shared rule set, and authority over the rules.
The author suggests applying a "consolidate-vs-split test" to similar situations: if the lifecycle stage or artifact type diverges, then the skills should not be consolidated. They also mention that different operations, such as scheduling, drafting, critique, and publishing, own different artifacts and stop lines, so they remain separate. The key takeaway is that a single skill should cover a coherent capability with internal routing between operations, rather than having multiple skills handling related actions.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written; read the original for the full account.
