How do I install the Communications Productivity Integrations skill?

Run npx skillmds@latest add davidtoby/communications-productivity-integrations in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Communications Productivity Integrations safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Communications Productivity Integrations?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Communications Productivity Integrations free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Communications Productivity Integrations?

davidtoby (@davidtoby) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Communications Productivity Integrations by davidtoby

Name: Communications Productivity Integrations
Author: davidtoby

Communications Productivity Integrations

Class-level workflow for messaging, email, calendars, notes, boards, workspaces, and collaboration integrations via CLIs/APIs: Discord, Slack, Gmail/IMAP, Google Workspace, CalDAV, Trello, Notion, Obsidian, Apple Notes/Reminders, iMessage/SMS, and Clawk. Use when asked to send/read/manage messages, email, calendar events, notes, tasks, pages, boards, or collaboration objects.

davidtoby e2c9534 10 files · 43.3 KB Updated Sep 17, 2026

File contents

Communications and Productivity Integrations

Use this umbrella for human communication and productivity-system actions.

Core workflow

Identify target service, account/workspace, recipient/channel/list/database, and whether the user wants read-only or side-effecting action.
For specific channels/people, list available targets before sending when the tool requires it.
Use IDs from lookup results rather than guessing names.
For writes, confirm ambiguous destinations or destructive edits; otherwise act with the obvious default.
Verify side effects by reading back the created/sent/updated object when possible.
Avoid leaking secrets, private message bodies, or unnecessary personal data in summaries.

Labeled playbooks

Chat and social messaging

Discord, Slack, iMessage/SMS, and Clawk workflows should preserve thread/channel context and support attachments/media when available.

Email

Use Gmail APIs or IMAP/SMTP CLIs depending on account configuration. For composition, draft clearly and confirm before sending if recipient/content is ambiguous.

Calendars

Use CalDAV/Google Workspace paths for event lookup, creation, and sync; check timezone explicitly.

Notes and knowledge bases

Use Apple Notes, Obsidian, Notion, or Google Docs depending on the user's repository. Preserve markdown/plain-text compatibility where possible.

Task and board systems

For Reminders/Trello/Notion databases, map user language to list/board/database IDs and verify card/task creation.

Reference files

Service-specific legacy skill bodies and command examples live in references/from-*.md.

---name: communications-productivity-integrationsdescription: Class-level workflow for messaging, email, calendars, notes, boards, workspaces, and collaboration integrations via CLIs/APIs: Discord, Slack, Gmail/IMAP, Google Workspace, CalDAV, Trello, Notion, Obsidian, Apple Notes/Reminders, iMessage/SMS, and Clawk. Use when asked to send/read/manage messages, email, calendar events, notes, tasks, pages, boards, or collaboration objects.---# Communications and Productivity IntegrationsUse this umbrella for human communication and productivity-system actions.## Core workflow1. Identify target service, account/workspace, recipient/channel/list/database, and whether the user wants read-only or side-effecting action.2. For specific channels/people, list available targets before sending when the tool requires it.3. Use IDs from lookup results rather than guessing names.4. For writes, confirm ambiguous destinations or destructive edits; otherwise act with the obvious default.5. Verify side effects by reading back the created/sent/updated object when possible.6. Avoid leaking secrets, private message bodies, or unnecessary personal data in summaries.## Labeled playbooks### Chat and social messagingDiscord, Slack, iMessage/SMS, and Clawk workflows should preserve thread/channel context and support attachments/media when available.### EmailUse Gmail APIs or IMAP/SMTP CLIs depending on account configuration. For composition, draft clearly and confirm before sending if recipient/content is ambiguous.### CalendarsUse CalDAV/Google Workspace paths for event lookup, creation, and sync; check timezone explicitly.### Notes and knowledge basesUse Apple Notes, Obsidian, Notion, or Google Docs depending on the user's repository. Preserve markdown/plain-text compatibility where possible.### Task and board systemsFor Reminders/Trello/Notion databases, map user language to list/board/database IDs and verify card/task creation.## Reference filesService-specific legacy skill bodies and command examples live in `references/from-*.md`.

Frequently asked questions