Notis Automation Skill

Use this skill whenever the user wants something to happen later, on a schedule, or in response to an event. It covers the three Notis building blocks and how they fit together:

• Skills hold the business logic — the reusable "what to do".
• Automations are the glue: they link a trigger to business logic. They are also how you make Notis do something in the future.
• Reminders are dumb: they deliver a fixed message at a time or on a schedule. No reasoning, no tools, no computed content.

The single most important job of this skill is to pick the right primitive, then build a valid payload for it.

Tool names

These are native Notis tools. When their canonical LOCAL_NOTIS_* names are available in the current tool set, call them directly. Do not send an already-available native automation or reminder tool through COMPOSIO_SEARCH_TOOLS or wrap it in COMPOSIO_MULTI_EXECUTE_TOOL; discovery is only for a capability that is not loaded. Always call native tools by their canonical names: