# Automate Microsoft Teams Workflows

Routine Teams work requires many manual lookups and repeated actions. This skill guides Claude or Codex through current Rube MCP tools for reliable execution.

## Install

```bash
npx skillstore add sickn33/microsoft-teams-automation
```

## Metadata

- Status: approved
- Slug: sickn33-microsoft-teams-automation
- Skillstore revision: r2
- Version status: missing
- Tree hash: 32a2eba3bc56f2135360cf183c8fa3999792b3843adab0645065f35809dad480
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/microsoft-teams-automation
- Ref: 81e05e636292629114b76cbb3922fbe57672fc02
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/sickn33-microsoft-teams-automation
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-microsoft-teams-automation/manifest

## Capabilities

- Lists accessible teams and resolves channel identifiers before posting.
- Sends messages to Teams channels, direct chats, and group chats.
- Creates standalone online meetings with specified participants and times.
- Lists, creates, and inspects channels within accessible teams.
- Lists team members and adds a selected user to a team.
- Searches Teams messages with KQL queries and handles paginated results.

## Use Cases

- Post Operational Updates: Resolve the correct team and channel, preview an update, and post it after approval.
- Coordinate Project Meetings: Find participant identifiers and create a Teams meeting with validated start and end times.
- Administer Team Spaces: Inspect teams, create channels, review membership, and add approved users.

## Prompt Templates

### List My Teams

```
Use Rube MCP to list the Microsoft Teams I can access. Show names and identifiers, and do not make changes.
```

### Prepare a Channel Message

```
Find the team named [team] and channel named [channel]. Draft this update: [message]. Show the destination and draft before posting.
```

### Create a Teams Meeting

```
Resolve these participants: [people]. Prepare a Teams meeting titled [subject] from [start] to [end] in [timezone]. Confirm details before creation.
```

### Audit and Update a Team

```
Inspect [team], list its channels and members, then propose changes for [goal]. Execute only approved changes and report each result.
```

## Limitations

- Requires a configured Rube MCP server and an active Microsoft Teams connection.
- Available actions depend on Microsoft Graph permissions and tenant policies.
- Created online meetings are not calendar events unless an Outlook calendar tool is used.
- Search results can be delayed, and Microsoft Graph can throttle frequent requests.

## Best Practices

- Search for current tool schemas before every workflow because MCP parameters can change.
- Resolve teams, channels, users, and chats through list operations instead of guessing identifiers.
- Preview destinations and content, then obtain explicit approval before write operations.

## Anti Patterns

- Do not post messages, create meetings, or change membership from ambiguous instructions.
- Do not reuse identifiers across tenants or assume display names are unique.
- Do not retry throttled requests immediately; honor Retry-After and use bounded backoff.

## Security Audit

- Audited at: 2026-08-04T14:14:32.868\+00:00
- Summary: The Markdown backticks and identifier examples are not executable commands or reconnaissance, so 59 static findings are false positives. The external Rube MCP endpoint is a real low-severity trust boundary, and write workflows lack explicit confirmation gates.

## Stats

- Views: 107
- Downloads: 10
- Favorites: 0
- Popularity score: 0