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 safest as one skill per action. Create a card here. Enrich a card there. Reclassify somewhere else. Each prompt got a clean boundary. Each file stayed small. Decomposition felt like good engineering.
That assumption started to fight the domain.
When every action gets its own skill
The first version of my inbox skill only created Inbox cards. That matched early usage: capture an observation, normalize it into a canonical shape, attach a small set of grounded references, and stop. The skill was create-only and treated each new card as immutable once it left Inbox.
