Automated summary
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 you need to explore an existing Pikku project, find specific functions, or verify the overall configuration.
When writing new Pikku code (use the specific wiring skill) or when asking about Pikku concepts (use pikku-concepts).
Security analysis
SafeThe 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
How this analysis is madeExamples
Show me all the functions registered in this Pikku project, including their transport types and source files.Can you give me a full overview of this Pikku project? List all functions, middleware, permissions, and tags with their counts.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
- 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)
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/pikku-project-discovery-mmh8qq3g/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/pikku-project-discovery-mmh8qq3g' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pikku-project-discovery-mmh8qq3g/download' --output '.skill-downloads/pikku-project-discovery-mmh8qq3g/SKILL.md.part' && mv '.skill-downloads/pikku-project-discovery-mmh8qq3g/SKILL.md.part' '.skill-downloads/pikku-project-discovery-mmh8qq3g/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/pikku-project-discovery-mmh8qq3g/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.