azure-functions
Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js programming models.
Profile →npx skills add sickn33/agentic-awesome-skills --skill azure-functions --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Translates to a guide that outlines multiple Azure Functions execution patterns across languages and hosting models, including an Isolated Worker Model for .NET, Node.js v4, Python v2, and Durable Functions scenarios (Function Chaining, Fan-Out/Fan-In), plus Cold Start Optimization and Queue Trigger with Error Handling. It includes concrete code templates, notes, and setup steps intended to help build production-ready Azure Functions apps.
How it works
- Describes each pattern with a title (e.g., Isolated Worker Model (.NET), Node.js v4 Programming Model, Python v2 Programming Model, Durable Functions variants, Cold Start Optimization, Queue Trigger).
- For each pattern, provides code templates and usage notes that show how to implement the pattern in the respective language/runtime.
- Includes notes clarifying model characteristics (e.g., in-process vs isolated, decorators, code-centric approach, pre-warmed instances, and retry/poison handling behavior).
- Organizes content under named sections (Isolated Worker Model, Durable Functions - Function Chaining, Durable Functions - Fan-Out/Fan-In, Cold Start Optimization, Queue Trigger with Error Handling) with example functions, triggers, and DI usage where applicable.
When to use it
- When starting new .NET Azure Functions apps with an isolated worker model.
- When building Node.js-based Azure Functions using the v4 programming model.
- When developing Python-based Azure Functions with decorators and out-of-process hosting.
- When needing durable orchestrations (Order orchestration, fan-out/fan-in) and their initialization/trigger patterns.
- When addressing cold start latency and planning deployment/architecture (Premium Plan, warmup, DI, and packaging tips).
- When implementing robust queue-trigger processing with error handling and poison queue monitoring.
What it can touch
- Shows integration points for DI (e.g., AddHttpClient, AddSingleton), hosting and deployment details, and various function triggers (HttpTrigger, TimerTrigger, BlobTrigger, QueueTrigger).
- Includes code snippets referencing function and trigger names, namespaces, and attributes as written in the patterns.
Caveats
- Notes indicate model limitations and operational considerations, such as the deprecation of the in-process model for .NET and platform requirements (Linux-based hosting for Python).
- Includes operational guidance like warmup triggers, pre-warmed instances, and deployment steps that affect cold starts.
- No explicit licensing or risk beyond labeled risk: none; license is MIT for the skill as a whole.
# Azure Functions Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js programming models. ## Patterns ### Isolated Worker Model (.NET) Modern .NET execution model with process isolation **When to use**: Building new .NET Azure Functions apps ### Template // Program.cs - Isolated Worker Model using Microsoft.Azure.Functions.Worker; using Microsoft.Extensions.DependencyInjection; using Microsoft.Extensions.Hosting; var host = new HostBuilder() .ConfigureFunctionsWorkerDefaults() .ConfigureServices(services => { // Add Application Insights services.AddApplicationInsightsTelemetryWorkerService(); services.ConfigureFunctionsApplicationInsights(); // Add HttpClientFactory (prevents socket exhaustion) services.AddHttpClient(); // Add your services services.AddSingleton<IMyService, MyService>(); }) .Build(); host.Run(); // HttpTriggerFunction.cs using Microsoft.Azure.Functions.Worker; using Microsoft.Azure.Functions.Worker.Http; using Microsoft.Extensions.Logging; public class HttpTriggerFunction { private readonly ILogger<HttpTriggerFunction> _lo
- Patterns
- Isolated Worker Model (.NET)
- Template
- Notes
- Node.js v4 Programming Model
- Python v2 Programming Model
- Durable Functions - Function Chaining
- Durable Functions - Fan-Out/Fan-In
- Cold Start Optimization
- Queue Trigger with Error Handling
- HTTP Trigger with Long-Running Pattern
- Sharp Edges
- HTTP Timeout is 230 Seconds Regardless of Plan
- Use async pattern with Durable Functions
Create new isolated worker project func init MyFunctionApp --worker-runtime dotnet-isolated Or with .NET 8 dotnet new func --name MyFunctionApp --framework net8.0 Check registered functions func host start --verbose Look for: If empty, check extensions and attributes Increase pre-warmed instances (costs more) az functionapp config set \
What does the azure-functions skill do?
Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js programming models.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill azure-functions --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.