typespec-api-operations

Generate CRUD REST operations with routing and parameters for TypeSpec API plugins.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill typespec-api-operations-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typespec-api-operations
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/typespec-api-operations
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill typespec-api-operations-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline API plugin development by automatically scaffold CRUD REST operations (GET, POST, PATCH, DELETE) for a TypeSpec API plugin, including routing and parameter handling, plus optional adaptive card integrations for UI renderings.

Core Features & Use Cases

  • Generate complete CRUD endpoints (GET, POST, PATCH, DELETE) for a TypeSpec service with proper routing and parameter definitions.
  • Support advanced use cases: query/path/body parameters, multiple models, and optional adaptive cards for visualizing results.
  • Use Case: A developer wants a ready-to-use API namespace to manage items with minimal boilerplate, including UI cards for Copilot responses.

Quick Start

Scaffold a new TypeSpec API namespace with GET, POST, PATCH, and DELETE operations and adaptive cards as demonstrated.

Frequently Asked Questions about typespec-api-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add CRUD REST operations to a TypeSpec API?

To add CRUD REST operations to a TypeSpec API, use this skill to scaffold GET, POST, PATCH, and DELETE endpoints with proper routing, path and query parameters, and optional adaptive cards for UI rendering.

What is the best way to generate REST API routing and parameters in TypeSpec?

Generating REST API routing and parameters in TypeSpec is done by applying specific TypeSpec syntax and decorators to define routes, path parameters, and query parameters while adhering to RESTful routing conventions.

Can I include adaptive cards in TypeSpec API operations for Copilot responses?

Yes, you can include adaptive cards in TypeSpec API operations to provide visual UI renderings, enabling ready-to-use API namespaces that return interactive cards for Copilot responses with minimal boilerplate.

Do I need specific TypeSpec decorators to define API service operations?

Yes, you need specific TypeSpec syntax and decorators to define API service operations, as the skill requires these decorators to properly map HTTP verbs like GET, POST, PATCH, and DELETE to your routing structure.

Does this TypeSpec scaffolding support body parameters for POST and PATCH requests?

This TypeSpec scaffolding supports body parameters for POST and PATCH requests, handling advanced use cases that include query, path, and body parameters alongside multiple models for complete endpoint generation.