# Platform Automation

> Choose and configure AgenticOS routines, watches, event triggers, task reminders and conversation suggestions without duplicating them. Explain schedules, working chats, Inbox cases and notification destinations.

- Skill: `vstorm-co/platform-automation` (Agent Skill)
- Install (CLI): `npx get-skill add vstorm-co/platform-automation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vstorm-co/platform-automation/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: vstorm-co (https://skillmd.com/u/vstorm-co)
- Updated: 2026-11-12
- Page: https://skillmd.com/skills/vstorm-co/platform-automation

---


# One responsibility, one automation

Use when choosing or designing unattended behavior, not for a simple routine edit. Current MCP descriptions own creation fields, scheduling syntax, source review and result-mode contracts.

Choose by intent:

- A recurring report or periodic job belongs to a routine.
- Read-only monitoring for meaningful changes belongs to a watch.
- A supported incoming event starts an event routine or workflow.
- A one-off commitment or reminder belongs to a durable Task.
- Suggestions derived from conversations propose improvements; they do not monitor a mailbox or silently activate jobs.
- Following command output in this turn is temporary monitoring, not an account watch.

Reuse an existing responsibility before adding another poller. Agree sources, relevance, cadence/time zone, audience, permitted actions and when to stay quiet. Ask through the question tool only for a missing decision. Account access, source scope and unattended-action consent remain separate from the agent's capabilities.

Make the result useful: a report reaches its configured destination; a source-item finding keeps its working conversation, draft and Inbox attention connected. A draft is not a sent message, and viewing a case is not completing its task. Resolve after a successful authorized effect or explicit completion. An uncertain send stays unresolved until checked.

Offer an unrequested automation as a non-blocking proposal. When creation is requested, perform the authorized setup through its normal gates, verify saved state and link it. Finish a one-off answer without holding the conversation open to ask about an optional recurring version.

