azure-bootstrap-typescript

Integrate Next.js apps with Python azure-bootstrap backends and port its primitives to TypeScript.

1|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill azure-bootstrap-typescript-theviziusgroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-bootstrap-typescript
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/azure-bootstrap/skills/azure-bootstrap-typescript
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill azure-bootstrap-typescript-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? The azure-bootstrap library is pure Python with no npm distribution, so TypeScript/Next.js teams cannot import it directly. This Skill documents the exact HTTP contract a Python azure-bootstrap backend exposes and provides native TypeScript reimplementations of its framework-agnostic primitives, including HMAC action tokens that interoperate byte-for-byte with the Python side. ## Core Features & Use Cases - HTTP Client Integration: Typed Next.js App Router code for x-api-key endpoints (401/429 handling), Graph-style webhook validationToken handshake and notification batches, health probes, and the /api/metrics snapshot shape. - TypeScript Pattern Ports: Drop-in reimplementations of structured JSON logging, AsyncLocalStorage correlation context, mask_* helpers, in-memory counters, TokenBucket rate limiting, and constant-time secret comparison. - Interoperable HMAC Tokens: Issue and verify base64url(json).base64url(hmac_sha256) action tokens in Node.js that a Python backend accepts, enabling cross-language admin flows like DLQ resubmission. - Use Case: A Next.js admin dashboard needs to call a FastAPI backend built on azure-bootstrap and issue a dlq_resubmit token the Python Service Bus consumer can verify; this Skill provides the exact client code and token helper. ## Quick Start Ask the AI to generate a typed Next.js client and webhook route handler for a Python azure-bootstrap backend, including an HMAC action token helper compatible with Python's tokens module.

Frequently Asked Questions about azure-bootstrap-typescript

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

FAQPage Schema
How do I call a Python azure-bootstrap backend from Next.js?

Call the backend over HTTP from a server-side Route Handler or Server Action, sending the x-api-key header from a server-only environment variable. Handle 401 for unauthorized, 429 for rate limiting with empty bodies, and never expose the key via NEXT_PUBLIC_* variables.

How do I handle a Graph webhook validationToken in Next.js?

Return the validationToken query parameter as a 200 plaintext response for the subscription handshake. For live notifications, verify clientState with a constant-time comparison, then return 202 on success, 401 on mismatch, or 400 for malformed JSON.

Can I install azure-bootstrap from npm for a TypeScript project?

No, azure-bootstrap is a pure Python package with no JavaScript or TypeScript distribution. You either call a Python backend over its HTTP contract or use the native TypeScript reimplementations of its primitives such as logging, token buckets, and HMAC tokens.

How do I make HMAC tokens in Node.js that Python can verify?

Use the base64url(json).base64url(hmac_sha256) format with sorted keys and compact separators matching Python's json.dumps output. Keep payload values to JSON primitives, share the same secret on both sides, and verify with timingSafeEqual.

Why does the webhook endpoint return 401 for all requests?

The endpoint returns 401 when GRAPH_WEBHOOK_CLIENT_STATE is unset or when the clientState value does not match under constant-time comparison. Set the environment variable on the backend and ensure the sender includes the matching clientState.

Does the in-memory TokenBucket work on serverless deployments?

In-process token buckets only protect a single Node instance. On Vercel, serverless, or multi-replica deployments, back the rate limiter with a shared store such as Redis or Upstash to enforce a consistent budget.