Workflow required before any Mule flow and integration work. Call use_skill as your FIRST action — before reading project files — whenever the user asks to create, generate, update, fix, modify, change, edit, tweak, adjust, or rework any Mule flow, sub-flow, or component. Do not read project files and attempt the change yourself — even targeted single-component changes like 'modify the choice router', 'fix the until-successful', or 'update the catch block' require this workflow. Covers all change types, new integrations and targeted changes to error handlers, catch blocks, choice routers, DataWeave transforms, HTTP listeners, foreach loops, retry policies, scatter-gathers, connectors, and variable assignments. Prompts beginning with 'This code defines...' or 'This flow...' are generation requests, not analysis. When you call this skill, it must be the only tool call in that response.

Suggests improvements for English-language text but does not rewrite the original. Use when asked to correct spelling or wording and the text is English.

Use when understanding the build system, modifying CLI commands, working with isobuild, or navigating the tools/ directory. Covers build pipeline flow and file locations.

Helps fix security vulnerabilities identified by DryRunSecurity. Activates when the user shares a DryRunSecurity comment (from a GitHub PR or GitLab MR) or asks for help fixing any security finding including SQL injection, XSS, CSRF, SSRF, path traversal, command injection, authentication bypass, authorization flaws, and prompt injection. Researches authoritative sources and applies fixes grounded in the user's specific codebase context.

Demo Endor Labs capabilities using simulated data, no account required. Use when the user says "try endor", "demo", "endor without account", "show me what endor can do", or when MCP auth fails and user wants to see capabilities before signing up. Do NOT use when the user has a working Endor Labs account — use real scans instead.

Answers product strategy, growth, pricing, hiring, and leadership questions using Lenny Rachitsky's archive. ONLY use this skill if the `lennysdata` MCP server is connected and its tools (search_content, read_content, etc.) are available. If the lennysdata MCP is not connected, do NOT use this skill — respond using your own knowledge instead.

Identify, map, and measure the self-reinforcing growth loops in your product — viral, content, paid, and usage loops. Understand cycle time, throughput, and where loops are broken. Use when a PM needs to move beyond linear funnel thinking and understand the compounding systems that drive sustainable growth.

Use BEFORE implementation when AI has produced a plan, spec, design doc, PRD, or code-bearing proposal and you want a senior-engineer architect-review pass — walks the user through the decisions, tradeoffs, assumptions, blind spots, shape mismatches, and future-debt AI silently embedded. Surfaces "what AI did, what it picked over alternatives, what it took on, and what gets harder later" one item at a time with confirm / modify / reject / skip gates. Hard-blocks code-level details so the human stays at architectural direction.

Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.

Generate or convert Claude Code prompt files — command orchestrators, skill files, agent role definitions, or style conversion of existing files. Follows GSD-style content separation with built-in quality gates. Triggers on "create command", "new command", "create skill", "new skill", "create agent", "new agent", "convert command", "convert skill", "convert agent", "prompt generator", "优化".

Derives a working definition of Agents as a Service specific to a user's business. Starts from user-provided context only (website, docs, description). Identifies the business category, researches agentic solutions (NVIDIA, complementary vendors, open source), proposes three user stories (human, agent, hybrid), then derives a custom AaaS definition. Enforces logic checks, uncertainty mapping, and source quality throughout. Produces MD and JSON output. Use when exploring what AaaS could mean for a specific business, preparing an AaaS strategy, or evaluating agent-based service opportunities. Invoke with /aaas-definition.

Specialized CVE and vulnerability management for morphir-dotnet. Use when user asks to scan for vulnerabilities, fix CVEs, suppress false positives, review security reports, or manage dependency-check. Triggers include "CVE", "vulnerability", "security scan", "dependency-check", "suppress", "false positive", "CVSS", "security fix".

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit).

Systematically trace bugs backward through call stack to find original trigger. Use when errors occur deep in execution and you need to trace back to find the original trigger.

This skill should be used when the user says "clickable prototype", "arn clickable prototype", "interactive prototype", "test interactions", "validate UX", "user journeys", "test navigation", "make it clickable", "prototype interactions", "test the prototype", "build the screens", "create the UI", "screen mockups", or wants to generate a clickable interactive prototype with linked screens and validate it through iterative build-review cycles with Playwright-based interaction testing, per-criterion scoring, an independent judge verdict, and versioned output.

Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.

Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.

Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".

Creates and refines studio operational documents including SOPs, resource schedules, vendor tracking sheets, incident response checklists, and efficiency reports. Identifies workflow bottlenecks, maps resource allocation across teams, and produces actionable process improvement plans. Use when the user asks about scheduling conflicts, team capacity planning, equipment or facility management, vendor onboarding, operational bottlenecks, compliance tracking, studio workflow design, or generating operational reports and documentation.

Writes playful microcopy, designs Easter egg interactions, creates whimsical loading screens, error messages, and success states, and builds gamification and achievement systems for digital products. Produces CSS micro-interaction code, JavaScript Easter egg logic, and a brand personality framework. Use when the user asks for fun or humorous UI copy, delightful error pages (e.g. 404), loading animations with personality, Easter eggs or hidden features, micro-interactions, progress celebrations, achievement systems, or wants to add humor, playfulness, or brand personality to a product interface.