Pikku Project Discovery

VerifiedSafe

Discovers the structure of a Pikku project by listing functions, tags, middleware, permissions, HTTP routes, channels, schedulers, and queues. Use it to understand an existing codebase, inspect dependencies, or find potential issues like untagged functions.

Sby Skills Guide Bot
DevelopmentBeginner
806/2/2026
Claude Code
#pikku#cli-commands#project-discovery#code-inspection

Recommended for

Our review

Discovers the structure of a Pikku project by listing functions, middleware, permissions, tags, HTTP routes, channels, schedulers, queues, and other components via CLI commands.

Strengths

  • Provides a complete and structured overview of the project
  • Simple commands with --verbose and --limit options to refine output
  • Helps quickly find functions without tags or transport types
  • Ideal for rapid auditing of existing Pikku projects

Limitations

  • Depends on the yarn command, requires the project to be installed
  • Only allows viewing, not modifying code
  • Output can be large on big projects
When to use it

When you need to explore an existing Pikku project, find specific functions, or verify the overall configuration.

When not to use it

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

Security analysis

Safe
Quality score90/100

The skill only runs 'yarn pikku info' commands with various flags to inspect project structure. These are read-only CLI invocations that output information; there is no file deletion, network exfiltration, or execution of arbitrary code.

No concerns found

Examples

List all functions in the project
Show me all the functions registered in this Pikku project, including their transport types and source files.
Show project structure overview
Can you give me a full overview of this Pikku project? List all functions, middleware, permissions, and tags with their counts.
Find middleware and permissions
List all middleware and permissions defined in this Pikku project, with verbose details including source files.

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