.claude/skills/pikku-deploy-azure/SKILL.md
Use when deploying a Pikku app to Azure Functions. Covers PikkuAzFunctionsLogger and PikkuAzTimerRequest for Azure Functions runtime. TRIGGER when: user asks about Azure Functions, Azure deployment, or @pikku/azure-functions. DO NOT TRIGGER when: user asks about AWS Lambda (use pikku-deploy-lambda) or Cloudflare Workers (use pikku-deploy-cloudflare).
npx skillsauth add pikkujs/pikku pikku-deploy-azureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
@pikku/azure-functions provides Azure Functions runtime adapters for Pikku.
yarn add @pikku/azure-functions @azure/functions
PikkuAzFunctionsLoggerLogger implementation that integrates with Azure Functions' built-in logging context.
PikkuAzTimerRequestTimer trigger request handler for running Pikku scheduled functions as Azure Timer Triggers.
import { app } from '@azure/functions'
import { PikkuAzFunctionsLogger } from '@pikku/azure-functions'
app.http('api', {
methods: ['GET', 'POST', 'PUT', 'DELETE'],
route: '{*path}',
handler: async (request, context) => {
const logger = new PikkuAzFunctionsLogger(context)
// Wire Pikku HTTP runner with Azure request/response
},
})
import { app } from '@azure/functions'
import { PikkuAzTimerRequest } from '@pikku/azure-functions'
app.timer('scheduler', {
schedule: '0 */5 * * * *',
handler: async (timer, context) => {
const request = new PikkuAzTimerRequest(timer)
// Process scheduled Pikku functions
},
})
documentation
Deprecated — use pikku-middleware instead. Tag middleware (addTagMiddleware) is now documented as a section within the pikku-middleware skill, alongside global HTTP middleware, execution order, and the service-to-service bearer auth pattern.
testing
Use when adding authorization checks to Pikku functions or routes — pikkuPermission, pikkuAuth, per-function permissions, pattern-based permissions, or understanding OR/AND permission logic. TRIGGER when: user wants to restrict who can call a function, check resource ownership, add role-based access, or understand where permission checks belong. DO NOT TRIGGER when: user asks about middleware or request interception (use pikku-middleware), authentication strategies (use pikku-security), or session management.
testing
Use when adding any middleware to a Pikku app — global HTTP middleware, tag-scoped middleware (including service-to-service bearer auth), per-route middleware, session-setting middleware, or understanding middleware execution order and priority. TRIGGER when: user wants middleware on some or all routes, machine-to-machine auth, tag-scoped cross-cutting concerns, global interceptors, or middleware priority/order questions. DO NOT TRIGGER when: user asks about permissions/authorization checks (use pikku-permissions), auth strategies like authBearer/authCookie (use pikku-security), or deployment.
documentation
Standard cleanup to run right after a Pikku template is cloned or scaffolded into a new project. TRIGGER when: a Pikku template was just cloned/scaffolded (via `pikku create`, `git clone <template>`, or the user says "I cloned the kanban template / starter / template"), or the working tree still looks like an untouched template (template README, placeholder `@project/*` name in package.json). DO NOT TRIGGER when: working in an established project mid-feature, or editing the template repo itself.