typespec-create-api-plugin

Solid

Generate a TypeSpec API plugin with REST operations, authentication, and Adaptive Cards for Microsoft 365 Copilot

API & Backend 34,233 stars 4188 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Create TypeSpec API Plugin Create a complete TypeSpec API plugin for Microsoft 365 Copilot that integrates with external REST APIs. ## Requirements Generate TypeSpec files with: ### main.tsp - Agent Definition ```typescript import "@typespec/http"; import "@typespec/openapi3"; import "@microsoft/typespec-m365-copilot"; import "./actions.tsp"; using TypeSpec.Http; using TypeSpec.M365.Copilot.Agents; using TypeSpec.M365.Copilot.Actions; @agent({ name: "[Agent Name]", description: "[Description]" }) @instructions(""" [Instructions for using the API operations] """) namespace [AgentName] { // Reference operations from actions.tsp op operation1 is [APINamespace].operationName; } ``` ### actions.tsp - API Operations ```typescript import "@typespec/http"; import "@microsoft/typespec-m365-copilot"; using TypeSpec.Http; using TypeSpec.M365.Copilot.Actions; @service @actions(#{ nameForHuman: "[API Display Name]", descriptionForModel: "[Model description]", descriptionForHuman: "[User description]" }) @server("[API_BASE_URL]", "[API Name]") @useAuth([AuthType]) // Optional namespace [APINamespace] { @route("[/path]") @get @action op operationName( @path param1: string, @query param2?: string ): ResponseModel; model ResponseModel { // Response structure } } ``` ## Authentication Options Choose based on API requirements: 1. **No Authentication** (Public APIs) ```typescript // No @useAuth decorator needed ``` 2. **...

Details

Author
github
Repository
github/awesome-copilot
Created
11 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

typespec-create-agent

Generate a complete TypeSpec declarative agent with instructions, capabilities, and conversation starters for Microsoft 365 Copilot

34,233 Updated today
github
AI & Automation Solid

typespec-api-operations

Add GET, POST, PATCH, and DELETE operations to a TypeSpec API plugin with proper routing, parameters, and adaptive cards

34,233 Updated today
github
AI & Automation Solid

typespec-sdk-generator

Microsoft TypeSpec-based API and SDK generation

1,160 Updated today
a5c-ai
API & Backend Listed

specgen-spring-jpa-restapi

Generate a detailed specification document for building a Spring Boot 3 REST API application with Spring Modulith packaging. Database (MongoDB, PostgreSQL, MySQL, or none), authentication (Keycloak OAuth2 Resource Server, Spring Security JWT, or none), scheduling (Quartz + Spring Batch or none), and messaging (RabbitMQ pub/sub or none) are configurable based on user input. Standardized input: application name (mandatory), version (mandatory), module (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new Spring Boot REST API application. Also trigger when the user says things like "spec out a new REST API project", "design a Spring Boot API skeleton", "write a technical spec for my new API", "scaffold spec for a REST API", or any request for a specification document describing a Spring Boot REST API application. Even if the user only mentions a subset of the stack (e.g., "Spring Boot API" or "Spring REST with MySQL" or "Spring Boot A

3 Updated 3 days ago
rashidee
Web & Frontend Listed

specgen-react-mui

Generate a detailed specification document for building a React SPA (Single Page Application) using React 19, TypeScript 5, Vite 6, Material UI (MUI) v6, React Router v7, TanStack Query v5, Zustand v5, React Hook Form v7, and Zod v3. Authentication (Keycloak OAuth2/OIDC PKCE, generic OIDC, or none), API integration (REST via Axios), and optional features (WebSocket, i18n, MUI X Data Grid, MUI X Charts) are configurable based on user input. Standardized input: application name (mandatory), version (mandatory), module (optional). Use this skill whenever the user asks to create a spec, specification, blueprint, or technical design document for a new React SPA or frontend application. Also trigger when the user says things like "spec out a new React project", "design a React SPA", "write a technical spec for my new frontend app", "scaffold spec for a React MUI app", or any request for a specification document describing a React + MUI + TypeScript application. Even if the user only mentions a subset of the stack (

3 Updated 3 days ago
rashidee