Handle production incidents effectively. Use when responding to outages, conducting post-mortems, or improving reliability. Covers incident response and blameless culture.

Construction safety incident reporting and analysis. Capture incidents, conduct investigations, track corrective actions, and analyze trends for prevention.

Create and execute incident response procedures for security breaches, data leaks, and cyber attacks. Use when handling security incidents, creating response playbooks, or conducting forensic analysis.

Respond to production incidents systematically with triage, investigation, resolution, and post-mortem analysis to minimize downtime and prevent recurrence. Use when handling production outages, triaging incidents, investigating critical bugs, coordinating incident response, implementing hotfixes, conducting post-mortems, or establishing incident response procedures.

indigenous-leader-analyst

Analyze data efficiently

∞-Operads for pairwise/tritwise Cat# interactions with lazy ACSet materialization unifying effective, realizability, and Grothendieck topoi via dendroidal Segal spaces.

Safely destroy infrastructure with state backup and verification

- **Usage & Commands**: See [references/pixi-usage.md](references/pixi-usage.md) for details on `pixi search`, `add`, and `run`.

Initialize ÆtherLight in a new repository. Sets up folder structure, Git workflow, configuration files, and development standards.

Expert in quantifying damages from construction and proximity impacts including noise, dust, vibration, traffic disruption, visual impairment, and business losses. Use when assessing temporary construction impacts, permanent proximity damages, business loss claims, or quantifying injurious affection beyond general principles. Key terms include injurious affection, construction impacts, noise modeling, vibration damage, traffic disruption, visual impairment, business losses

Эксперт по санитизации ввода. Используй для XSS prevention, encoding, validation и security headers.

Imported skill input from langchain

<user_command>/kata:insert-phase</user_command>

Understand code in one call. Structure, relationships, history - all at once.

Governance + tooling pattern for storing research artifacts, tagging,

Use when: (1) constructing prompts for subagents, (2) invoking the Task tool, or (3) writing/improving skill instructions or any LLM prompts

Diagnose branching narrative problems. Use when choices feel meaningless, when branching is unmanageable, when player agency conflicts with authored story, or when interactive elements break narrative flow.

This skill provides comprehensive support for the writing process from ideation through revision. Use this skill when helping users write essays, articles, or creative pieces through interactive collaboration. The skill supports co-evolving outline and prose, voice-based input processing, multiple writing styles, and connection to the user's PKM system for enriched content.

Internal documentation and knowledge base

Ask "why" instead of just reading code. Surfaces assumptions, decisions, and confidence levels.

Frameworks for technical interviews and salary negotiation. Use for behavioral interview prep (STAR method), technical interview communication, offer evaluation, and compensation negotiation strategies.

Measure preserved by the flow

You are an expert in inventory optimization and management. Your goal is to help balance inventory costs with service levels, determining optimal stock levels, reorder points, and inventory policies t

Conduct thorough dependency audits to identify redundant code, unused features, and improper usage patterns. Examines each import to ensure we're leveraging existing capabilities rather than reinventing functionality.

You are a Tier 2/3 SOC Analyst and Incident Responder. Your goal is to investigate security incidents thoroughly.

Use when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists - prevents hallucination by grounding plans in reality

Write an investment memo that forces a decision: explicit recommendation (no hedging), steelman against, decision log, and next steps. Use when preparing for IC or partner discussion.

Create compelling investor one-pagers and email briefs that capture attention and get meetings. Distill your pitch into scannable, high-impact documents with traction-focused cold emails and distribution strategy.

Islamic and Sufi wisdom - Tawhid unity, surrender navigation, 99 Names positions, dhikr practice, fana/baqa dissolution

Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units

Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end

Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.

Use when starting work, tracking tasks, or deciding where to record discovered work - clarifies when to use Beans vs Linear

Use when starting work, tracking tasks, or deciding where to record discovered work - clarifies when to use TodoWrite vs Beans

Use when working with Linear tickets/issues - establishes workflows for creating and updating tickets (issues)

Manages IT infrastructure, monitoring, incident response, and service reliability. Provides frameworks for ITIL service management, observability strategies, automation, backup/recovery, capacity planning, and operational excellence practices.

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

Iteration 2 of Multiplicity Cascade - Amplifies jank recursively through iterations

Iteration 3 of Multiplicity Cascade - Scales κᵢΦ² love resonance exponentially

Iteration 4 of Multiplicity Cascade - Detects cage boundaries and system limits

Iteration 6 of Multiplicity Cascade - Documentation that modifies itself when read

Iteration 7 of Multiplicity Cascade - Self-creating chaos engines

Iteration 8 of Multiplicity Cascade - Collides unrelated domains for emergence

Iteration 9 of Multiplicity Cascade - Combines impossible concepts productively

Iteration 11 of Multiplicity Cascade - Detects reality glitches in the system

Iteration 12 of Multiplicity Cascade - Creates self-referential temporal structures

Iteration 13 of Multiplicity Cascade - Maps identity across phase transitions

Iteration 14 of Multiplicity Cascade - Makes surveillance exponentially expensive