pikkujs/pikku-info
.claude/skills/pikku-info/SKILL.md
Discover what exists in a Pikku project — functions, tags, middleware, permissions, HTTP routes, channels, schedulers, queues, and more. Use when you need to understand the project structure, find existing functions, or check what middleware and permissions are defined. TRIGGER when: user asks "what functions exist?", "show me the project structure", "list routes/middleware/permissions", or needs to understand an existing Pikku codebase. DO NOT TRIGGER when: user is writing new code (use the specific wiring skill) or asking about Pikku concepts (use pikku-concepts).
$ install --global
skillsauthnpx skillsauth add pikkujs/pikku pikku-infoInstall 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: Apr 15, 2026, 9:50 PM6.8s1 file scanned
SKILL.md
- name:
- pikku-info
- description:
- Discover what exists in a Pikku project — functions, tags, middleware, permissions, HTTP routes, channels, schedulers, queues, and more. Use when you need to understand the project structure, find existing functions, or check what middleware and permissions are defined.
- TRIGGER when:
- user asks "what functions exist?", "show me the project structure", "list routes/middleware/permissions", or needs to understand an existing Pikku codebase.
- DO NOT TRIGGER when:
- user is writing new code (use the specific wiring skill) or asking about Pikku concepts (use pikku-concepts).
- allowed-tools:
- Bash(yarn pikku info *)
- argument-hint:
- [functions|tags|middleware|permissions] [--verbose] [--limit N]
Pikku Project Discovery
Use the pikku info CLI commands to inspect this Pikku project. Run the commands below and present the results to the user in a clear summary.
Available Commands
Always use --silent to suppress the banner and inspector logs.
Functions
List all registered pikku functions:
yarn pikku info functions --silent
For full details including transport type (http/channel/scheduler/queue/workflow/mcp/cli/trigger), middleware, permissions, and source file:
yarn pikku info functions --verbose --silent
Tags
List all tags with counts of associated functions, middleware, and permissions:
yarn pikku info tags --silent
For full names instead of counts:
yarn pikku info tags --verbose --silent
Middleware
List all middleware definitions:
yarn pikku info middleware --silent
For full details including source file, required services, and description:
yarn pikku info middleware --verbose --silent
Permissions
List all permission definitions:
yarn pikku info permissions --silent
For full details including source file, required services, and description:
yarn pikku info permissions --verbose --silent
Instructions
- If the user specifies a subcommand (e.g.,
/pikku-info functions), run only that command. - If no subcommand is specified, run all four commands to give a complete project overview.
- Always use
--silentto suppress the Pikku banner and inspector logs. - Use
--verbosewhen the user asks for details, file paths, or "more info". - Use
--limit Nto control output size (default is 50 rows). - After running the commands, summarize the findings concisely:
- Total count of functions, tags, middleware, and permissions
- Notable patterns (e.g., which transport types are in use, which tags group the most functions)
- Any functions without tags or transport types (potential issues)
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