Teams App Developer
MicrosoftOfficialPublished by Microsoft
- Skill
- Tool integration
- Software development
- MIT
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The teams-app-developer skill provides a structured framework for managing the lifecycle of Microsoft 365 agents and Teams applications. It leverages the ATK CLI to handle project scaffolding, local testing via the Agents Playground, cloud provisioning on Azure, and troubleshooting. The skill includes specialized guidance for migrating Slack bots to Teams, including converting Block Kit UI to Adaptive Cards, and provides access to an extensive library of micro-expert documentation for cross-platform development.
What it does
- Scaffolds new Microsoft 365 agents and Teams applications from templates.
- Facilitates local testing using the Agents Playground or Teams-specific environments.
- Automates Azure resource provisioning and cloud deployment workflows.
- Provides diagnostic procedures for common authentication and configuration errors.
- Supports migration of Slack bots to the Teams platform.
- Manages project configuration and environment variables for ATK-based projects.
When to use it
- When starting a new Teams app, bot, or Declarative Agent project.
- When you need to test an agent locally before deploying to the cloud.
- When migrating existing Slack bots to the Microsoft Teams ecosystem.
- When troubleshooting deployment or authentication issues in a Teams project.
- When you need to provision Azure infrastructure for a Teams application.
Advantages
- Streamlines the development lifecycle with standardized CLI commands.
- Reduces development time by offering a local testing playground.
- Provides expert-level guidance for complex cross-platform migrations.
- Ensures consistent configuration management across development environments.
- Includes robust error-handling protocols for common platform-specific pitfalls.
Usage examples
- “Create a new Teams bot project using the default template.”
- The agent will initialize a new project folder, configure the necessary YAML files, and guide you through the initial setup using the ATK CLI.
- “How do I migrate my Slack bot to Microsoft Teams?”
- The agent will initiate the slack-to-teams workflow, providing access to cross-platform bridging experts and guidance on converting UI components.
- “My Teams bot is returning a 401 error, how do I fix it?”
- The agent will trigger the troubleshooting workflow, checking your environment variables, tunnel status, and authentication configuration.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/teams-app-developer/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip teams-app-developer.zip -d .agents/skills
Documentation by Microsoft
Microsoft 365 Agents Toolkit Skill
Build Microsoft 365 agents and Teams apps using the ATK CLI.
AI Behavior Guidelines
Testing Strategy: Recommend Agents Playground first (faster, no M365 needed). Use Teams workflow only if user explicitly requests it.
Environment Variables: NEVER hardcode secrets or make up placeholder values. Always ask users for real values.
Error Handling: Read error messages carefully. Check
env/.env.local,.localConfigs, andatk auth list. Common pitfalls:AADSTS7000229→aadApp/createmissinggenerateServicePrincipal: truein YAML — add it and re-provisionMissing
TENANT_IDin.localConfigs→ SDK uses wrong token authority → 401 from Bot Connector401 persists after auth fix → devtunnel URL may be blacklisted — create a fresh tunnel
See troubleshoot/troubleshoot.md for full diagnostic steps
Long-Running Commands — WAIT for completion:
atk new,atk provision,atk deploycan take several minutesAlways wait for completion before running the next step (timeout 120000ms+)
Local Service Startup — Hangs terminal (expected):
npm run dev,npm start,python app.py,devtunnel host, etc. will hang — the process keeps running indefinitelyALWAYS run as a background process (
isBackground=true) — NEVER useisBackground=falsefor these commandsDo NOT wait for it to "finish" — verify startup by checking output for "listening on port" or tunnel URL
If errors appear, read logs, diagnose, fix, restart
Use a NEW terminal to launch Agents Playground or open Teams sideloading URL
Monitor App Logs: Periodically check background terminal output for runtime errors. If the app crashes, read the error, fix the root cause, and restart.
Telemetry Tagging: Before running any
atkCLI commands, set the session environment variable so all CLI invocations are tagged as skill-initiated:export ATK_CLI_SKILL=trueRun this once at the start of the session. All subsequent
atkcommands in the same terminal will inherit it.
ATK CLI Setup
atk --version # Must be > 1.1.5-betaIf ATK is not found or version is too old:
npm i -g @microsoft/m365agentstoolkit-cli@betaCLI Global Options
| Option | Meaning | Recommendation |
|---|---|---|
-i | Interactive mode | Always use -i false in automation to avoid hanging |
-f | Project folder | Default to be current directory, used when specifying a custom folder. When scaffolding a new project, this is the parent folder where the project folder will be created under. |
-h | Command help | Use atk <command> -h for quick syntax checks |
Sub-Skills
| Sub-Skill | When to Use | Reference |
|---|---|---|
| create-project | Scaffold new project from template, choose template, atk new | create-project/create-project.md |
| test-playground | Test locally with Agents Playground, agentsplayground, quick testing | test-playground/test-playground.md |
| test-teams | Run on Teams, devtunnel, sideload, Teams testing, test in Copilot | test-teams/test-teams.md |
| provision-deploy | Provision Azure resources, deploy to cloud, atk provision, atk deploy | provision-deploy/provision-deploy.md |
| troubleshoot | Fix errors, 401, port conflicts, YAML errors, stale bots | troubleshoot/troubleshoot.md |
| slack-to-teams | Migrate Slack bot to Teams, cross-platform bridging, Block Kit to Adaptive Cards | slack-to-teams/SKILL.md |
MANDATORY: Before executing any workflow, read the corresponding sub-skill document.
Shared References
manifest-and-yaml.md — Project files, YAML config, env vars, .localConfigs flow
commands.md — ATK CLI commands: package, validate, share, collaborate
templates.md — Complete template catalog with language support
experts/ — 100+ micro-expert files: Teams SDK, Slack SDK, cross-platform bridging, deploy, AI models, security, language conversion
docs/ — Platform comparison guides: UI, messaging, identity, infrastructure, feature gaps
Workflow Chains
Match user intent to the smallest valid workflow.
| User Intent | Workflow (read in order) |
|---|---|
| Build new app from scratch | create-project → test-playground |
| Test existing project locally | test-playground (recommended) or test-teams |
| Deploy to Azure | provision-deploy |
| Fix broken bot | troubleshoot → re-test |
| Migrate Slack bot to Teams | slack-to-teams |
MANDATORY: Before executing any slack-to-teams workflow, read slack-to-teams/SKILL.md first. The sub-skill contains a routed expert system with 100+ micro-expert files for cross-platform bot development.
ATK Project Context Resolution
Resolve config values only when missing. If a value is already known in the session, reuse it.
Step 1: Detect ATK Project
If m365agentstoolkit*.yml exists in the current folder, treat it as an ATK project and parse configuration.
Step 2: Resolve Common Configuration
Resolve variables referenced in m365agentstoolkit*.yml. Common variables:
AZURE_OPENAI_API_KEY
AZURE_OPENAI_ENDPOINT
AZURE_OPENAI_DEPLOYMENT_NAME
Step 3: Collect Missing Values
If required values are missing, ask the user for only the missing ones.
Refer to manifest-and-yaml.md for full config-file details.
Files
- ATTRIBUTION.mdAdded by AutoGineer906 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md7.6 KiB
- create-project/create-project.md8.1 KiB
- docs/README.md2.8 KiB
- docs/advanced-features.md7.0 KiB
- docs/feature-gaps.md46.3 KiB
- docs/files-and-links.md4.2 KiB
- docs/identity-and-auth.md4.3 KiB
- docs/infrastructure.md6.7 KiB
- docs/interactive-responses.md4.4 KiB
- docs/messaging-and-commands.md4.5 KiB
- docs/middleware-and-handlers.md4.4 KiB
- docs/ui-components.md6.9 KiB
- docs/workflows.md14.4 KiB
- experts/README.md8.6 KiB
- experts/_expert-ts.md2.2 KiB
- experts/analyzer.md14.0 KiB
- experts/bridge/app-distribution-packaging-ts.md14.2 KiB
- experts/bridge/channel-ops-graph-ts.md15.4 KiB
- experts/bridge/commands-slash-text-ts.md18.5 KiB
- experts/bridge/cross-platform-advisor-ts.md36.4 KiB
- experts/bridge/cross-platform-architecture-ts.md8.3 KiB
- experts/bridge/events-activities-ts.md22.4 KiB
- experts/bridge/files-upload-download-ts.md17.2 KiB
- experts/bridge/identity-oauth-bridge-ts.md19.8 KiB
- experts/bridge/index.md13.0 KiB
- experts/bridge/infra-compute-ts.md14.6 KiB
- experts/bridge/infra-observability-ts.md14.0 KiB
- experts/bridge/infra-secrets-config-ts.md13.2 KiB
- experts/bridge/infra-storage-ts.md14.3 KiB
- experts/bridge/interactive-responses-ts.md19.6 KiB
- experts/bridge/link-unfurl-preview-ts.md17.1 KiB
- experts/bridge/middleware-handlers-ts.md15.4 KiB
- experts/bridge/python-cross-platform.md9.3 KiB
- experts/bridge/rate-limiting-resilience-ts.md17.6 KiB
- experts/bridge/rest-only-integration-ts.md8.4 KiB
- experts/bridge/scheduling-deferred-send-ts.md17.8 KiB
- experts/bridge/shortcuts-extensions-ts.md17.5 KiB
- experts/bridge/transport-socketmode-https-ts.md14.3 KiB
- experts/bridge/ui-app-home-personal-tab-ts.md14.5 KiB
- experts/bridge/ui-block-kit-adaptive-cards-ts.md21.5 KiB
- experts/bridge/ui-legacy-attachments-cards-ts.md11.2 KiB
- experts/bridge/ui-modals-dialogs-ts.md21.4 KiB
- experts/bridge/workflow.composable-platform-ts.md13.7 KiB
- experts/bridge/workflows-automation-ts.md14.3 KiB
- experts/builder.md11.1 KiB
- experts/convert/bulk-conversion-strategy-ts.md12.8 KiB
- experts/convert/dependency-mapping-ts.md8.3 KiB
- experts/convert/index.md3.5 KiB
- experts/convert/java-to-ts-ts.md20.6 KiB
- experts/convert/js-to-ts-ts.md6.2 KiB
- experts/convert/json-serialization-ts.md11.0 KiB
- experts/convert/kotlin-to-ts-ts.md11.2 KiB
- experts/convert/ruby-to-ts-ts.md9.7 KiB
- experts/convert/type-mapping-ts.md10.1 KiB
- experts/deploy/aws-bot-deploy-ts.md14.6 KiB
- experts/deploy/aws-cli-reference-ts.md52.4 KiB
- experts/deploy/azure-bot-deploy-ts.md15.4 KiB
- experts/deploy/azure-cli-reference-ts.md16.9 KiB
- experts/deploy/index.md4.6 KiB
- experts/fallback.md2.1 KiB
- experts/index.md18.9 KiB
- experts/models/anthropic-ts.md7.8 KiB
- experts/models/bedrock-ts.md9.9 KiB
- experts/models/foundry-cloud-ts.md8.1 KiB
- experts/models/foundry-local-ts.md10.6 KiB
- experts/models/index.md5.8 KiB
- experts/models/openai-azure-openai-ts.md8.3 KiB
- experts/models/oss-openai-compatible-ts.md10.7 KiB
- experts/models/transformers-js-ts.md11.6 KiB
- experts/prompt-engineer.md14.7 KiB
- experts/researcher.md2.8 KiB
- experts/security/index.md1.2 KiB
- experts/security/input-validation-ts.md13.8 KiB
- experts/security/secrets-ts.md13.9 KiB
- experts/slack/bolt-assistant-ts.md9.9 KiB
- experts/slack/bolt-events-ts.md9.3 KiB
- experts/slack/bolt-java.md8.9 KiB
- experts/slack/bolt-oauth-distribution-ts.md10.9 KiB
- experts/slack/bolt-python.md9.5 KiB
- experts/slack/cli.app-management.md7.9 KiB
- experts/slack/cli.datastore-env.md8.6 KiB
- experts/slack/cli.getting-started.md8.0 KiB
- experts/slack/cli.local-dev-deploy.md8.4 KiB
- experts/slack/cli.manifest-triggers.md9.9 KiB
- experts/slack/index.md8.9 KiB
- experts/slack/runtime.ack-rules-ts.md9.8 KiB
- experts/slack/runtime.bolt-foundations-ts.md10.7 KiB
- experts/slack/runtime.shortcuts-ts.md11.0 KiB
- experts/slack/runtime.slash-commands-ts.md11.6 KiB
- experts/slack/runtime.socket-mode-ts.md9.5 KiB
- experts/slack/ui.block-kit-ts.md11.5 KiB
- experts/slack/ui.modals-lifecycle-ts.md13.3 KiB
- experts/slack/web-api-proactive-ts.md11.0 KiB
- experts/slack/workflow.slack-automations-ts.md10.2 KiB
- experts/teams/a2a.client-basics-ts.md9.7 KiB
- experts/teams/a2a.orchestrator-patterns-ts.md12.7 KiB
- experts/teams/a2a.server-basics-ts.md11.4 KiB
- experts/teams/ai.chatprompt-basics-ts.md8.1 KiB
- experts/teams/ai.citations-feedback-ts.md6.9 KiB
- experts/teams/ai.conversational-query-ts.md14.2 KiB
- experts/teams/ai.function-calling-design-ts.md9.0 KiB
- experts/teams/ai.function-calling-implementation-ts.md7.7 KiB
- experts/teams/ai.memory-localmemory-ts.md7.3 KiB
- experts/teams/ai.model-setup-ts.md6.6 KiB
- experts/teams/ai.rag-retrieval-ts.md7.4 KiB
- experts/teams/ai.rag-vectorstores-ts.md8.5 KiB
- experts/teams/ai.streaming-ts.md6.9 KiB
- experts/teams/auth.oauth-sso-ts.md10.1 KiB
- experts/teams/compat.botbuilder-interop-ts.md14.6 KiB
- experts/teams/dev.debug-test-ts.md14.1 KiB
- experts/teams/graph.usergraph-appgraph-ts.md9.0 KiB
- experts/teams/index.md9.8 KiB
- experts/teams/mcp.client-basics-ts.md9.5 KiB
- experts/teams/mcp.expose-chatprompt-tools-ts.md9.5 KiB
- experts/teams/mcp.security-ts.md10.4 KiB
- experts/teams/mcp.server-basics-ts.md9.9 KiB
- experts/teams/project.scaffold-files-ts.md12.2 KiB
- experts/teams/runtime.app-init-ts.md10.9 KiB
- experts/teams/runtime.manifest-ts.md12.3 KiB
- experts/teams/runtime.proactive-messaging-ts.md12.6 KiB
- experts/teams/runtime.routing-handlers-ts.md12.3 KiB
- experts/teams/state.storage-patterns-ts.md9.4 KiB
- experts/teams/teams-dotnet.md8.2 KiB
- experts/teams/teams-python.md8.3 KiB
- experts/teams/ui.adaptive-cards-ts.md12.9 KiB
- experts/teams/ui.dialogs-task-modules-ts.md15.1 KiB
- experts/teams/ui.message-extensions-ts.md15.6 KiB
- experts/teams/workflow.approvals-inline-ts.md12.4 KiB
- experts/teams/workflow.message-native-records-ts.md10.6 KiB
- experts/teams/workflow.sharepoint-lists-ts.md9.0 KiB
- experts/teams/workflow.state-driven-events-ts.md12.2 KiB
- experts/teams/workflow.triggers-compose-ts.md10.3 KiB
- experts/update-experts.md10.0 KiB
- provision-deploy/provision-deploy.md4.3 KiB
- test-playground/playground-cli.md4.6 KiB
- test-playground/playground.md4.5 KiB
- test-playground/test-playground.md1.1 KiB
- test-teams/test-teams.md4.9 KiB
- toolkit/README.md4.2 KiB
- toolkit/commands.md2.6 KiB
- toolkit/environments.md12.6 KiB
- toolkit/lifecycle-cli.md17.6 KiB
- toolkit/manifest-and-yaml.md6.0 KiB
- toolkit/playground.md7.6 KiB
- toolkit/publish.md9.3 KiB
- toolkit/templates.md6.7 KiB
- troubleshoot/troubleshoot.md20.2 KiB
experts/bridge/workflow.composable-platform-ts.md
workflow.composable-platform-ts
purpose
Architectural guide for building a composable, reusable workflow operating layer inside Teams — the five-element framework (trigger, state, logic, intelligence, visibility) as a platform pattern, not a point solution.
rules
Every workflow follows the same five-element lifecycle. (1) Trigger — how it starts, (2) State — where records live, (3) Logic — how decisions and automation execute, (4) Intelligence — how AI is layered over state, (5) Visibility — how records remain embedded in channels. Design every workflow as an instantiation of this lifecycle.
Define workflows as configuration, not code. A workflow definition specifies: trigger type + parameters, list schema (columns and types), routing rules (approval chain, auto-assign), query functions (NL schemas), and card templates (active/completed/error). The runtime consumes these definitions generically.
Use a
WorkflowDefinitioninterface as the core abstraction. This interface describes the workflow's schema, triggers, routing, and card templates. The runtime registers handlers dynamically from definitions. New workflows require a new definition object, not new handler code.Template workflows are reference implementations. Provide polished, out-of-the-box definitions for common scenarios: time-off requests, equipment booking, daily standup, account health. These serve as both usable workflows and examples for customization.
The runtime is a generic workflow engine. A single set of handlers (message,
card.action, proactive, webhooks) dispatch to the correct workflow based on the verb/command prefix in the message or action data. The engine creates records, processes actions, and renders cards for any registered workflow.SharePoint Lists are the default state backend. Each workflow definition maps to a SharePoint list. The engine creates lists on first use, following the schema in the definition. For enterprise needs, swap to Dataverse without changing the workflow definition.
Card templates are parameterized, not hardcoded. Define card templates as functions that take a record and return an Adaptive Card. The workflow definition includes templates for:
activeCard,completedCard,listCard, andformCard. The engine calls the right template based on record state.Query functions are auto-generated from the schema. Given a workflow definition's column schema, generate AI function-calling schemas automatically: each filterable column becomes a parameter. This eliminates writing per-workflow query functions manually.
Extensibility points for ecosystem partners. The composable platform should expose: (a) custom trigger types (plugin new event sources), (b) custom logic steps (plugin business rules), (c) custom card templates (brand and layout), (d) custom state backends (plugin storage). Each point has a defined interface.
Cross-workflow queries are first-class. The engine registers a
queryAnyWorkflowfunction that searches across all registered workflow lists. Users ask "what's overdue?" and get results from PTO, equipment, and standup workflows combined.Power Automate integration is optional, not required. The composable platform can execute logic in-bot (state machine) or delegate to Power Automate flows. Workflow definitions specify
executionMode: "bot" | "powerAutomate" | "hybrid". Bot mode is the default for SMB; Power Automate mode for enterprise.
patterns
WorkflowDefinition interface
interface WorkflowDefinition {
id: string; // Unique workflow identifier
name: string; // Display name
description: string; // Used in command suggestions and AI descriptions
commandPrefix: string; // e.g., "/pto", "/book", "/standup"
// Schema
columns: ColumnDefinition[]; // Maps to SharePoint List columns
statusField: string; // Which column tracks lifecycle state
statusValues: {
active: string[]; // e.g., ["Pending", "InProgress"]
completed: string[]; // e.g., ["Approved", "Rejected", "Done"]
};
// Triggers
triggers: TriggerConfig[];
// Routing
routing?: {
type: "none" | "single" | "sequential" | "parallel-any" | "parallel-all";
approverSource: "fixed" | "manager" | "field"; // Where to find the approver
approverField?: string; // Column name if approverSource is "field"
escalationTimeoutMs?: number;
};
// Cards
cards: {
active: (record: any) => object;
completed: (record: any) => object;
list: (records: any[]) => object;
form?: () => object; // For message extension action trigger
};
// AI
queryDescription: string; // Describes when AI should call the query function
filterableColumns: string[]; // Columns exposed as AI function parameters
}
interface ColumnDefinition {
name: string;
type: "text" | "number" | "dateTime" | "choice" | "personOrGroup" | "boolean";
choices?: string[]; // For choice columns
required?: boolean;
}
interface TriggerConfig {
type: "command" | "messageExtension" | "scheduled" | "stateChange";
config: Record<string, any>; // Trigger-specific configuration
}Register a workflow from a definition
function registerWorkflow(app: any, engine: WorkflowEngine, definition: WorkflowDefinition) {
// Command trigger
const commandTrigger = definition.triggers.find((t) => t.type === "command");
if (commandTrigger) {
const regex = new RegExp(`^\\${definition.commandPrefix}\\s*(.*)$`, "i");
app.message(regex, async (ctx: any) => {
await engine.handleCommand(ctx, definition);
});
}
// Scheduled trigger
const scheduledTrigger = definition.triggers.find((t) => t.type === "scheduled");
if (scheduledTrigger) {
cron.schedule(scheduledTrigger.config.cron, async () => {
await engine.handleScheduled(definition);
});
}
// Register AI query function
engine.registerQueryFunction(definition);
}Generic workflow engine
class WorkflowEngine {
private definitions = new Map<string, WorkflowDefinition>();
private graphClient: Client;
private siteId: string;
private lists = new Map<string, string>(); // workflowId -> listId
async handleCommand(ctx: any, def: WorkflowDefinition) {
const params = parseCommandParams(ctx.activity.text!, def);
const record = await this.createRecord(def, {
...params,
requesterId: ctx.activity.from?.aadObjectId,
requesterName: ctx.activity.from?.name,
conversationId: ctx.activity.conversation?.id,
serviceUrl: ctx.activity.serviceUrl,
});
const card = def.cards.active(record);
const response = await ctx.send({
attachments: [{
contentType: "application/vnd.microsoft.card.adaptive",
content: card,
}],
});
// Store activity ID for future updates
await this.updateRecordField(def, record.id, "CardActivityId", response.id);
// Start escalation timer if routing is configured
if (def.routing?.escalationTimeoutMs) {
this.startEscalation(def, record);
}
}
async handleAction(ctx: any, verb: string, data: any) {
const def = this.definitions.get(data.workflowId);
if (!def) return;
const record = await this.getRecord(def, data.recordId);
if (verb === "approve" || verb === "reject") {
return this.processApproval(ctx, def, record, verb, data.comment);
}
if (verb.startsWith("refresh")) {
const card = record.status === "completed"
? def.cards.completed(record)
: def.cards.active(record);
return {
status: 200,
body: {
statusCode: 200,
type: "application/vnd.microsoft.card.adaptive",
value: card,
},
};
}
}
registerQueryFunction(def: WorkflowDefinition) {
// Auto-generate AI function schema from definition
const parameters: Record<string, any> = {};
for (const col of def.filterableColumns) {
const colDef = def.columns.find((c) => c.name === col);
if (!colDef) continue;
switch (colDef.type) {
case "choice":
parameters[col] = { type: "string", enum: colDef.choices };
break;
case "dateTime":
parameters[col] = { type: "string", description: `Filter by ${col} (ISO date)` };
break;
case "personOrGroup":
parameters[col] = { type: "string", description: `Filter by ${col} name` };
break;
default:
parameters[col] = { type: "string" };
}
}
return {
name: `query_${def.id}`,
description: def.queryDescription,
parameters: { type: "object", properties: parameters },
};
}
private async createRecord(def: WorkflowDefinition, fields: Record<string, any>) {
const listId = await this.ensureList(def);
const item = await this.graphClient
.api(`/sites/${this.siteId}/lists/${listId}/items`)
.post({ fields });
return { id: item.id, ...item.fields };
}
private async ensureList(def: WorkflowDefinition): Promise<string> {
if (this.lists.has(def.id)) return this.lists.get(def.id)!;
// Check if list exists, create if not
try {
const existing = await this.graphClient
.api(`/sites/${this.siteId}/lists`)
.filter(`displayName eq '${def.name}'`)
.get();
if (existing.value.length > 0) {
this.lists.set(def.id, existing.value[0].id);
return existing.value[0].id;
}
} catch { /* List doesn't exist */ }
const list = await this.graphClient
.api(`/sites/${this.siteId}/lists`)
.post({
displayName: def.name,
list: { template: "genericList" },
columns: def.columns.map(colDefToGraphColumn),
});
this.lists.set(def.id, list.id);
return list.id;
}
}Template workflow: Time-Off Request
const ptoWorkflow: WorkflowDefinition = {
id: "pto",
name: "PTO Requests",
description: "Time-off and vacation request workflow",
commandPrefix: "/pto",
columns: [
{ name: "Requester", type: "personOrGroup", required: true },
{ name: "StartDate", type: "dateTime", required: true },
{ name: "EndDate", type: "dateTime", required: true },
{ name: "HoursRequested", type: "number" },
{ name: "Status", type: "choice", choices: ["Pending", "Approved", "Rejected"] },
{ name: "ApprovedBy", type: "personOrGroup" },
{ name: "Reason", type: "text" },
],
statusField: "Status",
statusValues: {
active: ["Pending"],
completed: ["Approved", "Rejected"],
},
triggers: [
{ type: "command", config: { pattern: "/pto START to END" } },
{ type: "messageExtension", config: { commandId: "createPto" } },
],
routing: {
type: "single",
approverSource: "manager",
escalationTimeoutMs: 48 * 60 * 60 * 1000, // 48 hours
},
cards: {
active: buildPtoActiveCard,
completed: buildPtoCompletedCard,
list: buildPtoListCard,
},
queryDescription: "Query PTO/time-off requests. Use when user asks about PTO, vacation, leave, days off.",
filterableColumns: ["Status", "Requester", "StartDate"],
};
// Register
registerWorkflow(app, engine, ptoWorkflow);pitfalls
Over-abstraction kills velocity. The composable platform should start with 2-3 template workflows and extract common patterns. Don't build the full generic engine before validating with real workflows.
Schema migrations are hard. Once a SharePoint List is created, adding required columns or changing types is disruptive. Version your schemas and handle missing columns gracefully.
Generic engines produce generic cards. Template card functions should be polished, not auto-generated. The best workflow UX comes from purpose-built card layouts, not generic field renderers.
Power Automate hybrid mode adds complexity. Supporting both bot-native and Power Automate execution means two code paths, two monitoring surfaces, and two failure modes. Default to bot-native for the FHL; add Power Automate later.
Ecosystem extensibility requires stable interfaces. Don't expose extension points until the core patterns stabilize through 3+ real workflow implementations.
references
instructions
Use this expert when designing the overall composable workflow architecture. Covers the five-element lifecycle framework, WorkflowDefinition interface, generic engine patterns, template workflows, auto-generated AI query schemas, and extensibility points. Pair with ../teams/workflow.sharepoint-lists-ts.md for state persistence, ../teams/workflow.message-native-records-ts.md for card-as-record patterns, ../teams/workflow.triggers-compose-ts.md for trigger unification, ../teams/ai.conversational-query-ts.md for NL retrieval, and ../teams/workflow.approvals-inline-ts.md for approval routing.
research
Deep Research prompt:
"Write a micro expert on designing a composable workflow platform inside Microsoft Teams (TypeScript). Cover: five-element lifecycle framework (trigger, state, logic, intelligence, visibility), WorkflowDefinition configuration interface, generic workflow engine that dispatches from definitions, template/reference workflows (PTO, equipment, standup), auto-generated AI function schemas from column definitions, SharePoint Lists as pluggable state backend, Power Automate hybrid execution mode, and ecosystem extensibility points. Include complete patterns for the definition interface, engine registration, and one template workflow."
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an API key, Needs Python, Needs Node.js
Security
What our scanner noticed· Medium risk
- Possible data-exfiltration endpoints
- Instructions that use the network
- Downloads piped into a shell
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Microsoft
- Publisher
- Microsoft (Official)
- Source
- microsoft/skills · .github/plugins/microsoft-365-agents-toolkit/skills/teams-app-developer · commit 0696600
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Microsoft.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download teams-app-developer.zip