Microsoft Teams Automation
Skill433 starsChanged 10 months agoMITView on GitHub
Automate Microsoft Teams messaging, meetings, channels, and workflow integrations
In this repository137 other files it gives its agents.
- .cursor/rules/project-rules.mdcCursor rule
- academic-searchSkill
- ads-copywriterSkill
- ai-agent-builderSkill
- airtable-automationSkill
- ai-slidesSkill
- Amazon SellerSkill
- Apple Shortcuts IntegrationSkill
- Applicant ScreeningSkill
- Asana AutomationSkill
- batch-convertSkill
- batch-processorSkill
- Brand Guidelines GeneratorSkill
- Browser AutomationSkill
- calendar-automationSkill
- Changelog GeneratorSkill
- chart-designerSkill
- Chat with PDFSkill
- ClickUp AutomationSkill
- company-researchSkill
- competitive-analysisSkill
- Content Research WriterSkill
- contract-reviewSkill
- contract-templateSkill
- cover-letterSkill
- crm-automationSkill
- crypto-reportSkill
- customer-successSkill
- cv-builderSkill
- data-analysisSkill
- Database SyncSkill
- data-extractorSkill
- data-pipelineSkill
- dcf-valuationSkill
- deep-researchSkill
- devops-automationSkill
- dev-slidesSkill
- diagram-creatorSkill
- discord-botSkill
- doc-parserSkill
- doc-pipelineSkill
- DocuSign AutomationSkill
- docx-manipulationSkill
- Email ClassifierSkill
- email-drafterSkill
- email-marketingSkill
- ETL PipelineSkill
- excel-automationSkill
- expense-reportSkill
- Expense TrackerSkill
- Facebook/Meta AdsSkill
- File OrganizerSkill
- financial-modelingSkill
- form-builderSkill
- gmail-workflowsSkill
- google-ads-managerSkill
- Home Assistant AutomationSkill
- hr-automationSkill
- html-slidesSkill
- html-to-pptSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 200
Adaptive Cards: Use for rich interactions
- Distinctive: line 203
Mentions: Use @mentions sparingly
- Distinctive: line 204
Webhooks: Use for one-way notifications
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Microsoft Teams Automation
Automate Microsoft Teams communication and collaboration workflows.
Core Capabilities
Channel Messaging
message_types:
simple_message:
channel_id: "channel_xxx"
message: "Hello, Team!"
formatted_message:
channel_id: "channel_xxx"
content_type: "html"
message: |
<h1>Weekly Update</h1>
<ul>
<li>Item 1</li>
<li>Item 2</li>
</ul>
adaptive_card:
channel_id: "channel_xxx"
card:
type: "AdaptiveCard"
body:
- type: "TextBlock"
text: "Approval Required"
weight: "bolder"
- type: "Input.Text"
id: "comment"
placeholder: "Add comment"
actions:
- type: "Action.Submit"
title: "Approve"
data:
action: "approve"Meeting Automation
meeting_creation:
subject: "Weekly Standup"
start: "2024-01-20T09:00:00"
end: "2024-01-20T09:30:00"
attendees:
- "user1@company.com"
- "user2@company.com"
is_online_meeting: true
settings:
allow_new_time_proposals: true
lobby_bypass: "organization"
record_automatically: falseIncoming Webhooks
webhook_message:
url: "https://outlook.webhook.office.com/..."
payload:
"@type": "MessageCard"
themeColor: "0076D7"
summary: "Deployment Complete"
sections:
- activityTitle: "Production Deployment"
activitySubtitle: "v2.1.0 deployed successfully"
facts:
- name: "Environment"
value: "Production"
- name: "Duration"
value: "5 minutes"
markdown: true
potentialAction:
- "@type": "OpenUri"
name: "View Dashboard"
targets:
- os: "default"
uri: "https://dashboard.example.com"Bot Workflows
bot_commands:
/status:
description: "Check system status"
response:
type: adaptive_card
template: status_card
/create-ticket:
description: "Create support ticket"
parameters:
- title: required
- priority: optional
action: create_jira_issue
/approve {id}:
description: "Approve request"
action: process_approval
response: "Request {{id}} approved ✓"Integration Workflows
CI/CD Notifications
pipeline_notifications:
on_build_start:
channel: "#deployments"
card:
title: "🚀 Build Started"
fields:
- Branch: "{{branch}}"
- Triggered by: "{{user}}"
on_build_complete:
channel: "#deployments"
card:
title: "{{#if success}}✅{{else}}❌{{/if}} Build {{status}}"
fields:
- Duration: "{{duration}}"
- Tests: "{{tests_passed}}/{{tests_total}}"
actions:
- title: "View Logs"
url: "{{logs_url}}"Approval Workflows
approval_flow:
trigger: expense_submitted
actions:
- send_adaptive_card:
channel: "#approvals"
card:
title: "Expense Approval"
body: "{{employee}} submitted ${{amount}}"
actions:
- Approve
- Reject
- wait_for_response:
timeout: 48_hours
- process_decision:
approved: update_expense_status
rejected: notify_submitterBest Practices
- Rate Limits: Respect Microsoft Graph limits
- Adaptive Cards: Use for rich interactions
- Permissions: Request minimal scopes
- Threading: Reply in threads for context
- Mentions: Use @mentions sparingly
- Webhooks: Use for one-way notifications
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

