postman

Generate Postman collections and environments from Azure Functions APIs.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/lcmassena/AI_Skills --skill postman-lcmassena
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postman
Source: https://github.com/lcmassena/AI_Skills/tree/main/hexagonal-architect/postman
Command: npx skills add https://github.com/lcmassena/AI_Skills --skill postman-lcmassena

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Azure Functions projects often struggle to keep Postman API documentation aligned with code and to manage environment-specific configurations. This skill provides a structured approach to create, organize, and automate Postman collections and environments for Azure Functions APIs, enabling consistent collaboration and deployment-ready documentation.

Core Features & Use Cases

  • Create and maintain Postman collections for Azure Functions APIs, including environment configuration for Local, Dev, QA, and Prod.
  • Document API endpoints and automate API discovery from Azure Functions to keep documentation in sync with code.
  • Store collections in source control and provide a clear folder structure for teams to collaborate.

Quick Start

Import your Azure Functions project, enable automatic discovery, and generate Postman collections with environments for Local, Dev, QA, and Prod.

Frequently Asked Questions about postman

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

FAQPage Schema
How do I generate Postman collections for Azure Functions APIs?

You generate Postman collections for Azure Functions by extracting HTTP trigger metadata and mapping routes to API paths. This produces a .postman structure with collections, environment configurations for Local, Dev, QA, and Prod, and a collection-level definition.

What is the best way to keep Postman API documentation in sync with Azure Functions code?

The best way to keep Postman API documentation in sync with Azure Functions code is to automate API discovery directly from the codebase. This extracts HTTP trigger metadata and automatically updates your Postman collection structure whenever your functions change.

Can I manage different environment configurations for my Azure Functions API in Postman?

Yes, you can manage different environment configurations for Azure Functions APIs in Postman. The generated .postman structure includes specific environment setups for Local, Dev, QA, and Prod, enabling consistent collaboration across deployment-ready documentation.

Does Azure Functions API Postman automation support storing collections in source control?

Yes, Azure Functions API Postman automation supports storing collections in source control. It generates a clear folder structure with YAML requests and collection-level definitions, allowing teams to collaborate and maintain deployment-ready API documentation.

Why do I need automated API discovery for Azure Functions Postman collections?

You need automated API discovery for Azure Functions Postman collections to prevent documentation drift. By automatically extracting HTTP trigger metadata and mapping routes to API paths, it ensures your Postman YAML requests accurately reflect the current codebase.