@pikku/skills 0.12.14 → 0.12.16

package/skills/pikku-info/SKILL.md

@@ -1,109 +0,0 @@
----
-name: pikku-info
-description: >-
-  Discover what exists in a Pikku project — functions (with their transport, middleware and
-  permissions), tags, middleware and permission definitions. 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
-
-## Agent Operating Procedure
-
-Use this skill as an execution checklist, not reference material.
-
-1. Discover before editing. Run the relevant `pikku meta ... --json` command and inspect only the focused output you need.
-2. Identify the source files that own the behavior. Do not start by reading generated output, `.pikku`, `node_modules`, vendored packages, or broad build artifacts.
-3. Make the smallest source change that satisfies the task. Keep generated files generated, and avoid hand-editing SDKs, schema output, or typegen.
-4. Validate with the narrowest relevant command first, then run `pikku-verify` or `pikku all` when functions, wirings, schemas, or generated clients may have changed.
-5. If validation fails, fix the source cause and rerun validation. Do not paper over generated errors by editing generated files.
-
-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.
-
-There are exactly four subcommands — `functions`, `tags`, `middleware`,
-`permissions`. Routes, channels, schedulers and queues are not separate
-subcommands; they show up as the _transport_ column of `info functions --verbose`.
-
-## Available Commands
-
-`--silent` suppresses the banner and the inspector's diagnostics, which is what
-you want when parsing the table. It is read by the CLI but not declared as an
-option, so every run also prints `Warning: Unknown option: --silent (ignored)` —
-the warning is wrong, the flag works. Ignore that one line.
-
-For anything you intend to parse rather than read, prefer `--json` (alias
-`-j`, or `--output json`), which emits NDJSON instead of a formatted table.
-
-### Functions
-
-List all registered pikku functions:
-
-```bash
-yarn pikku info functions --silent
-```
-
-For full details including transport type (http/channel/scheduler/queue/workflow/mcp/cli/trigger), middleware, permissions, and source file:
-
-```bash
-yarn pikku info functions --verbose --silent
-```
-
-### Tags
-
-List all tags with counts of associated functions and middleware:
-
-```bash
-yarn pikku info tags --silent
-```
-
-For full names instead of counts:
-
-```bash
-yarn pikku info tags --verbose --silent
-```
-
-### Middleware
-
-List all middleware definitions:
-
-```bash
-yarn pikku info middleware --silent
-```
-
-For full details including source file, required services, and description:
-
-```bash
-yarn pikku info middleware --verbose --silent
-```
-
-### Permissions
-
-List all permission definitions:
-
-```bash
-yarn pikku info permissions --silent
-```
-
-For full details including source file, required services, and description:
-
-```bash
-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, and disregard the spurious "Unknown option" warning it prints.
-4. Use `--verbose` when the user asks for details, file paths, or "more info". On `tags` it swaps counts for names; elsewhere it adds columns.
-5. Use `--limit N` to control output size (default is 50 rows) — the footer tells you how many were withheld.
-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)