pikkujs/pikku-pino
.claude/skills/pikku-pino/SKILL.md
Use when setting up structured logging with Pino in a Pikku app. Covers PinoLogger setup and log levels. TRIGGER when: code uses PinoLogger, user asks about structured logging, Pino, or @pikku/pino. DO NOT TRIGGER when: user asks about ConsoleLogger (use pikku-services) or general service setup.
$ install --global
skillsauthnpx skillsauth add pikkujs/pikku pikku-pinoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 9:50 PM9.2s1 file scanned
SKILL.md
- name:
- pikku-pino
- description:
- Use when setting up structured logging with Pino in a Pikku app. Covers PinoLogger setup and log levels.
- TRIGGER when:
- code uses PinoLogger, user asks about structured logging, Pino, or @pikku/pino.
- DO NOT TRIGGER when:
- user asks about ConsoleLogger (use pikku-services) or general service setup.
Pikku Pino (Structured Logging)
@pikku/pino provides structured JSON logging via Pino. Implements the Logger interface from @pikku/core.
Installation
yarn add @pikku/pino
API Reference
PinoLogger
import { PinoLogger } from '@pikku/pino'
const logger = new PinoLogger()
No constructor parameters. Creates a Pino logger instance.
Properties:
pino: pino.Logger— Access the underlying Pino instance for advanced config.
Methods:
setLevel(level: LogLevel): void— Set minimum log level.info(messageOrObj: string | Record<string, any> | Error): voidwarn(messageOrObj: string | Record<string, any> | Error): voiderror(messageOrObj: string | Record<string, any> | Error): voiddebug(messageOrObj: string | Record<string, any>): void
Usage Patterns
Basic Setup
import { PinoLogger } from '@pikku/pino'
const logger = new PinoLogger()
logger.setLevel('debug')
With Pikku Services
const createSingletonServices = pikkuServices(async (config) => {
const logger = new PinoLogger()
return { config, logger }
})
Accessing Underlying Pino
const logger = new PinoLogger()
logger.pino.child({ module: 'auth' }).info('Token verified')
Related Skills
pikkujs/pikku-tag-middleware
documentation
VerifiedTrustedCommunity
Deprecated — use pikku-middleware instead. Tag middleware (addTagMiddleware) is now documented as a section within the pikku-middleware skill, alongside global HTTP middleware, execution order, and the service-to-service bearer auth pattern.
56SKILL.mdUpdated Jun 10, 2026
pikkujs/pikku-permissions
testing
VerifiedTrustedCommunity
Use when adding authorization checks to Pikku functions or routes — pikkuPermission, pikkuAuth, per-function permissions, pattern-based permissions, or understanding OR/AND permission logic. TRIGGER when: user wants to restrict who can call a function, check resource ownership, add role-based access, or understand where permission checks belong. DO NOT TRIGGER when: user asks about middleware or request interception (use pikku-middleware), authentication strategies (use pikku-security), or session management.
56SKILL.mdUpdated Jun 10, 2026
pikkujs/pikku-middleware
testing
VerifiedTrustedCommunity
Use when adding any middleware to a Pikku app — global HTTP middleware, tag-scoped middleware (including service-to-service bearer auth), per-route middleware, session-setting middleware, or understanding middleware execution order and priority. TRIGGER when: user wants middleware on some or all routes, machine-to-machine auth, tag-scoped cross-cutting concerns, global interceptors, or middleware priority/order questions. DO NOT TRIGGER when: user asks about permissions/authorization checks (use pikku-permissions), auth strategies like authBearer/authCookie (use pikku-security), or deployment.
56SKILL.mdUpdated Jun 10, 2026
pikkujs/pikku-template-clone
documentation
VerifiedTrustedCommunity
Standard cleanup to run right after a Pikku template is cloned or scaffolded into a new project. TRIGGER when: a Pikku template was just cloned/scaffolded (via `pikku create`, `git clone <template>`, or the user says "I cloned the kanban template / starter / template"), or the working tree still looks like an untouched template (template README, placeholder `@project/*` name in package.json). DO NOT TRIGGER when: working in an established project mid-feature, or editing the template repo itself.
56SKILL.mdUpdated Jun 4, 2026