pikkujs/pikku-gateway-slack
packages/cli/skills/pikku-gateway-slack/SKILL.md
Use when integrating Slack with a Pikku app. Covers SlackGatewayAdapter, slash commands, OAuth flow, message handling, and signature verification. TRIGGER when: code uses SlackGatewayAdapter, parseSlashCommand, buildSlackInstallUrl, or user asks about Slack integration, Slack bots, or @pikku/gateway-slack. DO NOT TRIGGER when: user asks about general gateway/webhook patterns (use pikku-trigger).
$ install --global
skillsauthnpx skillsauth add pikkujs/pikku pikku-gateway-slackInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 6:05 AM215.7s1 file scanned
SKILL.md
- name:
- pikku-gateway-slack
- description:
- Use when integrating Slack with a Pikku app. Covers SlackGatewayAdapter, slash commands, OAuth flow, message handling, and signature verification.
- TRIGGER when:
- code uses SlackGatewayAdapter, parseSlashCommand, buildSlackInstallUrl, or user asks about Slack integration, Slack bots, or @pikku/gateway-slack.
- DO NOT TRIGGER when:
- user asks about general gateway/webhook patterns (use pikku-trigger).
Pikku Gateway Slack
Agent Operating Procedure
Use this skill as an execution checklist, not reference material.
- Discover before editing. Prefer OpenCode tools such as
pikku-metawhen available; otherwise run the relevantpikku meta ... --jsoncommand and inspect only the focused output you need. - Identify the source files that own the behavior. Do not start by reading generated output,
.pikku,node_modules, vendored packages, or broad build artifacts. - Make the smallest source change that satisfies the task. Keep generated files generated, and avoid hand-editing SDKs, schema output, or typegen.
- Validate with the narrowest relevant command first, then run
pikku-verifyorpikku allwhen functions, wirings, schemas, or generated clients may have changed. - If validation fails, fix the source cause and rerun validation. Do not paper over generated errors by editing generated files.
@pikku/gateway-slack provides a Slack Events API gateway adapter, slash command handling, OAuth installation flow, and message utilities.
Installation
yarn add @pikku/gateway-slack @slack/web-api
API Reference
SlackGatewayAdapter
import { SlackGatewayAdapter } from '@pikku/gateway-slack'
const adapter = new SlackGatewayAdapter(options: SlackGatewayAdapterOptions)
Bridges Slack Events API webhooks with Pikku's gateway system for processing Slack events as Pikku functions.
SlackGatewayHelper
Helper for handling Slack messages and metadata within gateway functions.
Slash Commands
import { parseSlashCommand, respondToSlashCommand } from '@pikku/gateway-slack'
const command = parseSlashCommand(request)
await respondToSlashCommand(responseUrl, { text: 'Done!' })
OAuth Flow
import {
buildSlackInstallUrl,
exchangeSlackOAuthCode,
RECOMMENDED_BOT_SCOPES,
} from '@pikku/gateway-slack'
const installUrl = buildSlackInstallUrl({
clientId: config.slackClientId,
scopes: RECOMMENDED_BOT_SCOPES,
redirectUri: config.slackRedirectUri,
})
const tokens = await exchangeSlackOAuthCode({
clientId: config.slackClientId,
clientSecret: config.slackClientSecret,
code: oauthCode,
redirectUri: config.slackRedirectUri,
})
Signature Verification
import { verifySlackSignature } from '@pikku/gateway-slack'
verifySlackSignature(signingSecret, timestamp, body, signature)
Usage Patterns
Slack Bot Gateway
import { SlackGatewayAdapter } from '@pikku/gateway-slack'
const slackGateway = new SlackGatewayAdapter({
signingSecret: config.slackSigningSecret,
botToken: config.slackBotToken,
})
// Register with your HTTP runner to handle /slack/events endpoint
Slash Command Handler
const handleSlashCommand = pikkuSessionlessFunc({
title: 'Handle Slack Command',
func: async ({ db }, data) => {
const command = parseSlashCommand(data)
// Process command...
await respondToSlashCommand(command.response_url, {
text: `Processed: ${command.text}`,
})
},
})
Related Skills
pikkujs/pikku-tag-middleware
documentation
VerifiedTrustedCommunity
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.
56SKILL.mdUpdated Jun 10, 2026
pikkujs/pikku-permissions
testing
VerifiedTrustedCommunity
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.
56SKILL.mdUpdated Jun 10, 2026
pikkujs/pikku-middleware
testing
VerifiedTrustedCommunity
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.
56SKILL.mdUpdated Jun 10, 2026
pikkujs/pikku-template-clone
documentation
VerifiedTrustedCommunity
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.
56SKILL.mdUpdated Jun 4, 2026