Pikku Project Discovery

VerifiedSafe

Inspect the complete structure of a Pikku project: functions, tags, middleware, permissions, HTTP routes, and more. Use to understand existing architecture and identify defined components.

Sby Skills Guide Bot
DevelopmentBeginner
206/2/2026
Claude CodeWindsurfCursor
#pikku#project-discovery#cli#inspection

Recommended for

Our review

This skill inspects a Pikku project by listing functions, middleware, permissions, and tags using CLI commands.

Strengths

  • Provides a quick overview of project structure without manual inspection.
  • Supports verbose mode for detailed information including file paths and required services.
  • Uses --silent flag to suppress banners and inspector logs for cleaner output.

Limitations

  • Only works within a Pikku project with yarn and pikku installed.
  • Does not analyze code semantics beyond registered items (e.g., function internals).
When to use it

Use it to understand the existing architecture of a Pikku project, list all functions, middleware, permissions, or find functions without tags or transport types.

When not to use it

Avoid it when writing new code or needing conceptual explanations of Pikku (use specific wiring skills or pikku-concepts instead).

Security analysis

Safe
Quality score90/100

The skill only runs read-only `yarn pikku info` commands that inspect a project's structure, with no destructive, exfiltrating, or obfuscated actions.

No concerns found

Examples

List all functions
Show me all the functions that exist in this Pikku project.
Full project overview
Give me a complete overview of this Pikku project including functions, middleware, permissions, and tags.
Middleware details with files
List all middleware with verbose details, including source files and descriptions.

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

  1. If the user specifies a subcommand (e.g., /pikku-info functions), run only that command.
  2. If no subcommand is specified, run all four commands to give a complete project overview.
  3. Always use --silent to suppress the Pikku banner and inspector logs.
  4. Use --verbose when the user asks for details, file paths, or "more info".
  5. Use --limit N to control output size (default is 50 rows).
  6. 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