azure
Azure cloud services SDK integration. Azure Functions, Cosmos DB, Blob Storage, Service Bus, Azure AD (Entra ID), and Key Vault. Node.js and .NET SDKs. USE WHEN: user mentions "Azure", "Azure Functions", "Cosmos DB", "Blob Storage", "Service Bus", "Azure AD", "Entra ID", "Key Vault", "Azure SDK" DO NOT USE FOR: AWS services - use `aws`; GCP services - use `gcp`; Terraform for Azure - use `terraform`
What this skill does
# Azure SDK Integration
## Azure Functions
```typescript
import { app, HttpRequest, HttpResponseInit, InvocationContext } from '@azure/functions';
app.http('getProduct', {
methods: ['GET'],
authLevel: 'anonymous',
route: 'products/{id}',
handler: async (req: HttpRequest, context: InvocationContext): Promise<HttpResponseInit> => {
const id = req.params.id;
const product = await getProduct(id);
return { status: 200, jsonBody: product };
},
});
// Queue trigger
app.serviceBusQueue('processOrder', {
connection: 'ServiceBusConnection',
queueName: 'orders',
handler: async (message: unknown, context: InvocationContext) => {
const order = message as Order;
await processOrder(order);
},
});
// Timer trigger (cron)
app.timer('dailyCleanup', {
schedule: '0 0 2 * * *',
handler: async (timer, context) => {
await cleanupExpiredSessions();
},
});
```
## Cosmos DB
```typescript
import { CosmosClient } from '@azure/cosmos';
const client = new CosmosClient(process.env.COSMOS_CONNECTION_STRING!);
const container = client.database('mydb').container('products');
// Create
await container.items.create({ id: '123', name: 'Widget', price: 19.99, category: 'tools' });
// Read
const { resource } = await container.item('123', 'tools').read();
// Query
const { resources } = await container.items
.query({
query: 'SELECT * FROM c WHERE c.category = @cat AND c.price < @maxPrice',
parameters: [
{ name: '@cat', value: 'tools' },
{ name: '@maxPrice', value: 50 },
],
})
.fetchAll();
```
## Blob Storage
```typescript
import { BlobServiceClient } from '@azure/storage-blob';
const blobService = BlobServiceClient.fromConnectionString(process.env.AZURE_STORAGE_CONNECTION!);
const container = blobService.getContainerClient('uploads');
// Upload
const blockBlob = container.getBlockBlobClient(`files/${filename}`);
await blockBlob.uploadData(buffer, {
blobHTTPHeaders: { blobContentType: contentType },
});
// Download
const downloadResponse = await blockBlob.download(0);
const content = await streamToBuffer(downloadResponse.readableStreamBody!);
// Generate SAS URL
import { generateBlobSASQueryParameters, BlobSASPermissions } from '@azure/storage-blob';
const sasUrl = blockBlob.generateSasUrl({
permissions: BlobSASPermissions.parse('r'),
expiresOn: new Date(Date.now() + 3600 * 1000),
});
```
## Service Bus
```typescript
import { ServiceBusClient } from '@azure/service-bus';
const sbClient = new ServiceBusClient(process.env.SERVICE_BUS_CONNECTION!);
// Send
const sender = sbClient.createSender('orders');
await sender.sendMessages({ body: { orderId: '123', status: 'created' } });
// Receive
const receiver = sbClient.createReceiver('orders');
const messages = await receiver.receiveMessages(10, { maxWaitTimeInMs: 5000 });
for (const msg of messages) {
await processOrder(msg.body);
await receiver.completeMessage(msg);
}
```
## Authentication (DefaultAzureCredential)
```typescript
import { DefaultAzureCredential } from '@azure/identity';
// Works in all environments: local dev, Azure VMs, App Service, AKS
const credential = new DefaultAzureCredential();
// Use with any Azure SDK client
const blobService = new BlobServiceClient(
`https://${accountName}.blob.core.windows.net`,
credential,
);
```
## Anti-Patterns
| Anti-Pattern | Fix |
|--------------|-----|
| Connection strings in code | Use `DefaultAzureCredential` + managed identity |
| Not using partition keys (Cosmos DB) | Design partition key for query patterns |
| Polling Service Bus | Use event-driven triggers or `receiveMessages` |
| No retry configuration | Azure SDKs retry automatically — configure `retryOptions` |
| Hardcoded resource names | Use environment variables or App Configuration |
## Production Checklist
- [ ] Managed identity for authentication (no secrets in config)
- [ ] DefaultAzureCredential for local + cloud parity
- [ ] Key Vault for secrets management
- [ ] Application Insights for monitoring
- [ ] Resource tagging for cost management
- [ ] Network security (VNet integration, private endpoints)
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".