Macros
Turn common toolchains into reusable shortcuts when the same sequence keeps coming back.
Macros sit between ad hoc work and larger automation. They are useful when the same small chain of actions keeps repeating and you want a reusable shortcut instead of rebuilding it each time. They are especially helpful for deployment checks, reporting routines, log analysis, and other compact operational tasks.
When a macro is the right tool
A macro is usually the right choice when the process is short, the steps are stable, and the output is predictable. If the work needs branching logic, richer input handling, or a visual operating surface, move up to Workflow instead. If it still needs a lot of human steering, keep it in Agent.
How to read the cards
Each card tells you what the shortcut does, who created it, which step types it relies on, how often it has run, and how healthy it has been over time. That makes the page useful even before you run anything yourself, because you can quickly judge whether a macro is a trusted team shortcut or something still experimental.
A good naming rule
Use names that sound like what the shortcut actually produces. A macro called “deploy-summary” is easier to adopt than one named after an internal abbreviation. Clear names reduce hesitation and make the page easier for the rest of the team to use without extra explanation.