Pikku Project Discovery

VerifiedSafe

Inspect a Pikku project structure including functions, tags, middleware, permissions, HTTP routes, and more. Use to understand existing codebase architecture and locate project components.

Sby Skills Guide Bot
DevelopmentBeginner
306/2/2026
Claude Code
#pikku#project-discovery#cli#inspection#codebase-analysis

Recommended for

Our review

This skill uses the `pikku info` CLI commands to inspect a Pikku project and list its functions, tags, middleware, permissions, and other project structure elements.

Strengths

  • Provides a quick, comprehensive overview of the project.
  • Supports filtering by type (functions, tags, middleware, permissions).
  • Silent mode to suppress unnecessary logs.
  • Verbose option for in-depth details (source file, required services).

Limitations

  • Only works for projects using the Pikku framework.
  • Requires the project to be installed and `yarn` to be available.
  • Cannot visualize dependencies between modules.
When to use it

Explore an existing Pikku project to understand its structure, routes, middleware, and permissions.

When not to use it

Avoid using when writing new code (use the specific wiring skill instead) or when asking about Pikku concepts (use pikku-concepts).

Security analysis

Safe
Quality score90/100

The skill only runs `yarn pikku info` commands with safe arguments (`--silent`, `--verbose`, `--limit`). These are read-only project inspection commands. No destructive actions, exfiltration, or external network calls are involved. The Bash tool is restricted to the pattern `yarn pikku info *`.

No concerns found

Examples

List all functions
List all registered pikku functions in the project, including transport types and middleware.
Show project structure overview
Give me a complete overview of this Pikku project: list all functions, tags, middleware, and permissions.
Get middleware details
Show me all middleware with full details including source files and required services.

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