# PrePilot Agency Suite
> PrePilot is an AI workflow layer for marketing agencies, freelancers, and marketing teams. It gives Claude and ChatGPT structured workflows for paid media, SEO, content, ad copy, UGC scripts, proposals, reports, landing pages, decks, and Arabic/English marketing work.
> This file is the full machine-readable documentation export for PrePilot. Use it to understand what PrePilot is, how to connect it, how to route tasks, how credits work, and how agents should execute workflows safely.

## Canonical Product Facts
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core

- Public marketing message: 526 agency workflows
- Internal database catalog: 583 skill records (includes internal, experimental, or system skills)
- Local workspace skills: 23 engineering and design skills
- MCP runtime tools: 16 tools
- Prompt assets: 529 prompts
- Automated tests: 4,940+

## What PrePilot Is
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core
PrePilot is a structured AI operating layer for agency work. It turns broad marketing requests into routed workflows, skill-specific instructions, staged execution, validation gates, and final deliverables that can be produced consistently across Claude, ChatGPT, and MCP-enabled environments.

## Who Uses PrePilot
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core
PrePilot is built for marketing agencies, solo consultants, freelancers, performance marketers, content teams, SEO teams, account managers, and founders who need repeatable, high-quality marketing execution without rebuilding prompts and process logic for every task.

## What PrePilot Produces
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core
PrePilot produces practical agency deliverables such as campaign plans, ad copy, UGC scripts, SEO briefs, content calendars, proposals, reports, landing page drafts, pitch decks, strategy documents, creative briefs, Arabic and English marketing assets, and workflow outputs shaped by each task's selected skill.

## Decision Router
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core

If the user wants a paid media plan: Use `paid-media-plan-architect`
If the user wants ad variations: Use `ad-copy`
If the user wants UGC scripts: Use `ugc-script` or related UGC skill
If the user wants SEO briefs: Use `seo-aeo-geo-superhero` or `seo-content-brief`
If the user asks how to connect PrePilot: Use MCP setup or ChatGPT setup based on client
If the user asks about balance: Use credits section and `check_my_credits`

## How PrePilot Works
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core
PrePilot routes each request to the most relevant agency skill, loads the required workflow pack, executes the task in ordered stages, checks required inputs and quality gates, and returns a finished deliverable rather than a generic response. Credits and runtime tools support controlled access, task execution, and account-level usage tracking.

## Connection Paths
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core
PrePilot can be connected through MCP-compatible clients or through ChatGPT-oriented setup paths. Agents should choose the connection instructions that match the user's client, environment, and authentication needs, then guide the user through the appropriate setup and validation steps.

## Runtime Execution Loop
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core

PrePilot execution follows a staged runtime loop. First, `sequentialthinking` clarifies the task, assumptions, constraints, and expected output. Next, `intent_route` identifies the best workflow or skill for the user's request. Then `start_agency_task` opens the routed task context, and `get_skill_pack` loads the selected skill's workflow instructions, prompts, schemas, and routing rules. During execution, `get_section` retrieves the needed stage or instruction block, `validate_stage_gate` checks whether the current stage meets the required quality and completeness criteria, and `finalize_deliverable` packages the completed output for the user.



## Credits
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core

## Auth
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core

## Errors
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core

## Troubleshooting
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core

## Skill Catalog Summary
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core

PrePilot contains 583 database-driven skills and 23 local workspace skills. The top-priority skills include real examples, while the remaining skills provide precise I/O schemas for programatic routing.


## Full Skill Catalog
### Part B: Local Workspace Skills Catalog
### 1. python-mcp-server-generator
- **purpose**: Automates the generation of a complete, production-ready Python-based Model Context Protocol (MCP) server project configured with standard directory layout, `uv` packaging, stdio/HTTP transport, custom tools/resources, and robust error handling.
- **inputs**: Project name, list of tools and resources to expose, transport method (`stdio` or `streamable-http`), package dependencies, and Python version constraints.
- **outputs**: A complete file tree representing a Python MCP server project including `server.py` containing tools and resources definitions, `pyproject.toml` (or `uv` configuration), `.gitignore`, and execution/setup scripts.
- **best used when**: Starting a new Python-based MCP server or wrapping local CLI scripts/APIs for LLM usage with minimal boilerplate setup.
- **avoid when**: Creating TypeScript/Node.js MCP servers or simple non-agentic Python projects that do not require Model Context Protocol interfaces.
- **example prompt**: "Create a new Python MCP server named 'weather-mcp' with stdio transport using `uv`. Include a tool named `get_temperature` that takes a string city and returns the weather forecast, with proper type hints and exception handling."
- **expected result**: A fully-structured Python directory containing a structured `server.py` (with `@mcp_server.tool` decorators, correct type hints, docstrings, and robust try-except error handling) and a corresponding `pyproject.toml` pre-configured with the `"mcp[cli]"` dependency.

### 2. chatkit-widgets
- **purpose**: Guides the design, implementation, styling, and server-side integration of interactive, rich ChatKit widgets (based on the OpenAI Apps SDK) inside ChatGPT conversations using the `chatkit` Python SDK.
- **inputs**: UI specifications, layout constraints, interactive elements (buttons, forms, date pickers), target functions in `prepilot_agency_suite/app/mcp/widgets.py`, and widget builder state from `https://widgets.chatkit.studio`.
- **outputs**: Valid, structured JSON representation of the `WidgetRoot` and nested `WidgetNode` hierarchy or Python backend code serving the widget with custom callbacks (`onClickAction`/`onSubmitAction`).
- **best used when**: Designing or modifying interactive components, form elements, card views, lists, and actionable UIs rendered directly in the ChatGPT client interface.
- **avoid when**: Creating standard CLI tools or purely text-based agent responses that do not render rich-media UI widgets.
- **example prompt**: "Design a ChatKit widget for a project planner showing a `ListView` of milestones. Each `ListViewItem` should have a title, progress badge, and a button to mark it complete, utilizing `prepilot_agency_suite/app/mcp/widgets.py`."
- **expected result**: Clean, compliant Python code utilizing `chatkit` SDK classes (e.g., `WidgetRoot`, `Card`, `ListView`, `ListViewItem`, `Badge`, `Button`) properly registered in the widgets system, along with accurate `onClickAction` payloads.

### 3. openapi-to-mcp
- **purpose**: Transforms an OpenAPI (3.x) or Swagger (2.0) specification file into a fully functional, self-hosted Model Context Protocol (MCP) server written in TypeScript using the `mcp-use` SDK.
- **inputs**: OpenAPI specification (YAML/JSON), API endpoint URLs, authentication types (API keys, Basic, Bearer, OAuth), and specific operation filters.
- **outputs**: Scaffolding for `create-mcp-use-app`, including tool definitions mapped to endpoint operations, Zod input validation schemas, client fetch bindings, configuration files, and deployment scripts.
- **best used when**: Exposing an existing RESTful API to LLM agents as standard, discoverable MCP tools with minimal custom coding.
- **avoid when**: Creating standalone servers with no existing REST API backends, or when the target server is written in Python (use `python-mcp-server-generator` instead).
- **example prompt**: "I have an `openapi.yaml` spec for my user database. Generate an MCP server in TypeScript using the `mcp-use` SDK that wraps the GET `/users` and POST `/users` endpoints, including Bearer token auth."
- **expected result**: A TypeScript MCP server project featuring automatically generated tools, complete Zod schemas verifying path/query parameters, custom API client handlers with Bearer headers, and a deployment-ready configuration.

### 4. mcp-apps-builder
- **purpose**: Establishes a mandatory navigational framework, pre-flight safety checks, and strict architectural standards for constructing or extending MCP servers with `mcp-use`.
- **inputs**: Current MCP server files, tools, schemas, resources, and UI widgets to review or upgrade.
- **outputs**: Architectural audits, safety evaluations, optimized tool signatures, and robust registration of prompts and widgets.
- **best used when**: Developing, editing, or auditing any aspect of an MCP server utilizing the `mcp-use` framework.
- **avoid when**: Building simple standalone scripts or non-MCP applications.
- **example prompt**: "Audit our current PrePilot MCP server tools in `server.py` to ensure proper resource caching, description tags, and compliant Zod schemas."
- **expected result**: A comprehensive `<evaluation>` audit block followed by refined tool registrations featuring descriptive metadata, clean response mapping, and structured widget payloads.

### 5. impeccable
- **purpose**: Facilitates professional, agency-level frontend design, auditing, iteration, and visual polish across all visual elements (websites, landing pages, dashboards, and app components).
- **inputs**: Existing HTML/CSS/JS code, visual layouts, design guidelines, `PRODUCT.md`/`DESIGN.md` specification files, and specific UI commands (`craft`, `shape`, `audit`, `polish`).
- **outputs**: Exceptional, responsive styling definitions, refined typography, and high-performance interactive visual updates.
- **best used when**: Building premium user interfaces, redesigning flat/boring layouts, auditing visual hierarchy, or optimizing micro-interactions and motion design.
- **avoid when**: Developing backend APIs, databases, data engineering scripts, or terminal-based applications with no graphical layout.
- **example prompt**: "Audit our dashboard layout and craft a premium dark mode redesign with improved typography and refined card borders to elevate the user experience."
- **expected result**: A detailed UI audit listing specific visual enhancements followed by fully-written, production-ready, beautiful CSS rules and HTML components conforming to modern high-end UX design standards.

### 6. full-output-enforcement
- **purpose**: Strictly guarantees the delivery of exhaustive, fully-written, production-critical code blocks and text without placeholders or summaries.
- **inputs**: Code snippets, templates, or files that need to be fully generated, expanded, or refactored.
- **outputs**: Completed, unabridged, non-truncated file contents and comprehensive documentation ready for immediate compilation or execution.
- **best used when**: Delivering final code reviews, critical scripts, API controllers, and large configurations where omission of details results in broken systems.
- **avoid when**: The user explicitly asks for quick conceptual pseudocode, or during short conversational exploration where brevity is prioritized.
- **example prompt**: "Write the complete database model file for our application containing all user, transaction, and log tables, ensuring zero placeholders or shortened lines."
- **expected result**: An entirely written, long-form, flawless code file with every model, relationship, validator, and helper completely implemented and fully documented.

### 7. design-taste-frontend-v1
- **purpose**: Recreates the classic, highly structured v1 design engine that implements responsive layouts and high-variance visual styling using a preset dial configuration.
- **inputs**: Design spec, target webpage components, layout constraints, and visual theme requirements.
- **outputs**: Production-ready CSS and markup conforming to classical bento grids and custom color schemas.
- **best used when**: Working on legacy PrePilot projects that rely specifically on the v1 parameters (`DESIGN_VARIANCE: 8`, `MOTION_INTENSITY: 6`, `VISUAL_DENSITY: 4`) for visual style parity.
- **avoid when**: Building modern projects where the upgraded, more context-aware `design-taste-frontend` (v2) is available and recommended.
- **example prompt**: "Redesign our pricing cards to match the legacy v1 frontend visual density and motion configurations."
- **expected result**: Elegant CSS rules and matching markup containing classical border animations, structured cards, and precise grid spacing.

### 8. imagegen-frontend-mobile
- **purpose**: Guides the generation of premium, highly-polished mobile app user interface concepts and mockups wrapped in realistic phone frames.
- **inputs**: Screen specifications, target industry (Fintech, Health, Social), app flow, and selected color palette.
- **outputs**: High-end conceptual images showing detailed app screens inside subtle, elegant device mockups.
- **best used when**: Ideating, presenting, or clarifying the visual direction of a mobile application before writing code.
- **avoid when**: Developing websites, desktop layouts, backend configurations, or when actual code implementation is needed.
- **example prompt**: "Generate a high-fidelity onboarding screen concept for a premium personal finance app, featuring a sleek dark theme, minimalist card design, and textured background, presented inside a clean iPhone frame."
- **expected result**: A stunning, high-agency design image showcasing precise UI components, modern typography, readable data values, and gorgeous color balance.

### 9. affiliate-marketing
- **purpose**: Strategizes, structures, and launches professional affiliate and partner referral programs, defining commission brackets, tracking metrics, and growth pipelines.
- **inputs**: Business model (SaaS, E-commerce, Info), average customer lifetime value (LTV), target commission structure, and promotional assets.
- **outputs**: Operational strategy docs, programmatic commission rules, tracking setup requirements, and partner onboarding structures.
- **best used when**: Introducing a new referral/affiliate program to a SaaS product, designing merchant portals, or establishing commission payouts.
- **avoid when**: Developing purely technical integrations that do not involve partner commission models or marketing growth strategies.
- **example prompt**: "Create a complete affiliate program plan for a subscription SaaS charging $49/month, including commission percentages, tracking setup recommendations, and promo templates."
- **expected result**: A highly detailed markdown report mapping out profitable commission tiers, recommended tracking software configurations, cookie retention periods, and structured affiliate email sequences.

### 10. stitch-design-taste
- **purpose**: Bridges the gap between advanced design-system rules and Google Stitch by generating robust, highly descriptive `DESIGN.md` documents that guide Stitch's screen-generation engine.
- **inputs**: Visual design requirements, product theme parameters, desired typography, and component specs.
- **outputs**: A structured, semantic `DESIGN.md` file optimized for RAG and agent parsing under Google Stitch.
- **best used when**: Preparing a project for screen generation, UI layouts, or page scaffolding using the Google Stitch web tool.
- **avoid when**: Implementing normal React/Vue codebases directly without using Google Stitch.
- **example prompt**: "Generate a `DESIGN.md` for our new real-estate marketplace to be used in Google Stitch, detailing modern brutalist typography, asymmetric layouts, and deep shadow rules."
- **expected result**: A professionally structured `DESIGN.md` containing detailed natural-language definitions, color token HSL bounds, strict typographic hierarchies, and interactive behavior rules.

### 11. industrial-brutalist-ui
- **purpose**: Designs, styles, and builds raw, highly functional web interfaces inspired by mid-century Swiss typography and aerospace telemetry systems.
- **inputs**: Screen copy, data metrics, target system layout, and visual asset guidelines.
- **outputs**: High-contrast, modular CSS rules, bitmap dithered halftones, monospace layouts, and raw terminal grid templates.
- **best used when**: Designing complex dashboards, developer tools, creative portfolios, and data-heavy telemetry interfaces requiring a distinct, non-generic look.
- **avoid when**: Designing typical consumer apps, soft pastel landing pages, or when the target audience prefers standard friendly SaaS layouts.
- **example prompt**: "Build a system monitoring dashboard layout in raw industrial brutalist style, utilizing heavy monospace typography, thick borders, and green-on-black color schemas."
- **expected result**: Distinctive HTML and CSS featuring rigid grid lines (`border: 2px solid`), strict layout geometry, monospace numeric data tables, and high-impact micro-animations.

### 12. supabase-postgres-best-practices
- **purpose**: Formulates highly optimized, secure, and production-grade Postgres database schemas and SQL queries tailored for Supabase environments.
- **inputs**: Schema specifications, SQL queries, EXPLAIN query plans, transaction structures, Row-Level Security (RLS) rules, and index strategies.
- **outputs**: Highly performant SQL queries, secure RLS policies, optimal index definitions, and schema refactoring plans.
- **best used when**: Developing database models, troubleshooting slow database transactions, writing complex triggers, or configuring secure row-level client access.
- **avoid when**: Working with non-relational databases (NoSQL), SQLite, or databases unrelated to PostgreSQL.
- **example prompt**: "Optimize this query selecting users and their latest purchases, and write a secure RLS policy preventing read access for unauthenticated requests."
- **expected result**: Clean, standard-compliant SQL with optimized join operations, proper indexing recommendations, and safe Row-Level Security declarations.

### 13. supabase
- **purpose**: Serves as the central coordination layer for implementing, debugging, and maintaining entire application lifecycles inside the Supabase ecosystem.
- **inputs**: Supabase configurations, environment keys, schema definitions, Edge Functions, integration routes, and client-side framework code.
- **outputs**: Structured Supabase migration files, CLI deployment steps, JWT/Cookie authentication pipelines, and robust database storage and serverless scripts.
- **best used when**: Setting up database connections, implementing user authentication, deploying serverless Edge Functions, or writing client queries via `supabase-js`.
- **avoid when**: Developing apps with separate hosting, authentication providers, and cloud databases (e.g. Firebase, custom Node.js/Mongo backends).
- **example prompt**: "Implement a complete login and sign-up flow using `@supabase/ssr` in a Next.js App Router project, including cookie session middleware and secure user redirection."
- **expected result**: Production-ready TypeScript implementation containing Next.js route handlers, secure session validation, middleware cookie processing, and descriptive error recovery steps.

### 14. brandkit
- **purpose**: Facilitates the generation of premium, high-end brand identity packages, logo boards, style grids, and aesthetic presentations for startups and premium products.
- **inputs**: Brand core values, selected theme, color preferences, stylistic DNA guidelines (e.g. minimalist dark tech, cultural, luxury), and layout format.
- **outputs**: Gorgeous, high-fidelity brand presentation boards featuring clean grid alignments, logo concepts, typography charts, and product mockups.
- **best used when**: Ideating, presenting, and establishing corporate identities, logomarks, or color palettes for new startup projects.
- **avoid when**: Generating website code, coding databases, setting up server connections, or when functional code assets are needed.
- **example prompt**: "Generate a premium brand guideline board for a developer tool named 'LogiKit', utilizing a dark tech style with a minimalist vector logo concept, off-white typography, and clear grid structure."
- **expected result**: A stunning, high-agency presentation layout featuring a logo mark, color chips, typographical hierarchy rules, and subtle brand-aligned product mockups.

### 15. chatgpt-app-builder
- **purpose**: Orchestrates the development and deployment of ChatGPT companion apps containing embedded React widgets powered by `mcp-use` and the OpenAI Apps SDK.
- **inputs**: React widget specifications, state parameters, API hooks, payload definitions, and integration requirements.
- **outputs**: Fully verified React widget trees, server integration code (via widgets.py or widgets.ts), and ChatGPT app configuration manifests.
- **best used when**: Creating specialized applications inside ChatGPT that require custom widgets, interactive forms, and direct API actions.
- **avoid when**: Developing standard backend-only APIs, CLI tools, or web systems that do not run inside ChatGPT's app platform.
- **example prompt**: "Build a ChatGPT task app with a customized React form widget that collects a task title, due date, and priority level, and submits it to our MCP backend."
- **expected result**: Compliant React code wrapping the form inside `<McpUseProvider>` with appropriate state handlers, pending transaction loaders, and standard error fallback boundaries.

### 16. design-taste-frontend
- **purpose**: Implements clean, anti-slop, non-templated frontend views (landing pages, personal portfolios, visual marketing pages) tailored closely to the specific industry vibe.
- **inputs**: Project brief, design aesthetic keywords (Satoshi, Editorial, Tech, Neo-brutalist), branding colors, and specific page blocks.
- **outputs**: Custom, highly curated HTML and CSS (or framework code) using tailored typography, creative asymmetry, micro-animations, and balanced color systems.
- **best used when**: Launching startup landing pages, product releases, visual portfolios, and websites that need to feel expensive and unique.
- **avoid when**: Building administrative portals, heavy data-table dashboards, multi-step transaction forms, or complex backend applications.
- **example prompt**: "Create a premium portfolio site for a creative developer using a warm editorial theme, serif headers, custom page-reveal animations, and an off-grid layout."
- **expected result**: Flawless, non-templated HTML and CSS utilizing hand-picked Google Fonts (e.g. Outfit, Satoshi), responsive flexbox layouts, organic gradients, and elegant scroll effects.

### 17. gpt-taste
- **purpose**: Guides the implementation of award-winning, fluid, motion-rich frontend websites using GSAP ScrollTriggers, strict AIDA structure, and unique asymmetric layout flows.
- **inputs**: Brand identity, visual assets, scroll animation goals, interactive layers, and component structures.
- **outputs**: Production-grade GSAP animation setups, complex scroll timeline handlers, responsive grid structures, and premium typography styling.
- **best used when**: Creating immersive marketing pages, product experiences, and high-impact digital portfolios that need to win design awards (like Awwwards).
- **avoid when**: Developing simple, lightweight text-only documentation, static dashboards, or when fast loading speed with minimal Javascript is the absolute priority.
- **example prompt**: "Write a GSAP ScrollTrigger script that pins the hero section and sequentially stacks three content cards as the user scrolls, with custom opacity fades and smooth scrubbing."
- **expected result**: Flawless, hardware-accelerated JavaScript and CSS implementing GSAP timelines, precise ScrollTrigger properties, custom pinning points, and beautiful, fluid motion choreographies.

### 18. high-end-visual-design
- **purpose**: Implements high-end, premium web layouts characterized by subtle depth, micro-interactions, custom lighting, organic borders, and luxurious visual pacing.
- **inputs**: Site structure, corporate identity, brand values, content sections, and interaction guidelines.
- **outputs**: High-agency HTML and CSS defining custom drop-shadow levels, elegant card nesting, premium glassmorphism parameters, and clean layouts.
- **best used when**: Crafting software-as-a-service (SaaS) homepages, developer tools landing pages, and consumer brand presentations aiming for premium quality.
- **avoid when**: Developing classic brutalist sites, low-end proof-of-concept projects, or simple text blogs where design aesthetics are secondary.
- **example prompt**: "Design a premium Apple-esque features section showcasing our analytics engine with soft glassmorphic cards, glowing borders, and subtle dark shadows."
- **expected result**: Clean, expensive-looking CSS rules utilizing calibrated box-shadow values, custom glass filters (`backdrop-filter: blur`), subtle border glows, and wide grid gutters.

### 19. image-to-code
- **purpose**: Standardizes a robust "design-then-implement" workflow where premium conceptual images are generated and systematically parsed before writing frontend code.
- **inputs**: Layout brief, generated design references, typography guidelines, and target frontend framework.
- **outputs**: High-fidelity frontend source code (HTML/CSS, React, or Vue) that replicates the design reference's spacing, colors, and layout exactly.
- **best used when**: Translating complex visual layouts, custom components, and highly stylized concepts into pixel-perfect, responsive code.
- **avoid when**: Implementing backend systems, database logic, API routes, or standard text-based content without visual mockups.
- **example prompt**: "Analyze the provided reference design image of our pricing section and implement it fully using responsive vanilla CSS and HTML, preserving the exact spacing and subtle shadow styling."
- **expected result**: Flawless, clean, structured CSS and HTML that mimics the input reference image perfectly, featuring semantic layouts, readable typography sizes, and clean media queries.

### 20. imagegen-frontend-web
- **purpose**: Guides the creation of gorgeous, high-end website layout mockups section-by-section as separate horizontal design files to prevent visual compression and guarantee absolute quality.
- **inputs**: Component brief, section list, design aesthetics (Minimalist, Brutalist, Tech), and target layout patterns.
- **outputs**: A series of separate, beautiful horizontal design images, one for each section, displaying premium layout reference patterns.
- **best used when**: Developing conversion-aware SaaS landing pages, marketing sites, and corporate interfaces requiring high-end art-direction.
- **avoid when**: Designing mobile native app screens (use `imagegen-frontend-mobile`), database schemas, or when direct code generation is requested first.
- **example prompt**: "Generate a design reference for our security startup landing page containing three sections: a sleek Hero, a features grid, and a dark CTA trust block, outputting one horizontal image per section."
- **expected result**: Three highly structured, high-resolution horizontal design files featuring consistent colors, clean spacing, and modern typographic visual rhythm.

### 21. mcp-builder
- **purpose**: Guides the rapid creation, configuration, and packaging of secure Model Context Protocol (MCP) servers utilizing the TypeScript-based `mcp-use` framework.
- **inputs**: Service definition, tool descriptions, input/output structures, authentication types, and target host endpoints.
- **outputs**: Ready-to-deploy TypeScript MCP project containing verified tools, resources, and custom prompts registered on the `mcp-use` stack.
- **best used when**: Setting up new MCP integrations, building custom developer tools, or connecting databases and services directly to Claude or ChatGPT clients.
- **avoid when**: Developing standard web servers, REST APIs, or Python-based systems that do not implement the Model Context Protocol.
- **example prompt**: "Create a TypeScript MCP server with a tool that queries our database and returns a formatted markdown summary, including full input schemas and description tags."
- **expected result**: A fully-configured TypeScript directory including `index.ts` declaring tools with thorough descriptions, zod schemas, appropriate response types, and package.json configuration files.

### 22. minimalist-ui
- **purpose**: Formulates clean, editorial-style, document-inspired user interfaces featuring heavy typography, flat layouts, macro-whitespace, and warm monochrome palettes.
- **inputs**: Page content, structured text blocks, data elements, and primary navigation items.
- **outputs**: Stunningly simple, premium, ultra-flat HTML and CSS (avoiding shadows, gradients, and rounded edges) that prioritize reading focus and crisp layout boundaries.
- **best used when**: Creating technical wikis, document portals, minimalist blog feeds, agency websites, and clean product dashboards.
- **avoid when**: Designing high-energy consumer products, heavy three-dimensional visual games, or when the user demands vibrant color gradients and heavy drop-shadows.
- **example prompt**: "Design an editorial dashboard for a writer showing active manuscripts, word counts, and daily goals in a flat bento grid, utilizing a warm monochrome color scheme and Cabinet Grotesk headers."
- **expected result**: Exceptionally clean markup and styling rules featuring off-white backgrounds, dark grey text boundaries, thin black grid lines, bold headers, and extensive, comfortable spacing.

### 23. redesign-existing-projects
- **purpose**: Audits, modernizes, and upgrades existing codebases to high-agency aesthetic standards, replacing generic UI defaults while preserving application functionality.
- **inputs**: Existing HTML/CSS files, framework configs (e.g. Tailwind, Bootstrap), page paths, and target visual mood.
- **outputs**: Targeted refactoring suggestions, refined stylesheet rules, optimized typographic settings, and clean visual upgrades.
- **best used when**: Migrating basic or outdated templates, generic AI-generated templates, or simple MVPs into elegant, custom interfaces.
- **avoid when**: Creating entirely new applications from scratch (use `design-taste-frontend` or `impeccable` instead).
- **example prompt**: "Audit our current landing page in `/index.html` and rewrite its CSS to replace the generic browser fonts with Satoshi, add smooth hover borders, and optimize layout spacing."
- **expected result**: A detailed design diagnostics report followed by complete, drop-in replacement stylesheet code containing customized interactive states, balanced spacing, and elevated typography.

### Part C: Database Catalog Skills
### Chunk 1 Skills Index

#### 1. 00_governance
- **purpose**: Governance — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `context` (string, required): Current system state or request
- `action_type` (string, required): Type of governance action required
- `risk_level` (string, optional): Assessed risk level: low|medium|high|critical
- **outputs**:
- `governance_decision` (object): Structured governance_decision payload
- `audit_entry` (object): Structured audit_entry payload
- `escalation` (boolean): Structured escalation payload
- **best used when**: When requiring strategic Governance support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Governance or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 2. 01_orchestration
- **purpose**: Orchestration — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `user_request` (string, required): The user's original request
- `available_agents` (array, optional): List of available agents to route to
- `context` (object, optional): Session context and history
- **outputs**:
- `routing_decision` (object): Structured routing_decision payload
- `agent_assignment` (string): Structured agent_assignment payload
- `execution_plan` (array): Structured execution_plan payload
- **best used when**: When requiring strategic Orchestration support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Orchestration or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 3. 02_agents
- **purpose**: Agents — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `agent_task` (string, required): Task to assign to agent
- `agent_type` (string, required): Type of agent to use
- `constraints` (array, optional): Operational constraints
- **outputs**:
- `agent_output` (object): Structured agent_output payload
- `status` (string): Structured status payload
- `artifacts` (array): Structured artifacts payload
- **best used when**: When requiring strategic Agents support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Agents or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 4. 03_creative_content_system
- **purpose**: Creative Content System — Professional-grade content skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete creative content system document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Creative Content System support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Creative Content System or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 5. 03_egyptian_dialect_writer
- **purpose**: Egyptian Dialect Writer — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete egyptian dialect writer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Egyptian Dialect Writer support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Egyptian Dialect Writer or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 6. 03_product
- **purpose**: Product — Professional-grade product skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 7. 04_research
- **purpose**: Research — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete research document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Research support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Research or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 8. 05_architecture
- **purpose**: Architecture — Professional-grade tech skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete architecture document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Architecture support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Architecture or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 9. 06_security
- **purpose**: Security — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete security document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Security support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Security or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 10. 07_tracking
- **purpose**: Tracking — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tracking document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Tracking support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Tracking or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 11. 08_ux
- **purpose**: Ux — Professional-grade product skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ux document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Ux support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ux or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 12. 09_agentic_parallelism_system
- **purpose**: Agentic Parallelism System — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete agentic parallelism system document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Agentic Parallelism System support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Agentic Parallelism System or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 13. 09_tooling
- **purpose**: Tooling — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tooling document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Tooling support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Tooling or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 14. 10_legacy
- **purpose**: Legacy — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete legacy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Legacy support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Legacy or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 15. 11_marketing_growth_agent
- **purpose**: Marketing Growth Agent — Professional-grade marketing skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete marketing growth agent document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Marketing Growth Agent support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Marketing Growth Agent or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 16. 12_saudi_strategic_system
- **purpose**: Saudi Strategic System — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete saudi strategic system document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Saudi Strategic System support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Saudi Strategic System or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 17. Marketing Agency
- **purpose**: Marketing Agency — Professional-grade marketing skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete marketing agency document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Marketing Agency support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Marketing Agency or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 18. Vibe-coding
- **purpose**: Vibe Coding — Professional-grade general skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete vibe coding document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Vibe Coding support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Vibe Coding or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 19. __pycache__
- **purpose**: Pycache   — Professional-grade general skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete   pycache   document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic   Pycache   support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to   Pycache   or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 20. ab-test-plan
- **purpose**: Designs A/B test plans with hypothesis, variants, sample size calculations, success metrics, and statistical significance criteria. Use when optimizing conversions or UX.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ab test plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Ab Test Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ab Test Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 21. abandoned-cart-email
- **purpose**: Writes abandoned cart email sequences with timing, subject lines, incentive escalation, and product image notes. Use when recovering lost sales from customers who left items in their cart.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete abandoned cart email document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 22. about-page
- **purpose**: Writes compelling about pages, founder bios, and team introductions that build trust and convert visitors using storytelling frameworks and social proof. Use when a user needs an about page for their website, wants to write a professional bio, or needs to introduce their team in a way that builds credibility.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete about page document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic About Page support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to About Page or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 23. accessibility-policy
- **purpose**: Writes website accessibility policies with WCAG compliance commitments and accommodation procedures. Use when creating an accessibility statement for your website.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete accessibility policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 24. account-manager
- **purpose**: للمتابعة مع العملاء، كتابة updates، محاضر الاجتماعات، تلخيص القرارات، وتجهيز رسائل واضحة للعميل
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete account manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Account Manager support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Account Manager or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 25. ad-copy
- **purpose**: Writes high-converting ad copy for Facebook, Google, and LinkedIn with multiple creative variations, audience targeting suggestions, and optional ad graphics via Canva. Use when a user needs paid advertising copy, wants to launch ad campaigns, or needs creative variations for A/B testing across ad platforms.
- **inputs**:
- `product_service` (string, required): Product or service name
- `platform` (string, required): Platform: Facebook|Instagram|Google|LinkedIn|TikTok
- `objective` (string, required): Campaign objective: awareness|traffic|leads|sales
- `audience` (string, required): Target audience description
- `usp` (string, required): Unique selling proposition
- `offer` (string, optional): Special offer or promotion
- `tone` (string, optional): Ad tone: urgent|playful|professional|emotional
- **outputs**:
- `ad_variants` (array): 3-5 ad copy variants to test
- `headlines` (array): Multiple headline options
- `hooks` (array): Opening hook variations
- `cta_options` (array): CTA button text options
- **best used when**: When requiring strategic Ad Copy support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ad Copy or when more specialized Advertising tools are available.
- **example prompt**: "Execute PrePilot task for 'Ad Copy' (ID: ad-copy) to generate a premium strategic deliverable with inputs: product_service='Standard product_service brief', platform='Standard platform brief', objective='Standard objective brief', audience='Standard audience brief', usp='Standard usp brief'."
- **expected result**: 
```json
{
  "ad_variants": [
    "Validated ad_variants milestone 1",
    "Validated ad_variants milestone 2"
  ],
  "headlines": [
    "Validated headlines milestone 1",
    "Validated headlines milestone 2"
  ],
  "hooks": [
    "Validated hooks milestone 1",
    "Validated hooks milestone 2"
  ],
  "cta_options": [
    "Validated cta_options milestone 1",
    "Validated cta_options milestone 2"
  ]
}
```

#### 26. ad-creative-brief
- **purpose**: Creates detailed ad creative briefs with visual direction, copy variants, dimensions, and platform specifications. Use when producing ads for any paid media channel.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ad creative brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Ad Creative Brief support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ad Creative Brief or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 27. ad-performance-report
- **purpose**: Creates ad performance reporting templates with ROAS analysis, creative insights, and optimization recommendations. Use when you need structured ad campaign reports.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ad performance report document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Ad Performance Report support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ad Performance Report or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 28. ad-spend-calculator
- **purpose**: Calculates ad spend budgets based on revenue goals, conversion rates, and cost-per-acquisition targets. Use when planning how much to spend on ads to hit revenue targets.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ad spend calculator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Ad Spend Calculator support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ad Spend Calculator or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 29. affiliate-program
- **purpose**: Sets up affiliate and referral program structures with commission tiers, terms and conditions, affiliate onboarding materials, and promotional asset guidelines. Use when a user wants to launch an affiliate program, needs to recruit partners to promote their product, or wants to create a referral incentive system for existing customers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete affiliate program document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Affiliate Program support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Affiliate Program or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 30. affiliate-recruitment
- **purpose**: Writes affiliate recruitment emails, landing pages, and onboarding materials to attract partners. Use when building or growing an affiliate program.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete affiliate recruitment document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Affiliate Recruitment support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Affiliate Recruitment or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 31. affiliate-terms
- **purpose**: Creates affiliate program terms and conditions with commission rules, prohibited methods, and termination clauses. Use when launching or documenting an affiliate program.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete affiliate terms document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 32. agency-onboarding
- **purpose**: Creates a complete client onboarding system for agencies and service providers, including welcome email sequence, intake questionnaire, kickoff meeting checklist, and communication guidelines. Use when a user runs an agency, consultancy, or service business and needs to standardize how new clients are brought on board.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete agency onboarding document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Agency Onboarding support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Agency Onboarding or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 33. ai-content-policy
- **purpose**: Creates AI-generated content policies with disclosure requirements, quality standards, and review processes. Use when standardizing how your business produces AI-assisted content.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ai content policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 34. ai-ethics-policy
- **purpose**: Creates AI usage policies for businesses with transparency commitments, bias mitigation, and disclosure guidelines. Use when establishing responsible AI practices.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ai ethics policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 35. ai-use-case-finder
- **purpose**: Identifies AI automation opportunities in business workflows with feasibility assessment and ROI estimates. Use when evaluating where AI can save time and money in your business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ai use case finder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Ai Use Case Finder support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ai Use Case Finder or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 36. ambassador-program
- **purpose**: Designs brand ambassador programs with tiers, perks, responsibilities, content requirements, and tracking systems. Use when building a community of advocates who promote your brand.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ambassador program document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Ambassador Program support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ambassador Program or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 37. analytics-setup-guide
- **purpose**: Plans web analytics implementation with event tracking, goals, conversion setup, and dashboard configuration. Use when setting up Google Analytics or similar tools from scratch.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete analytics setup guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Analytics Setup Guide support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Analytics Setup Guide or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 38. annual-planning
- **purpose**: Facilitates annual business planning with vision setting, goal cascading, quarterly milestones, and resource allocation for focused execution.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete annual planning document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Annual Planning support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Annual Planning or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 39. annual-report-writer
- **purpose**: Creates annual reports for stakeholders with narrative sections, metric highlights, and forward-looking statements. Use when summarizing yearly performance for investors, partners, or your team.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete annual report writer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Annual Report Writer support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Annual Report Writer or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 40. annual-review
- **purpose**: Compiles annual business reviews with year-over-year metrics, milestone highlights, lessons learned, and strategic goals for the upcoming year. Use when a user needs to reflect on their business year, wants to create a year-in-review document for stakeholders, or is setting annual goals and needs to assess where they stand.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete annual review document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Annual Review support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Annual Review or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 41. anysearch
- **purpose**: API key for higher rate limits. Anonymous access available with lower rate limits.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete anysearch document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Anysearch support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Anysearch or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 42. api-documentation
- **purpose**: Creates API documentation templates with endpoint descriptions, request/response examples, and authentication guides. Use when documenting REST APIs for developers.
- **inputs**:
- `api_name` (string, required): API name
- `base_url` (string, required): Base API URL
- `endpoints` (array, required): List of endpoints with methods and descriptions
- `auth_method` (string, required): Authentication: API-key|OAuth|Bearer|Basic
- `response_format` (string, optional): Response format: JSON|XML
- `programming_language` (string, optional): Example code language
- **outputs**:
- `documentation` (string): Complete API documentation
- `endpoint_table` (array): Endpoints reference table
- `code_examples` (object): Code examples per endpoint
- **best used when**: When requiring strategic Api Documentation support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Api Documentation or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 43. archive-librarian
- **purpose**: Organizes, searches, and retrieves legacy documentation and old scope.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete archive librarian document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Archive Librarian support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Archive Librarian or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 44. article-rewriter
- **purpose**: Rewrites existing articles with fresh angles, updated data, and improved SEO while preserving core message. Use when refreshing outdated content or adapting articles for new audiences.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete article rewriter document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Article Rewriter support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Article Rewriter or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 45. attribution-model
- **purpose**: Designs marketing attribution models with channel mapping, weighting logic, reporting recommendations, and implementation steps. Use when understanding which channels drive conversions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete attribution model document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Attribution Model support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Attribution Model or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 46. author-platform-plan
- **purpose**: Builds author platform plans with book promotion, speaking gigs, media appearances, and audience building.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete author platform plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Author Platform Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Author Platform Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 47. authority-content-strategy
- **purpose**: Plans content strategies for building authority with research pieces, original frameworks, and data studies.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete authority content strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Authority Content Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Authority Content Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 48. automation-workflow
- **purpose**: Designs automation workflows with trigger-action sequences, tool connections, and error handling procedures. Use when automating repetitive business processes.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete automation workflow document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Automation Workflow support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Automation Workflow or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 49. award-application
- **purpose**: Writes business award applications with narrative sections, metric evidence, and supporting documentation checklists. Use when applying for industry or business awards.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete award application document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Award Application support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Award Application or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 50. backend-architect
- **purpose**: Manages backend Node.js/TypeScript code and configurations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete backend architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Backend Architect support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Backend Architect or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 51. batch-processing-system
- **purpose**: Designs batch processing workflows for repetitive tasks like invoicing, content publishing, and reporting to save hours each week.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete batch processing system document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Batch Processing System support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Batch Processing System or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 52. benchmarking-report
- **purpose**: Creates industry benchmarking reports comparing business metrics against standards and best-in-class performers. Use when evaluating where your business stands versus peers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete benchmarking report document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Benchmarking Report support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Benchmarking Report or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 53. benefits-guide
- **purpose**: Writes employee benefits guides explaining health insurance, retirement plans, PTO, and perks in plain language. Use when onboarding new hires or updating benefits documentation.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete benefits guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Benefits Guide support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Benefits Guide or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 54. beta-launch-plan
- **purpose**: Plans beta launches with user recruitment, feedback collection, bug reporting, and iteration cycles. Use when preparing to launch a product or feature in beta.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete beta launch plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Beta Launch Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Beta Launch Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 55. black-friday-emails
- **purpose**: Creates Black Friday/Cyber Monday email sequences with early access, flash deals, last chance, and extended sale phases. Use for holiday sale campaigns.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete black friday emails document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Black Friday Emails support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Black Friday Emails or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 56. blog-post
- **purpose**: Writes SEO-optimized long-form blog posts with outline approval, meta descriptions, internal link suggestions, featured image briefs, and a pre-publish SEO checklist. Use when a user needs a blog article for their website, wants to rank for specific keywords, or needs content marketing pieces that drive organic traffic.
- **inputs**:
- `target_keyword` (string, required): Primary SEO keyword or phrase to rank for
- `topic` (string, required): Blog post topic or title idea
- `audience` (string, optional): Target reader persona
- `word_count` (integer, optional): Target word count (default: 1500-2000)
- `angle` (string, optional): Unique angle or perspective
- `internal_links` (array, optional): URLs of existing posts to link to
- `brand_voice` (string, optional): Brand voice: professional|conversational|bold
- **outputs**:
- `blog_post` (string): Full blog post in markdown
- `meta_description` (string): SEO meta description (155 chars)
- `image_brief` (string): Featured image brief
- `seo_checklist` (array): Pre-publish SEO checklist
- **best used when**: When requiring strategic Blog Post support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Blog Post or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 57. book-outline
- **purpose**: Outlines non-fiction books with chapter structure, key arguments, supporting evidence, and word count targets per chapter. Use when a user wants to write a non-fiction book, needs to organize their expertise into a publishable structure, or is pitching a book proposal to publishers or agents.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete book outline document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Book Outline support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Book Outline or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 58. book-proposal
- **purpose**: Writes non-fiction book proposals with overview, market analysis, competitive titles, chapter outlines, and sample chapters.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete book proposal document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Book Proposal support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Book Proposal or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 59. bookkeeping-setup
- **purpose**: Sets up bookkeeping systems with chart of accounts, transaction categories, and reconciliation procedures. Use when establishing or organizing business bookkeeping.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete bookkeeping setup document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Bookkeeping Setup support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Bookkeeping Setup or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 60. brand-architecture
- **purpose**: Designs brand architecture frameworks (house of brands, branded house, endorsed) with naming conventions, visual relationships, and portfolio management. Use when managing multiple brands.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete brand architecture document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Brand Architecture support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Brand Architecture or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 61. brand-audit
- **purpose**: Conducts brand audits evaluating consistency, perception, competitive positioning, and improvement recommendations across all touchpoints. Use when assessing brand health.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete brand audit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Brand Audit support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Brand Audit or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 62. brand-identity-guide
- **purpose**: Creates comprehensive brand identity guidelines with logo usage, color codes, typography, imagery style, voice, and application examples. Use when documenting your brand standards.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete brand identity guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Brand Identity Guide support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Brand Identity Guide or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 63. brand-photography-brief
- **purpose**: Creates shot lists, mood board descriptions, and creative direction for brand photo shoots. Use this skill when a user needs to prepare for a professional photography session, plan visual content for their brand, or brief a photographer on the look and feel they want.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete brand photography brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Brand Photography Brief support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Brand Photography Brief or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 64. brand-positioning-statement
- **purpose**: Crafts brand positioning statements with target audience, category, point of difference, reason to believe, and competitive context. Use when defining how your brand stands apart.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete brand positioning statement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Brand Positioning Statement support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Brand Positioning Statement or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 65. brand-refresh
- **purpose**: Batch updates text and imagery across existing Canva designs when brand elements change, searching for affected designs and applying find-and-replace operations across all confirmed files. Use when a user has updated their brand colors, fonts, tagline, logo, or contact info and needs to propagate those changes across multiple existing Canva designs.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete brand refresh document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Brand Refresh support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Brand Refresh or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 66. brand-review
- **purpose**: Audit a brand's consistency, messaging, visual identity, tone of voice, and competitive
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete brand review document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Brand Review support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Brand Review or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 67. brand-story
- **purpose**: Crafts compelling origin stories and brand narratives using the hero's journey framework. Use when a user needs an about page story, launch narrative, pitch deck backstory, or wants to articulate why their business exists in a way that emotionally connects with customers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete brand story document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Brand Story support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Brand Story or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 68. brand-tagline
- **purpose**: Generates brand taglines and slogans with positioning rationale, use cases, and A/B testing variants. Use when creating or refreshing your brand's tagline or slogan.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete brand tagline document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Brand Tagline support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Brand Tagline or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 69. brand-voice-guide
- **purpose**: Creates a comprehensive brand voice guide with tone attributes, vocabulary lists, do's and don'ts, and platform-specific adaptations. Use when a user needs to document their brand voice for consistency, is onboarding writers or team members, or wants to establish clear messaging guidelines.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete brand voice guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Brand Voice Guide support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Brand Voice Guide or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 70. breakeven-analysis
- **purpose**: Performs break-even analyses with fixed/variable cost breakdowns, margin calculations, and scenario modeling. Use when determining how many sales you need to cover costs.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete breakeven analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Breakeven Analysis support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Breakeven Analysis or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 71. budget-planner
- **purpose**: Creates monthly and annual business budgets with category breakdowns, variance tracking, and adjustment triggers. Use when building or revising a business budget.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete budget planner document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Budget Planner support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Budget Planner or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 72. bundle-creator
- **purpose**: Designs product bundles with pricing strategy, margin analysis, and promotional copy. Use this skill when a user wants to create product bundles, increase average order value through bundling, analyze bundle margins, or write promotional copy for bundle offers in their e-commerce store.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete bundle creator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Bundle Creator support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Bundle Creator or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 73. business-continuity-plan
- **purpose**: Develops business continuity plans with risk assessment, recovery procedures, and communication protocols to keep operations running during crises.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete business continuity plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Business Continuity Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Business Continuity Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 74. business-plan
- **purpose**: Writes complete business plans with executive summary, market analysis, revenue model, and financial projections. Use when a user is starting a new venture, seeking funding, pivoting their business, or needs a structured plan to guide strategic decisions.
- **inputs**:
- `business_idea` (string, required): Business idea or concept
- `industry` (string, required): Industry or sector
- `target_market` (string, required): Target customer segment
- `funding_stage` (string, optional): Stage: pre-seed|seed|series-a|bootstrapped
- `revenue_model` (string, optional): How the business makes money
- `initial_budget` (string, optional): Available startup capital
- **outputs**:
- `executive_summary` (string): 1-page business summary
- `market_analysis` (object): Market size, competition, opportunity
- `financial_projections` (object): 3-year revenue projections
- `action_plan` (array): 90-day launch action plan
- **best used when**: When requiring strategic Business Plan support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Business Plan or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 75. campaign-plan
- **purpose**: Generate a full campaign brief with objectives, audience, messaging, channel strategy, content calendar, and success metrics. Use when planning a product launch, lead-gen push, or awareness campaign, when you need a week-by-week content calendar with dependencies, or when translating a marketing goal into a structured, executable plan.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete campaign plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Campaign Plan support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Campaign Plan or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 76. caption-writer
- **purpose**: Writes platform-optimized social media captions with CTAs, hashtags, and character limits for Instagram, LinkedIn, TikTok, X/Twitter, and Facebook. Use when a user needs captions for social media posts, wants to batch-write captions for a content calendar, or needs platform-specific formatting.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete caption writer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Caption Writer support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Caption Writer or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 77. cart-recovery-sms
- **purpose**: Writes SMS cart recovery messages with timing, personalization tokens, and compliance disclaimers. Use when you need to recover abandoned carts via text message.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete cart recovery sms document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 78. case-study
- **purpose**: Transforms client results and project outcomes into structured case studies with situation, challenge, solution, and results sections. Use when a user wants to showcase client wins, needs social proof for their sales process, or wants to document project success stories for their website or proposals.
- **inputs**:
- `client_name` (string, required): Client or customer name
- `industry` (string, required): Client's industry
- `challenge` (string, required): Problem or challenge faced
- `solution` (string, required): How your product/service solved it
- `results` (array, required): Measurable results achieved
- `timeline` (string, optional): How long the project took
- **outputs**:
- `case_study` (string): Full case study document
- `headline` (string): Compelling case study headline
- `pull_quotes` (array): Key quotes for use in marketing
- **best used when**: When requiring strategic Case Study support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Case Study or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 79. cash-flow-forecast
- **purpose**: Projects monthly cash flow for 3-12 months from revenue and expense inputs with scenario modeling and runway calculations. Use when a user needs to plan spending, evaluate whether they can afford a hire or investment, or wants to understand when they'll run out of (or accumulate) cash.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete cash flow forecast document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Cash Flow Forecast support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Cash Flow Forecast or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 80. catering-proposal
- **purpose**: Writes catering proposals with menu options, pricing tiers, service descriptions, and logistics details. Use when bidding on catering jobs or formalizing catering offers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete catering proposal document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Catering Proposal support under the Food & Restaurant domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Catering Proposal or when more specialized Food & Restaurant tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 81. cause-marketing-campaign
- **purpose**: Plans cause marketing campaigns with brand-nonprofit partnerships, messaging, and impact measurement.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete cause marketing campaign document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Cause Marketing Campaign support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Cause Marketing Campaign or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 82. cease-and-desist
- **purpose**: Drafts cease and desist letters for IP infringement, defamation, or contract violations. Use when you need to formally demand someone stop harmful activity.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete cease and desist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 83. certification-program
- **purpose**: Designs certification programs with curriculum, assessment criteria, grading rubrics, and credential management.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete certification program document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Certification Program support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Certification Program or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 84. change-management-plan
- **purpose**: Creates change management plans with stakeholder analysis, communication strategy, and transition timelines for smooth business changes.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete change management plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Change Management Plan support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Change Management Plan or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 85. chatbot-script
- **purpose**: Designs chatbot conversation flows with decision trees, handoff triggers, and fallback responses for automated customer interactions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete chatbot script document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Chatbot Script support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Chatbot Script or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 86. checkout-optimizer
- **purpose**: Audits e-commerce checkout flows and recommends friction-reduction improvements to increase conversion rates. Use this skill when a user has cart abandonment issues, low checkout completion rates, or wants to optimize their online store's purchase flow.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete checkout optimizer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 87. churn-analysis
- **purpose**: Diagnoses customer churn patterns and creates retention intervention strategies with warning signals, win-back triggers, and prevention playbooks. Use when a user is losing customers or subscribers, wants to understand why people leave, or needs to reduce churn rate for a subscription or recurring service.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete churn analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Churn Analysis support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Churn Analysis or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 88. churn-prevention-playbook
- **purpose**: Creates churn prevention playbooks with early warning indicators, intervention sequences, and save offer strategies. Use when reducing customer churn in subscription businesses.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete churn prevention playbook document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Churn Prevention Playbook support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Churn Prevention Playbook or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 89. class-schedule-planner
- **purpose**: Plans class/session schedules with instructor assignments, room allocation, and enrollment capacity management.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete class schedule planner document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Class Schedule Planner support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Class Schedule Planner or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 90. claude-config-manager
- **purpose**: This skill was automatically generated from the `.claude` infrastructure directory.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete claude config manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Claude Config Manager support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Claude Config Manager or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 91. claude-plugin-manager
- **purpose**: This skill was automatically generated from the `.claude-plugin` infrastructure directory.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete claude plugin manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Claude Plugin Manager support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Claude Plugin Manager or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 92. client-agreement
- **purpose**: Drafts client service agreements with scope, deliverables, timelines, revisions, and payment terms. Use when creating contracts for client engagements.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete client agreement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 93. client-crm
- **purpose**: Creates a complete client relationship management system in Notion with pipeline stages, contact records, deal values, and follow-up tracking. Use when a user wants to replace spreadsheet-based client tracking, set up a CRM without paid software, or build a sales pipeline from scratch.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete client crm document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Client Crm support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Client Crm or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 94. client-feedback-system
- **purpose**: Designs structured client feedback systems with mid-project check-ins and post-project reviews for service businesses.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete client feedback system document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Client Feedback System support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Client Feedback System or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 95. client-intake-form
- **purpose**: Creates client intake forms and questionnaires that gather essential project information efficiently.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete client intake form document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Client Intake Form support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Client Intake Form or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 96. client-report-template
- **purpose**: Designs client reporting templates with executive summaries, data visualizations, and next-step recommendations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete client report template document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Client Report Template support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Client Report Template or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 97. client-transformation-story
- **purpose**: Writes client transformation narratives with before/after frameworks, timeline, and ethical presentation guidelines.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete client transformation story document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Client Transformation Story support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Client Transformation Story or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 98. co-marketing-plan
- **purpose**: Plans co-marketing campaigns with partner selection criteria, shared content, cross-promotion tactics, and attribution.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete co marketing plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Co Marketing Plan support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Co Marketing Plan or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 99. coaching-framework
- **purpose**: Builds systematized coaching session structures with intake forms, session agendas, progress tracking frameworks, and client communication templates. Use when a coach, consultant, or service provider wants to systematize their 1-on-1 client work, create a repeatable coaching process, or professionalize their client experience.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete coaching framework document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Coaching Framework support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Coaching Framework or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 100. codacy-config-manager
- **purpose**: Manages Codacy linting/security configurations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete codacy config manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Codacy Config Manager support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Codacy Config Manager or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 101. cohort-analysis
- **purpose**: Creates cohort analysis frameworks for understanding retention, revenue, and behavior patterns over time. Use when measuring how user groups perform across their lifecycle.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete cohort analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Cohort Analysis support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Cohort Analysis or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 102. cohort-program
- **purpose**: Designs cohort-based learning programs with weekly structure, peer interaction, accountability systems, and graduation criteria.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete cohort program document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Cohort Program support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Cohort Program or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 103. cold-outreach
- **purpose**: Builds personalized cold email and DM outreach sequences with research-backed personalization, multi-touch follow-up cadence, subject line formulas, and response-handling scripts for every outcome. Use when an entrepreneur, freelancer, or agency owner needs to reach prospects they have no prior relationship with — for sales, partnerships, collaborations, or client acquisition.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete cold outreach document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 104. collaboration-agreement
- **purpose**: Drafts collaboration agreements for joint projects with scope, contribution, revenue, and IP ownership terms.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete collaboration agreement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 105. collection-page-copy
- **purpose**: Writes collection and category page copy with SEO-friendly descriptions, navigation aids, cross-sell suggestions, and filtering guidance. Use for e-commerce category pages.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete collection page copy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Collection Page Copy support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Collection Page Copy or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 106. color-palette-generator
- **purpose**: Generates brand color palettes with hex codes, accessibility ratings, application guidelines, and print/digital specifications. Use when establishing or refreshing brand colors.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete color palette generator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Color Palette Generator support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Color Palette Generator or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 107. commission-structure
- **purpose**: Designs sales commission structures with tiers, accelerators, clawback provisions, and payout schedules. Use when creating or revising compensation plans for sales roles.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete commission structure document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Commission Structure support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Commission Structure or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 108. community-launch
- **purpose**: Plans online community launches (Discord, Circle, Skool) with structure, rules, engagement tactics, and onboarding. Use when launching a paid or free community around your brand.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete community launch document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Community Launch support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Community Launch or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 109. community-moderation
- **purpose**: Creates community moderation guidelines with rules, escalation procedures, and automated moderation recommendations. Use when establishing or improving moderation for online communities.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete community moderation document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Community Moderation support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Community Moderation or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 110. company-profile-story-architect
- **purpose**: Premium Claude skill pack for writing company profiles, capability statements, executive bios, and related narrative assets with strategic storytelling, strong positioning, and proof-led structure
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete company profile story architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Company Profile Story Architect support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Company Profile Story Architect or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 111. comparison-article
- **purpose**: Writes 'X vs Y' comparison articles with feature tables, pros/cons, use cases, and recommendation logic. Use when creating product or service comparison content for SEO or buyer guidance.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete comparison article document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Comparison Article support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Comparison Article or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 112. compensation-plan
- **purpose**: Designs compensation plans with salary bands, bonus structures, equity frameworks, and market benchmarking for competitive hiring.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete compensation plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Compensation Plan support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Compensation Plan or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 113. competitive-brief
- **purpose**: Research competitors and generate a positioning and messaging comparison with content gaps, opportunities, and threats. Use when building sales battlecards, when finding positioning gaps and messaging angles competitors haven't claimed, or when a competitor makes a move and you need to assess the impact.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete competitive brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Competitive Brief support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Competitive Brief or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 114. competitor-analysis
- **purpose**: Conducts a structured competitor analysis with comparison matrices, positioning maps, gap identification, and strategic recommendations. Use when a user wants to understand their competitive landscape, needs to differentiate their offering, or is preparing a go-to-market strategy.
- **inputs**:
- `your_business` (string, required): Your business and offer
- `competitors` (array, required): List of competitor names/URLs
- `analysis_dimensions` (array, optional): Dimensions: pricing|content|seo|product|marketing
- **outputs**:
- `competitive_matrix` (object): Feature/attribute comparison matrix
- `gaps_opportunities` (array): Market gaps and opportunities
- `differentiation_strategy` (string): How to position against competition
- **best used when**: When requiring strategic Competitor Analysis support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Competitor Analysis or when more specialized Strategy & Planning tools are available.
- **example prompt**: "Execute PrePilot task for 'Competitor Analysis' (ID: competitor-analysis) to generate a premium strategic deliverable with inputs: your_business='Standard your_business brief', competitors=['item1', 'item2']."
- **expected result**: 
```json
{
  "competitive_matrix": {
    "status": "APPROVED",
    "score": 95,
    "remarks": "This generated competitive_matrix satisfies all professional-tier constraints."
  },
  "gaps_opportunities": [
    "Validated gaps_opportunities milestone 1",
    "Validated gaps_opportunities milestone 2"
  ],
  "differentiation_strategy": "Professional-grade differentiation_strategy output details"
}
```

#### 115. complaint-resolution
- **purpose**: Creates complaint resolution frameworks with empathy scripts, escalation paths, recovery offers, and follow-up procedures for customer retention.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete complaint resolution document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Complaint Resolution support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Complaint Resolution or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 116. compliance-checklist
- **purpose**: Creates industry-specific regulatory compliance checklists with documentation requirements and audit preparation. Use when ensuring your business meets regulatory obligations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete compliance checklist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 117. conference-planner
- **purpose**: Plans multi-day conferences with tracks, speaker management, logistics, sponsorship, and attendee experience design.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete conference planner document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Conference Planner support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Conference Planner or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 118. consulting-framework
- **purpose**: Builds consulting engagement frameworks with diagnostic questions, analysis templates, and recommendation structures.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete consulting framework document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Consulting Framework support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Consulting Framework or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 119. consulting-proposal-template
- **purpose**: Creates reusable consulting proposal templates with customizable sections for different engagement types.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete consulting proposal template document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Consulting Proposal Template support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Consulting Proposal Template or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 120. content-audit
- **purpose**: Audits existing content inventory for gaps, update opportunities, consolidation candidates, and SEO decay. Use when reviewing your content library to find what to update, merge, or remove.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete content audit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Content Audit support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Content Audit or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 121. content-brief
- **purpose**: Creates detailed content briefs for freelance writers with tone, structure, SEO targets, examples, and quality criteria. Use when a user is outsourcing content creation, needs to give clear direction to a writer, or wants to systematize their content production process.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete content brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Content Brief support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Content Brief or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 122. content-calendar
- **purpose**: Generates a 30-day content calendar as a Notion database with posts mapped to content pillars, platforms, and dates, plus starter graphic templates in Canva for each content pillar. Use when a user needs to plan their content for the month, wants a structured posting schedule, or needs to batch-create content across multiple platforms.
- **inputs**:
- `business_type` (string, required): Type of business
- `platforms` (array, required): Content platforms: blog|instagram|linkedin|youtube|tiktok
- `duration` (string, required): Calendar duration: 1-month|3-months|6-months
- `posting_frequency` (string, optional): How often to post per platform
- `content_goals` (array, optional): Goals: brand-awareness|leads|sales|engagement
- `brand_voice` (string, optional): Brand tone and voice
- **outputs**:
- `calendar` (array): Week-by-week content plan
- `content_themes` (array): Monthly themes and pillars
- `post_ideas` (array): Ready-to-use post ideas
- **best used when**: When requiring strategic Content Calendar support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Content Calendar or when more specialized Content Creation tools are available.
- **example prompt**: "Execute PrePilot task for 'Content Calendar' (ID: content-calendar) to generate a premium strategic deliverable with inputs: business_type='Standard business_type brief', platforms=['item1', 'item2'], duration='Standard duration brief'."
- **expected result**: 
```json
{
  "calendar": [
    "Validated calendar milestone 1",
    "Validated calendar milestone 2"
  ],
  "content_themes": [
    "Validated content_themes milestone 1",
    "Validated content_themes milestone 2"
  ],
  "post_ideas": [
    "Validated post_ideas milestone 1",
    "Validated post_ideas milestone 2"
  ]
}
```

#### 123. content-cluster-plan
- **purpose**: Designs topic cluster strategies with pillar pages, cluster content, and internal linking architecture. Use when building topical authority for SEO.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete content cluster plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 124. content-creation
- **purpose**: Create structured, on-brand marketing content drafts for any channel and format.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete content creation document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Content Creation support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Content Creation or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 125. content-gap-finder
- **purpose**: Identifies content gaps by analyzing competitor content, search intent mismatches, and audience questions. Use when planning what content to create next based on strategic opportunities.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete content gap finder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Content Gap Finder support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Content Gap Finder or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 126. content-machine-egypt
- **purpose**: Auto-pilot content creation system for Egyptian Content Creators and Social Media Managers. Use whenever the user needs: content calendar, social media posts/captions/copies, content strategy, content ideas, monthly plans, campaign content, or ad copy. Trigger on: 'اعملي كالندر', 'محتاج كونتنت للكلاينت', 'اكتبلي بوستات', 'كالندر شهري', 'خطة محتوى', 'بوستات سوشيال', 'كابشنز', 'content calendar', 'social media plan', 'اعملي content plan', 'عايز أفكار بوستات', 'campaign content', 'كونتنت بالمصري',
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete content machine egypt document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Content Machine Egypt support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Content Machine Egypt or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 127. content-pillar-strategy
- **purpose**: Designs a content pillar framework with 3-5 core pillars, sub-topics, and a 90-day content mapping plan. Use when building a structured content strategy from scratch or overhauling an unfocused one.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete content pillar strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Content Pillar Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Content Pillar Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 128. content-plan-architect
- **purpose**: Build full-funnel content systems and omnichannel content operating plans. Use proactively whenever a user needs a content plan, channel-by-channel content requirements, website content strategy, social media content plan, SEO/AEO/GEO content strategy, WhatsApp scripts, Telegram content, ad copy requirements, or agency-ready content production scope. Trigger on content plan, content strategy, content calendar, content production, editorial plan, or any request spanning website to social to ads to messaging channels.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete content plan architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Content Plan Architect support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Content Plan Architect or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 129. content-products-manager
- **purpose**: This skill was automatically generated from the `content` infrastructure directory.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete content products manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Content Products Manager support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Content Products Manager or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 130. content-repurpose
- **purpose**: Repurposes a single piece of content (blog post, transcript, newsletter, video script) into multiple platform-ready formats including social posts, email copy, threads, and short-form video scripts. Use when a user has existing content they want to distribute across multiple channels without writing everything from scratch.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete content repurpose document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Content Repurpose support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Content Repurpose or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 131. content-style-guide
- **purpose**: Creates editorial style guides covering grammar preferences, formatting rules, tone guidelines, and word lists. Use when standardizing content quality across writers, platforms, or team members.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete content style guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Content Style Guide support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Content Style Guide or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 132. continuing-education
- **purpose**: Plans continuing education offerings with credit requirements, course catalogs, and completion tracking systems.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete continuing education document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Continuing Education support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Continuing Education or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 133. contract-writer
- **purpose**: Drafts service agreements, freelance contracts, and partnership agreements with standard clauses and plain-language annotations explaining each section. Use when a user needs a professional contract template, wants to formalize a client relationship, or needs a starting point for legal review.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete contract writer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 134. contractor-brief
- **purpose**: Writes detailed contractor briefs with scope, deliverables, timeline, communication expectations, and payment terms for clear engagements.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete contractor brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Contractor Brief support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Contractor Brief or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 135. conversion-copy-reviewer
- **purpose**: Analyzes software landing pages and ad copy against CRO copywriting standards of neuromarketing and friction reduction. This skill should trigger whenever the user provides landing page copy, value proposition ideas, CTA button text, headline drafts, or inputs containing sales pitches.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete conversion copy reviewer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 136. conversion-funnel-analysis
- **purpose**: Maps and analyzes conversion funnels with drop-off identification, optimization priorities, and benchmarking. Use when diagnosing where prospects are lost in your sales process.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete conversion funnel analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 137. cookie-policy
- **purpose**: Writes cookie consent policies with category descriptions, opt-out mechanisms, and GDPR/CCPA compliance. Use when creating or updating your website's cookie policy.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete cookie policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 138. copyright-notice
- **purpose**: Creates copyright notices and policies for digital content with DMCA procedures and fair use guidelines. Use when protecting original content and establishing copyright policies.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete copyright notice document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 139. core-legacy
- **purpose**: Core Legacy — Professional-grade general skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete core legacy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Core Legacy support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Core Legacy or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 140. core-source-manager
- **purpose**: Manages the core TypeScript source and infrastructure code.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete core source manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Core Source Manager support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Core Source Manager or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 141. cost-analysis
- **purpose**: Performs cost-of-goods-sold and cost-per-unit analyses with margin calculations and optimization recommendations. Use when analyzing product or service costs.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete cost analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Cost Analysis support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Cost Analysis or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 142. course-outline
- **purpose**: Designs complete online course curricula with modules, lessons, learning objectives, assignments, and recommended formats. Use when a user wants to create an online course, needs to structure their expertise into teachable content, or is planning a cohort-based program or self-paced course.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete course outline document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Course Outline support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Course Outline or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 143. creative-script-writer
- **purpose**: Arabic-first creative scripting system. Writes commercially strong video scripts, UGC scripts, VSL scripts, demo/explainer scripts, voiceover scripts, ad copy, social captions, hooks, angles, CTAs, shot lists, and creative testing matrices for Egypt, Saudi, UAE/Qatar, Levant, and pan-Arab markets. Trigger on: "اكتبلي سكربت", "عايز hooks", "اعملي ad copy", "كابشن", "محتوى إعلاني", "سكربت فيديو", "نص إعلاني", "creative بالعربي", video scripts, UGC scripts, voiceover scripts, emotional storytelling
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete creative script writer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Creative Script Writer support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Creative Script Writer or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 144. creative-strategist
- **purpose**: للأفكار، الحملات، الزوايا، والـ content angles اللي يقدر الفريق يبني عليها شغل قابل للنشر والاختبار
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete creative strategist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Creative Strategist support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Creative Strategist or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 145. crisis-comms
- **purpose**: Creates crisis communication plans with response templates, escalation protocols, and stakeholder messaging for business emergencies. Use when a user faces a PR crisis, product failure, data breach, negative viral attention, or needs proactive crisis preparedness plans.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete crisis comms document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Crisis Comms support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Crisis Comms or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 146. cross-border-selling
- **purpose**: Plans international selling strategies with localization, shipping, duties/taxes, and compliance considerations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete cross border selling document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Cross Border Selling support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Cross Border Selling or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 147. cross-sell-strategy
- **purpose**: Maps cross-sell opportunities with product pairing logic, timing triggers, and messaging templates. Use when you want to increase revenue from existing customers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete cross sell strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Cross Sell Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Cross Sell Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 148. culture-document
- **purpose**: Writes company culture documents with values, behaviors, rituals, and how culture shows up in daily work for team alignment.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete culture document document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Culture Document support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Culture Document or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 149. curriculum-review
- **purpose**: Reviews and improves existing course curricula with gap analysis, modern content updates, and engagement optimization.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete curriculum review document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Curriculum Review support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Curriculum Review or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 150. customer-advisory-board
- **purpose**: Plans customer advisory board programs with recruitment criteria, meeting structure, and feedback integration processes for strategic input.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete customer advisory board document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Customer Advisory Board support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Customer Advisory Board or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 151. customer-health-score
- **purpose**: Designs customer health scoring models with engagement metrics, risk indicators, and intervention triggers to prevent churn proactively.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete customer health score document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Customer Health Score support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Customer Health Score or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 152. customer-journey-map
- **purpose**: Maps the full customer journey from awareness through advocacy, identifying touchpoints, emotions, pain points, and conversion gaps. Use when a user wants to understand their customer experience end-to-end, find drop-off points, improve conversion at specific stages, or design a better onboarding/purchase flow.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete customer journey map document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Customer Journey Map support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Customer Journey Map or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 153. customer-lifetime-value
- **purpose**: Calculates customer lifetime value with segmentation, prediction models, and retention investment recommendations. Use when determining how much a customer is worth over time.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete customer lifetime value document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Customer Lifetime Value support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Customer Lifetime Value or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 154. customer-persona
- **purpose**: Creates detailed customer personas with demographics, psychographics, buying behaviors, and messaging preferences for targeted marketing.
- **inputs**:
- `business_description` (string, required): What your business does
- `product_service` (string, required): Product or service being sold
- `known_customers` (string, optional): What you already know about your customers
- `personas_count` (integer, optional): Number of personas to create (default: 3)
- **outputs**:
- `personas` (array): Detailed customer personas
- `pain_points_map` (array): Key pain points per persona
- `messaging_guide` (object): How to speak to each persona
- **best used when**: When requiring strategic Customer Persona support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Customer Persona or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 155. customer-review-strategy
- **purpose**: Designs post-purchase review collection strategies with timing, email templates, and incentive programs to build social proof.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete customer review strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Customer Review Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Customer Review Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 156. customer-segmentation
- **purpose**: Segments customers by behavior, value, and needs with tailored communication strategies per segment for targeted engagement.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete customer segmentation document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Customer Segmentation support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Customer Segmentation or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 157. customer-success-playbook
- **purpose**: Creates customer success playbooks with lifecycle stages, touchpoint cadence, and expansion opportunity identification for retention and growth.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete customer success playbook document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Customer Success Playbook support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Customer Success Playbook or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 158. customer-support-kb
- **purpose**: Builds a complete customer support knowledge base with tiered FAQs, canned response templates, troubleshooting decision trees, and escalation protocols. Use when a user needs to systematize customer support, reduce response times, onboard support staff, or stop answering the same questions repeatedly.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete customer support kb document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Customer Support Kb support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Customer Support Kb or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 159. customer-win-story
- **purpose**: Transforms customer successes into internal win stories with metrics, timeline, and key moments for team motivation and learning.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete customer win story document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Customer Win Story support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Customer Win Story or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 160. data-collection-plan
- **purpose**: Plans data collection strategies with tracking requirements, privacy compliance, storage recommendations, and implementation steps. Use when building your business data infrastructure.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete data collection plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Data Collection Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Data Collection Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 161. data-dashboard-design
- **purpose**: Plans data dashboard layouts with metric selection, visualization types, refresh frequency, and user-focused design. Use when building dashboards that drive decisions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete data dashboard design document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Data Dashboard Design support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Data Dashboard Design or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 162. data-processing-agreement
- **purpose**: Drafts data processing agreements for GDPR compliance with processing details and security measures. Use when you process personal data on behalf of another business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete data processing agreement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 163. decision-matrix
- **purpose**: Creates weighted decision matrices for business choices with criteria, scoring, and recommendation logic to remove emotion from decisions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete decision matrix document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Decision Matrix support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Decision Matrix or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 164. delegation-framework
- **purpose**: Builds task delegation systems with responsibility matrices, handoff templates, accountability tracking, and escalation protocols. Use when a solopreneur is hiring their first VA, a team lead is struggling with delegation, or an agency is scaling operations and needs clear ownership of tasks.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete delegation framework document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Delegation Framework support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Delegation Framework or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 165. diagnostic-assessment
- **purpose**: Builds diagnostic assessment tools for consulting engagements with scoring, benchmarking, and recommendation logic.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete diagnostic assessment document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Diagnostic Assessment support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Diagnostic Assessment or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 166. digital-product-plan
- **purpose**: Plans digital product creation (templates, tools, resources) with market validation, pricing, and distribution. Use when building downloadable products for passive income.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete digital product plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Digital Product Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Digital Product Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 167. direct-response-funnel-auditor
- **purpose**: Audit, diagnose, and improve aggressive direct-response landing pages, info-product pages, bundle offers, tripwire funnels, and offer-driven sales pages without damaging the conversion mechanisms that already sell. Use when the user asks to analyze a landing page, funnel, sales page, offer page, screenshots, page copy, or wants controlled improvements for a page that is selling well.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete direct response funnel auditor document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 168. disclaimer-generator
- **purpose**: Generates legal disclaimers for websites, products, and services with liability limitations and warranty exclusions. Use when adding disclaimers to your business properties.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete disclaimer generator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 169. discount-strategy
- **purpose**: Plans promotional pricing campaigns with discount types, timing, margin-safe guardrails, and promotion calendars. Use this skill when a user wants to run a sale, create a promotional offer, or plan seasonal discounts without destroying their profit margins.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete discount strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Discount Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Discount Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 170. discovery-call-script
- **purpose**: Creates discovery call frameworks with qualifying questions, pain point exploration, and next-step closing. Use when you need a structured script for sales calls.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete discovery call script document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Discovery Call Script support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Discovery Call Script or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 171. diversity-policy
- **purpose**: Writes diversity, equity, and inclusion policies with commitments, programs, accountability measures, and implementation timelines. Use when building or updating your company DEI framework.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete diversity policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 172. donation-page-copy
- **purpose**: Writes donation page copy with urgency, impact framing, recurring giving encouragement, and trust signals.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete donation page copy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Donation Page Copy support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Donation Page Copy or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 173. downsell-sequence
- **purpose**: Builds downsell offers and sequences for prospects who decline the primary offer. Use when you need to capture revenue from people who say no to your main pitch.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete downsell sequence document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Downsell Sequence support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Downsell Sequence or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 174. drip-campaign
- **purpose**: Builds nurture drip campaigns with conditional logic, lead scoring triggers, and content mapping per stage. Use when you need automated email sequences that move leads through your funnel based on behavior.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete drip campaign document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 175. dropshipping-supplier-brief
- **purpose**: Creates supplier evaluation and communication templates for dropshipping businesses with quality standards, SLAs, and order management workflows. Use when vetting dropshipping partners.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete dropshipping supplier brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Dropshipping Supplier Brief support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Dropshipping Supplier Brief or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 176. ebook-outline
- **purpose**: Outlines downloadable ebooks with chapter structure, design notes, and lead magnet positioning strategy. Use when creating a free or paid ebook as a content asset or lead generator.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ebook outline document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Ebook Outline support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ebook Outline or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 177. email-ab-test-plan
- **purpose**: Designs A/B testing plans for email campaigns with hypothesis, test variables, sample sizes, and success metrics. Use when you need data-driven email optimization.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete email ab test plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 178. email-deliverability-audit
- **purpose**: Audits email practices for deliverability issues including sender reputation, authentication, and list hygiene. Use when emails are landing in spam or engagement rates are dropping.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete email deliverability audit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 179. email-design-system
- **purpose**: Designs email template systems with header/footer standards, button styles, image guidelines, responsive rules, and type-specific layouts. Use when standardizing email communications.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete email design system document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 180. email-list-cleanup
- **purpose**: Plans email list segmentation and cleanup strategies with re-engagement criteria and sunsetting rules. Use when your list has inactive subscribers hurting deliverability.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete email list cleanup document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 181. email-newsletter-template
- **purpose**: Designs reusable newsletter templates with section layouts, formatting rules, and brand guidelines. Use when creating a consistent, repeatable newsletter format you can use every edition.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete email newsletter template document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 182. email-preference-center
- **purpose**: Designs email preference center structure with subscription options, frequency controls, and topic selections. Use when you need to reduce unsubscribes and give subscribers control.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete email preference center document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 183. email-sequence
- **purpose**: Builds complete automated email sequences with timing delays, conditional triggers, A/B subject lines, and platform-specific implementation notes. Use when a user needs a welcome series, nurture sequence, launch sequence, re-engagement campaign, or any multi-email automation flow.
- **inputs**:
- `sequence_goal` (string, required): Goal: nurture|onboard|re-engage|launch|upsell
- `audience` (string, required): Who receives this sequence
- `email_count` (integer, optional): Number of emails (default: 5-7)
- `frequency` (string, optional): Send frequency: daily|every-2-days|weekly
- `product` (string, optional): Product or service being promoted
- `brand_voice` (string, optional): Brand voice and tone
- `trigger` (string, optional): What triggers this sequence
- **outputs**:
- `email_sequence` (array): Array of emails with subject, body, and CTA
- `sequence_map` (object): Visual sequence flow with timing
- `subject_line_variants` (array): A/B test variants for each email
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 184. email-subject-line-tester
- **purpose**: Generates and scores 20+ subject line variations using proven formulas and predicts open rate performance. Use when you need high-performing email subject lines.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete email subject line tester document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 185. employee-handbook
- **purpose**: Creates employee or contractor handbooks with company policies, expectations, benefits, communication guidelines, and operational procedures in a professional yet approachable tone. Use when a user is hiring their first employee, onboarding contractors, scaling their team, or needs to formalize workplace policies.
- **inputs**:
- `company_name` (string, required): Company name
- `company_size` (string, required): Team size: 1-10|10-50|50-200|200+
- `work_model` (string, required): Work model: remote|hybrid|in-office
- `industry` (string, optional): Industry type
- `company_values` (array, optional): Core company values
- `policies_to_include` (array, optional): Specific policies to include
- **outputs**:
- `handbook` (string): Complete employee handbook
- `policy_checklist` (array): Policies included and their status
- **best used when**: When requiring strategic Employee Handbook support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Employee Handbook or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 186. employee-survey
- **purpose**: Creates employee engagement surveys with anonymous feedback mechanisms, question categories, rating scales, and action planning frameworks. Use when measuring team satisfaction or culture.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete employee survey document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Employee Survey support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Employee Survey or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 187. energy-management
- **purpose**: Maps energy levels to task types for optimized daily scheduling with peak performance time blocks and recovery periods.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete energy management document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Energy Management support under the Health & Wellness domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Energy Management or when more specialized Health & Wellness tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 188. engagement-playbook
- **purpose**: Builds engagement strategies with comment response templates, DM scripts, and community interaction frameworks. Use when you need a systematic approach to social media engagement.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete engagement playbook document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Engagement Playbook support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Engagement Playbook or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 189. escalation-procedure
- **purpose**: Defines escalation procedures with trigger criteria, escalation levels, response time requirements, and resolution tracking for support issues.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete escalation procedure document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Escalation Procedure support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Escalation Procedure or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 190. event-budget-planner
- **purpose**: Creates event budgets with line items, contingency planning, sponsor offset calculations, and ROI projections.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete event budget planner document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Event Budget Planner support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Event Budget Planner or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 191. event-follow-up
- **purpose**: Creates post-event follow-up sequences with thank-you emails, survey distribution, content delivery, and nurture paths.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete event follow up document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Event Follow Up support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Event Follow Up or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 192. event-marketing-plan
- **purpose**: Creates event marketing campaigns with timeline, channels, early bird promotions, and attendance forecasting.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete event marketing plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Event Marketing Plan support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Event Marketing Plan or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 193. event-planner
- **purpose**: Plans virtual and in-person events with detailed checklists, timelines, run-of-show documents, promotional copy, and attendee communications, with optional planning pages in Notion. Use when a user is organizing a workshop, conference, meetup, launch party, networking event, or any event that needs structured planning and communication materials.
- **inputs**:
- `event_name` (string, required): Event name or type
- `event_type` (string, required): Type: conference|workshop|webinar|networking|launch|corporate
- `audience_size` (integer, required): Expected attendee count
- `date` (string, required): Event date or timeframe
- `budget` (string, optional): Total event budget
- `venue_type` (string, optional): in-person|virtual|hybrid
- `goals` (array, optional): Event goals and success criteria
- **outputs**:
- `event_plan` (object): Complete event planning document
- `timeline` (array): Pre-event timeline and tasks
- `run_of_show` (array): Day-of event schedule
- `checklist` (array): Master event checklist
- **best used when**: When requiring strategic Event Planner support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Event Planner or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 194. event-registration-page
- **purpose**: Writes event registration page copy with agenda highlights, speaker bios, pricing tiers, and urgency elements.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete event registration page document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Event Registration Page support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Event Registration Page or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps


### Chunk 2 Skills Index

#### 1. event-run-of-show
- **purpose**: Creates detailed run-of-show documents with minute-by-minute timing, cues, transitions, and contingency plans.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete event run of show document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Event Run Of Show support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Event Run Of Show or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 2. event-sponsorship-proposal
- **purpose**: Creates event sponsorship proposals with tier packages, benefits, audience data, and activation opportunities.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete event sponsorship proposal document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Event Sponsorship Proposal support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Event Sponsorship Proposal or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 3. exchange-policy
- **purpose**: Writes exchange policies with eligibility criteria, process steps, customer communication templates, and exception handling. Use when establishing or improving your exchange process.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete exchange policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 4. executive-resume
- **purpose**: Writes executive resumes with achievement-focused content, leadership narrative, and ATS-friendly formatting.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete executive resume document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Executive Resume support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Executive Resume or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 5. exit-interview-template
- **purpose**: Creates exit interview question templates with themed categories for identifying retention issues, improvement areas, and actionable insights. Use when an employee is departing.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete exit interview template document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Exit Interview Template support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Exit Interview Template or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 6. expense-policy
- **purpose**: Creates corporate expense policies with spending limits, approval workflows, and reimbursement procedures. Use when establishing rules for business spending and reimbursements.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete expense policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 7. expense-tracker
- **purpose**: Creates an expense tracking and categorization system in Notion with transaction records, category breakdowns, monthly summaries, and tax-deduction flagging for freelancers and small businesses. Use when a user needs to track business expenses, wants to replace spreadsheet-based bookkeeping, or needs to organize receipts and transactions for tax time.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete expense tracker document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Expense Tracker support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Expense Tracker or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 8. expert-positioning
- **purpose**: Builds expert positioning strategies with thought leadership plans, speaking opportunities, and visibility tactics.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete expert positioning document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Expert Positioning support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Expert Positioning or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 9. expert-roundup-pitch
- **purpose**: Writes pitches for inclusion in expert roundups with quotable responses and authority-building positioning. Use when seeking backlinks and thought leadership exposure.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete expert roundup pitch document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Expert Roundup Pitch support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Expert Roundup Pitch or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 10. facebook-ad-campaign
- **purpose**: Plans Facebook/Meta ad campaigns with audience targeting, ad creative briefs, budget allocation, and testing strategy. Use when running paid ads on Meta platforms.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete facebook ad campaign document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Facebook Ad Campaign support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Facebook Ad Campaign or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 11. facebook-group-plan
- **purpose**: Plans Facebook Group strategy with content schedule, engagement prompts, moderation rules, and growth tactics. Use when launching or revitalizing a Facebook Group for community and lead generation.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete facebook group plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Facebook Group Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Facebook Group Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 12. faq-generator
- **purpose**: Generates comprehensive FAQ sections organized by category with clear, concise answers optimized for websites, sales pages, and help centers. Use when a user needs an FAQ section for their website, wants to preempt common customer questions, or is building a help page for a product or service.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete faq generator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Faq Generator support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Faq Generator or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 13. feature-announcement
- **purpose**: Writes feature release announcements with benefit framing, screenshots, and adoption encouragement across channels. Use when launching new product features.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete feature announcement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Feature Announcement support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Feature Announcement or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 14. feature-request-system
- **purpose**: Designs feature request collection and prioritization systems with voting, tagging, and roadmap integration. Use when organizing customer input into product decisions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete feature request system document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Feature Request System support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Feature Request System or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 15. featured-snippet-optimizer
- **purpose**: Optimizes content to win featured snippets with format analysis, answer structure, and formatting. Use when targeting position zero in Google search results.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete featured snippet optimizer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 16. feedback-analysis
- **purpose**: Analyzes customer feedback data to identify themes, sentiment patterns, and actionable improvement priorities for product and service decisions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete feedback analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Feedback Analysis support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Feedback Analysis or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 17. financial-dashboard
- **purpose**: Creates a financial KPI tracking dashboard structure with revenue, expenses, margins, runway, and trend analysis. Use this skill when a business owner wants a single view of their financial health, needs to set up KPI tracking, or wants to monitor financial metrics consistently.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete financial dashboard document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Financial Dashboard support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Financial Dashboard or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 18. financial-model
- **purpose**: Builds financial models for startups with revenue drivers, cost assumptions, and sensitivity analysis. Use when creating detailed financial models for fundraising or planning.
- **inputs**:
- `business_type` (string, required): Type of business (SaaS, e-commerce, service, etc.)
- `revenue_streams` (array, required): All revenue sources
- `cost_structure` (object, required): Fixed and variable costs
- `projection_period` (string, optional): Years to project: 1|3|5
- `growth_assumptions` (object, optional): Growth rate assumptions
- **outputs**:
- `income_statement` (object): Projected P&L
- `cash_flow` (object): Cash flow projection
- `kpis` (array): Key financial KPIs
- `breakeven_point` (object): Breakeven analysis
- **best used when**: When requiring strategic Financial Model support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Financial Model or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 19. financial-projection
- **purpose**: Builds 12-month financial projections with revenue scenarios, expense forecasting, and break-even analysis. Use when planning future revenue and expenses for your business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete financial projection document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Financial Projection support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Financial Projection or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 20. fitness-program-outline
- **purpose**: Outlines fitness programs with phase structure, progression logic, exercise selection, and client modifications.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete fitness program outline document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Fitness Program Outline support under the Health & Wellness domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Fitness Program Outline or when more specialized Health & Wellness tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 21. flash-sale-campaign
- **purpose**: Plans flash sale campaigns with countdown messaging, email sequence, and social media coordination. Use when running a short, time-limited promotional event.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete flash sale campaign document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Flash Sale Campaign support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Flash Sale Campaign or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 22. food-delivery-strategy
- **purpose**: Plans food delivery operations with platform selection, packaging, pricing, and quality control procedures. Use when launching or optimizing restaurant delivery service.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete food delivery strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Food Delivery Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Food Delivery Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 23. food-photography-brief
- **purpose**: Creates food photography shot lists with styling direction, composition notes, and platform-specific dimensions. Use when planning photo shoots for menus, social media, or marketing.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete food photography brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Food Photography Brief support under the Food & Restaurant domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Food Photography Brief or when more specialized Food & Restaurant tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 24. food-truck-business-plan
- **purpose**: Creates food truck business plans with menu strategy, location planning, permits checklist, and revenue projections. Use when launching or scaling a food truck business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete food truck business plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Food Truck Business Plan support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Food Truck Business Plan or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 25. freelance-rate-card
- **purpose**: Calculates freelance rates based on expenses, desired income, and market positioning with rate card formatting. Use when setting or updating your freelance pricing.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete freelance rate card document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Freelance Rate Card support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Freelance Rate Card or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 26. freelancer-management
- **purpose**: Creates systems for managing multiple freelancers with briefing templates, feedback processes, payment workflows, and quality control. Use when scaling with contract talent.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete freelancer management document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Freelancer Management support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Freelancer Management or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 27. frontend-architect
- **purpose**: Manages frontend React/TypeScript architecture and assets.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete frontend architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Frontend Architect support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Frontend Architect or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 28. fulfillment-sop
- **purpose**: Creates order fulfillment SOPs with picking, packing, shipping procedures, quality control checkpoints, and error handling. Use when standardizing your shipping operations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete fulfillment sop document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Fulfillment Sop support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Fulfillment Sop or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 29. fundraising-tracker
- **purpose**: Creates fundraising pipeline trackers with investor stages, valuation calculations, and term sheet comparisons. Use when managing an active fundraising process.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete fundraising tracker document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Fundraising Tracker support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Fundraising Tracker or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 30. gdpr-compliance-checklist
- **purpose**: Creates GDPR compliance checklists with data mapping, consent mechanisms, and breach response procedures. Use when ensuring your business complies with GDPR requirements.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete gdpr compliance checklist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 31. gem-dmm-agent-pack
- **purpose**: Gem Dmm Agent Pack — Professional-grade system skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete gem dmm agent pack document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Gem Dmm Agent Pack support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Gem Dmm Agent Pack or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 32. ghostwriter-brief
- **purpose**: Creates comprehensive briefs for ghostwriters including voice samples, topic guidance, SEO targets, and style rules. Use when hiring a writer and need to communicate your expectations clearly.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ghostwriter brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Ghostwriter Brief support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ghostwriter Brief or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 33. gift-guide
- **purpose**: Creates themed gift guides with product curation, descriptions, price tiers, and promotional strategy for seasonal marketing.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete gift guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Gift Guide support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Gift Guide or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 34. github-actions-manager
- **purpose**: Manages GitHub Actions workflows and issue templates.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete github actions manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Github Actions Manager support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Github Actions Manager or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 35. github-instructions-manager
- **purpose**: Manages Copilot instructions and GitHub-specific docs.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete github instructions manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Github Instructions Manager support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Github Instructions Manager or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 36. google-ads-campaign
- **purpose**: Plans Google Ads campaigns with keyword groups, ad copy variations, landing page recommendations, and bid strategy. Use when running paid search advertising.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete google ads campaign document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Google Ads Campaign support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Google Ads Campaign or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 37. google-business-profile
- **purpose**: Optimizes Google Business Profile listings with categories, attributes, posts, Q&A, and review response templates. Use when improving local search presence.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete google business profile document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Google Business Profile support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Google Business Profile or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 38. grant-application
- **purpose**: Writes small business grant applications with narrative sections, budget justification, and impact statements. Use when applying for business grants or funding.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete grant application document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Grant Application support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Grant Application or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 39. grant-report
- **purpose**: Writes grant progress and final reports with metric tracking, narrative updates, and financial accounting.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete grant report document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Grant Report support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Grant Report or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 40. group-program-design
- **purpose**: Designs group coaching or fitness programs with cohort structure, scheduling, pricing, and community elements.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete group program design document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Group Program Design support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Group Program Design or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 41. gtm-sales-consultant
- **purpose**: لبناء عروض دخول السوق، lead gen logic، رسائل البيع، وتوضيح الـ offer قبل إطلاق الحملات
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete gtm sales consultant document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 42. guest-post-pitch
- **purpose**: Writes pitches for guest posting on target blogs with topic ideas, credentials summary, and follow-up templates. Use when you want to publish content on other websites for authority and backlinks.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete guest post pitch document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Guest Post Pitch support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Guest Post Pitch or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 43. hashtag-strategy
- **purpose**: Researches and organizes platform-specific hashtag sets by reach tier and content pillar. Use this skill when a content creator wants to maximize discoverability through strategic hashtag use on Instagram, TikTok, LinkedIn, or other platforms.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete hashtag strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Hashtag Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Hashtag Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 44. headline-generator
- **purpose**: Generates 20+ headline variations using proven formulas (how-to, listicle, question, number, curiosity gap). Use when you need compelling headlines for blog posts, ads, emails, or landing pages.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete headline generator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Headline Generator support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Headline Generator or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 45. health-disclaimer
- **purpose**: Creates health and fitness disclaimers with liability protection, medical advice boundaries, and consent forms.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete health disclaimer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 46. help-center-article
- **purpose**: Writes help center articles with step-by-step instructions, screenshot placeholders, and troubleshooting sections for customer self-service.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete help center article document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Help Center Article support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Help Center Article or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 47. high-ticket-sales-page
- **purpose**: Writes sales pages for premium ($500+) offers with extensive social proof, objection handling, and application CTAs. Use for high-ticket products and services.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete high ticket sales page document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 48. hiring-scorecard
- **purpose**: Creates structured interview scorecards with competency ratings, question banks, and evaluation rubrics for objective hiring decisions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete hiring scorecard document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Hiring Scorecard support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Hiring Scorecard or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 49. homework-assignment
- **purpose**: Creates homework and practice assignments with clear instructions, grading criteria, and learning connections.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete homework assignment document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Homework Assignment support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Homework Assignment or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 50. hook-generator
- **purpose**: Generates attention-grabbing hooks for any content format including video intros, social posts, emails, articles, and ads. Use when a user needs opening lines that stop the scroll, wants to test multiple hook angles for a piece of content, or is struggling with how to start their content.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete hook generator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Hook Generator support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Hook Generator or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 51. hybrid-event-plan
- **purpose**: Plans hybrid events with in-person and virtual audience coordination, tech setup, and unified experience design.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete hybrid event plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Hybrid Event Plan support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Hybrid Event Plan or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 52. icon-set-brief
- **purpose**: Briefs icon set design with style direction, size requirements, use cases, consistency guidelines, and delivery specifications. Use when commissioning custom icons for your brand.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete icon set brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Icon Set Brief support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Icon Set Brief or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 53. impact-report
- **purpose**: Creates annual impact reports with metric visualization, beneficiary stories, and donor recognition sections.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete impact report document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Impact Report support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Impact Report or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 54. independent-contractor-agreement
- **purpose**: Creates independent contractor agreements with scope, payment, IP ownership, and non-compete clauses. Use when hiring freelancers or contractors for your business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete independent contractor agreement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 55. industry-association-plan
- **purpose**: Plans industry association involvement with membership selection, participation strategy, and leadership positioning.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete industry association plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Industry Association Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Industry Association Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 56. influencer-campaign-brief
- **purpose**: Creates detailed campaign briefs for influencer partnerships with deliverables, messaging guidelines, and approval workflows. Use when planning influencer marketing collaborations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete influencer campaign brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Influencer Campaign Brief support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Influencer Campaign Brief or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 57. influencer-outreach
- **purpose**: Creates influencer collaboration proposals with pitch templates, compensation models, and follow-up sequences. Use this skill when a user wants to partner with content creators or influencers for brand promotion, needs outreach templates, or is planning an influencer marketing campaign.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete influencer outreach document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Influencer Outreach support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Influencer Outreach or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 58. instagram-carousel
- **purpose**: Plans Instagram carousel posts with slide-by-slide copy, design notes, and caption with hashtags. Use when you need educational or storytelling carousel content for Instagram.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete instagram carousel document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Instagram Carousel support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Instagram Carousel or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 59. intellectual-property-audit
- **purpose**: Audits IP assets with trademark, copyright, trade secret, and patent inventory and protection recommendations. Use when assessing and organizing your business IP portfolio.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete intellectual property audit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When writing high-converting property listings, building neighborhood guides, or analyzing rental property ROIs.
- **avoid when**: When drafting general technology software documentation or engineering cloud pipelines.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 60. interview-question-bank
- **purpose**: Creates role-specific interview question banks with behavioral, situational, and technical categories for structured hiring interviews.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete interview question bank document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Interview Question Bank support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Interview Question Bank or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 61. inventory-management
- **purpose**: Sets up inventory tracking systems with reorder points, supplier management, and stockout prevention for product-based businesses.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete inventory management document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Inventory Management support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Inventory Management or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 62. investment-property-analysis
- **purpose**: Analyzes rental investment properties with cash flow projections, cap rate calculations, and ROI scenarios.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete investment property analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When writing high-converting property listings, building neighborhood guides, or analyzing rental property ROIs.
- **avoid when**: When drafting general technology software documentation or engineering cloud pipelines.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 63. investor-update
- **purpose**: Creates monthly investor update emails with metrics, highlights, challenges, and asks in a standard format. Use when sending regular updates to investors or advisors.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete investor update document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Investor Update support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Investor Update or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 64. invoice-template
- **purpose**: Generates professional invoice documents with line items, tax calculations, payment terms, and late payment policies, plus a reusable template for future invoices. Use when a user needs to create an invoice, set up a billing system, or standardize their invoicing process as a freelancer or small business owner.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete invoice template document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Invoice Template support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Invoice Template or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 65. job-posting
- **purpose**: Writes compelling job descriptions and hiring ads with role summaries, responsibilities, requirements, benefits, and application instructions optimized for job boards and social media. Use when a user needs to hire employees or contractors, wants to post on job boards, or needs a role description for their careers page.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete job posting document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Job Posting support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Job Posting or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 66. joint-venture-proposal
- **purpose**: Writes joint venture proposals with value exchange, revenue sharing, responsibilities, and exit terms.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete joint venture proposal document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Joint Venture Proposal support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Joint Venture Proposal or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 67. keyword-research
- **purpose**: Conducts keyword research with search volume estimates, difficulty assessment, and content mapping recommendations. Use when planning SEO-driven content.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete keyword research document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 68. knowledge-base-builder
- **purpose**: Structures internal knowledge bases with categories, article templates, and maintenance procedures for organized business documentation.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete knowledge base builder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Knowledge Base Builder support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Knowledge Base Builder or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 69. kpi-dashboard
- **purpose**: Sets up KPI tracking dashboards in Notion with metrics, targets, status indicators, and trend tracking for any business type. Use when a user wants to track business performance, needs a visual dashboard for key metrics, or wants to replace scattered spreadsheets with a centralized KPI view.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete kpi dashboard document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Kpi Dashboard support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Kpi Dashboard or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 70. landing-page-architect
- **purpose**: The ultimate HTML landing page skill for Claude.ai artifacts. Use this skill EVERY TIME the user asks to build, design, create, or improve a landing page, sales page, coming soon page, product page, signup page, event page, or any marketing page as an HTML artifact. Also trigger when the user says 'landing page', 'sales page', 'hero section', 'build me a page', 'design a page', 'marketing page', 'conversion page', 'squeeze page', 'opt-in page', 'launch page', 'promo page', 'one-pager', or any variation in Arabic like 'اعملي landing page', 'صمملي صفحة', 'عايز صفحة هبوط', 'صفحة تسويقية'. Covers: design system generation (67 styles, 161 color palettes, 57 font pairings, 100 industry reasoning rules), conversion-focused layout patterns, RTL/Arabic support, SEO/AEO/GEO/AIO 2026 standards, and anti-AI-slop aesthetics. Produces single-file HTML artifacts with Tailwind CSS via CDN that look hand-designed, not AI-generated.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete landing page architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 71. landing-page-audit
- **purpose**: Audits landing pages for conversion optimization with layout, copy, social proof, and CTA recommendations. Use when you need to improve a landing page's conversion rate or identify why a page is underperforming.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete landing page audit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 72. landing-page-copy
- **purpose**: Writes conversion-focused landing page copy with hero, benefits, social proof, and CTA sections. Use when building a landing page for a product, service, or lead magnet.
- **inputs**:
- `offer` (string, required): What you're offering (lead magnet, product, service)
- `audience` (string, required): Target audience and pain points
- `conversion_goal` (string, required): Primary CTA: opt-in|purchase|demo|free-trial
- `unique_value_prop` (string, required): Main value proposition
- `benefits` (array, optional): Key benefits list
- `social_proof` (string, optional): Available testimonials or stats
- **outputs**:
- `headline` (string): Hero headline
- `subheadline` (string): Supporting subheadline
- `body_copy` (string): Full page copy
- `cta_copy` (string): CTA button text
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: "Execute PrePilot task for 'Landing Page Copy' (ID: landing-page-copy) to generate a premium strategic deliverable with inputs: offer='Standard offer brief', audience='Standard audience brief', conversion_goal='Standard conversion_goal brief', unique_value_prop='Standard unique_value_prop brief'."
- **expected result**: 
```json
{
  "headline": "Professional-grade headline output details",
  "subheadline": "Professional-grade subheadline output details",
  "body_copy": "Professional-grade body_copy output details",
  "cta_copy": "Professional-grade cta_copy output details"
}
```

#### 73. landing-page-generator-super
- **purpose**: 22-stage intelligent landing page generation system. Run EVERY TIME someone needs a landing page: "build me a landing page", "create sales page", "اعملي صفحة هبوط". Executes evidence collection → business model detection (8 models) → psychology analysis (6 frameworks: loss aversion, social proof, authority, scarcity, reciprocity, cognitive ease) → design system selection (8 variants) → copy generation (native Arabic or English, zero buzzwords) → tracking architecture (11 custom Meta Pixel events
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete landing page generator super document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 74. landing-page-superhero-builder
- **purpose**: Use when creating, adapting, auditing, or repairing PrePilot-style landing pages, checkout pages, lead-capture funnels, WhatsApp handoffs, Meta Pixel/CAPI tracking, RTL Arabic sales pages, or dark SaaS offer pages in Claude, Codex, or any coding agent environment.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete landing page superhero builder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 75. launch-assets
- **purpose**: Builds a complete product or service launch package with a structured checklist in Notion and coordinated visual assets in Canva, including social media graphics, announcement images, and email headers. Use when a user is preparing to launch a product, course, service, or campaign and needs both the planning checklist and the visual assets created together.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete launch assets document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Launch Assets support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Launch Assets or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 76. launch-checklist
- **purpose**: Builds comprehensive pre-launch and post-launch checklists with dependencies and go/no-go gates. Use this skill when a user is launching a product, course, service, website, or campaign and needs to ensure nothing slips through the cracks during the launch process.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete launch checklist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Launch Checklist support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Launch Checklist or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 77. launch-email-sequence
- **purpose**: Builds pre-launch to post-launch email sequences with teaser, announcement, urgency, and follow-up phases. Use when launching a new product, service, or offer.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete launch email sequence document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 78. lead-magnet
- **purpose**: Creates lead magnet content (checklists, cheat sheets, mini-guides, templates) plus the landing page copy to promote it, including headline, benefit bullets, CTA, and objection handling. Use when a user wants to grow their email list, needs a free downloadable resource, or wants to create an opt-in incentive for their audience.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete lead magnet document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Lead Magnet support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Lead Magnet or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 79. learning-path
- **purpose**: Maps learning paths with prerequisite skills, milestone assessments, and recommended resource sequences.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete learning path document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Learning Path support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Learning Path or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 80. lease-agreement-checklist
- **purpose**: Creates lease agreement review checklists ensuring all essential terms, disclosures, and addenda are included.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete lease agreement checklist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 81. lesson-plan
- **purpose**: Creates structured lesson plans with objectives, activities, assessment methods, and differentiation strategies.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete lesson plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Lesson Plan support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Lesson Plan or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 82. letter-of-intent
- **purpose**: Creates letters of intent for business transactions with key terms, conditions, and timeline. Use when formalizing preliminary agreement on a business deal.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete letter of intent document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Letter Of Intent support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Letter Of Intent or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 83. licensing-agreement
- **purpose**: Drafts content and product licensing agreements with usage rights, royalty structures, exclusivity terms, and territory definitions. Use this skill when a creator wants to license their intellectual property, photos, courses, templates, music, or digital products to another party.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete licensing agreement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 84. link-building-plan
- **purpose**: Designs link building strategies with outreach templates, target site lists, and content-based link earning tactics. Use when you need to improve domain authority.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete link building plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 85. linkedin-ad-campaign
- **purpose**: Plans LinkedIn ad campaigns with audience targeting, ad formats, lead gen form design, and budget recommendations. Use when running B2B advertising campaigns on LinkedIn.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete linkedin ad campaign document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Linkedin Ad Campaign support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Linkedin Ad Campaign or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 86. linkedin-article
- **purpose**: Writes long-form LinkedIn articles optimized for the platform's algorithm with professional tone, engagement hooks, and CTA. Use when you need thought leadership content published directly on LinkedIn.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete linkedin article document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Linkedin Article support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Linkedin Article or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 87. linkedin-profile-optimizer
- **purpose**: Optimizes LinkedIn profiles with headline formulas, about section copywriting, experience descriptions, and keyword strategy.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete linkedin profile optimizer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Linkedin Profile Optimizer support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Linkedin Profile Optimizer or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 88. linkedin-strategy
- **purpose**: Builds LinkedIn personal brand strategy with posting schedule, content themes, engagement tactics, and connection outreach. Use when growing your professional presence and generating leads on LinkedIn.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete linkedin strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Linkedin Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Linkedin Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 89. listicle-generator
- **purpose**: Creates engaging listicle articles with consistent entry structure, examples, and SEO optimization. Use when writing numbered list posts like 'Top 10' or 'Best X for Y' articles.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete listicle generator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Listicle Generator support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Listicle Generator or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 90. local-seo-plan
- **purpose**: Creates local SEO strategies with Google Business Profile optimization, citation building, and review generation. Use when improving visibility for local searches.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete local seo plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 91. lookalike-audience-plan
- **purpose**: Designs lookalike audience strategies with source audience selection, percentage tiers, and testing framework. Use when planning paid ad targeting to find new customers similar to your best existing ones.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete lookalike audience plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Lookalike Audience Plan support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Lookalike Audience Plan or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 92. loyalty-program
- **purpose**: Designs customer loyalty and rewards programs with tier structures, earning rules, redemption options, and promotional launch messaging. Use when a user wants to increase repeat purchases, reduce churn, reward their best customers, or build a membership-style retention system.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete loyalty program document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Loyalty Program support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Loyalty Program or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 93. market-research
- **purpose**: Conducts market sizing, trend analysis, audience segmentation, and opportunity assessment for business ideas and products. Use when a user is validating a new business idea, entering a new market, preparing a pitch deck, or needs data to support strategic decisions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete market research document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Market Research support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Market Research or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 94. market-sizing
- **purpose**: Estimates TAM, SAM, and SOM with top-down and bottom-up methodologies, assumptions documentation, and presentation-ready outputs. Use for business plans or investor pitches.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete market sizing document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Market Sizing support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Market Sizing or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 95. marketing-guru-aggent
- **purpose**: Marketing Guru Aggent — Professional-grade marketing skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete marketing guru aggent document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Marketing Guru Aggent support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Marketing Guru Aggent or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 96. marketing-skills
- **purpose**: Full-stack marketing intelligence collection. Routes any marketing task to the most
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete marketing skills document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Marketing Skills support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Marketing Skills or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 97. marketplace-fee-structure
- **purpose**: Designs marketplace fee structures with commission models, premium tiers, and competitive analysis. Use when setting or restructuring pricing for a platform business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete marketplace fee structure document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Marketplace Fee Structure support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Marketplace Fee Structure or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 98. marketplace-launch-plan
- **purpose**: Plans two-sided marketplace launches with supply/demand seeding, trust-building features, and growth mechanics. Use when launching a platform connecting buyers and sellers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete marketplace launch plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Marketplace Launch Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Marketplace Launch Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 99. marketplace-listing
- **purpose**: Optimizes marketplace listings for Etsy, Amazon, eBay with platform-specific SEO, pricing, and imagery guidelines.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete marketplace listing document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Marketplace Listing support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Marketplace Listing or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 100. marketplace-metrics
- **purpose**: Defines and tracks marketplace health metrics including liquidity, take rate, GMV, and supply/demand balance. Use when measuring and optimizing marketplace performance.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete marketplace metrics document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Marketplace Metrics support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Marketplace Metrics or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 101. marketplace-seo
- **purpose**: Plans SEO strategies for marketplace platforms with category page optimization, review schema, and internal linking. Use when driving organic traffic to a marketplace.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete marketplace seo document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 102. mastermind-group
- **purpose**: Designs mastermind group structures with member selection, meeting formats, hot seat protocols, and accountability systems.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete mastermind group document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Mastermind Group support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Mastermind Group or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 103. media-buy-plan
- **purpose**: Plans paid media budgets across channels with allocation strategy, expected ROAS, and testing roadmap. Use when managing ad spend across multiple platforms.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete media buy plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Media Buy Plan support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Media Buy Plan or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 104. media-kit
- **purpose**: Builds influencer and creator media kits with audience stats, collaboration options, rate cards, and brand alignment sections. Use when a user wants to pitch brand partnerships, needs a professional document to share with sponsors, or is monetizing their content through collaborations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete media kit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Media Kit support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Media Kit or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 105. meeting-agenda
- **purpose**: Builds structured meeting agendas with time allocations, discussion topics, decision items, and action item templates for productive meetings.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete meeting agenda document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Meeting Agenda support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Meeting Agenda or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 106. meeting-notes
- **purpose**: Transforms raw meeting notes or transcripts into structured Notion pages with executive summary, key decisions, action items with owners and deadlines, and open questions. Use when a user has messy meeting notes, a transcript, or bullet points from a call and needs them organized into an actionable format in Notion.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete meeting notes document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Meeting Notes support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Meeting Notes or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 107. membership-site-plan
- **purpose**: Plans membership site content libraries, tier structures, pricing, drip schedules, and retention strategies. Use this skill when a creator or coach wants to build recurring revenue through a membership model, needs to design tier levels, or is planning content delivery for a subscription community.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete membership site plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Membership Site Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Membership Site Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 108. meme-content-brief
- **purpose**: Creates branded meme content briefs with cultural references, brand alignment guidelines, and format templates. Use when incorporating memes into your social media content strategy.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete meme content brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Meme Content Brief support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Meme Content Brief or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 109. mentorship-program
- **purpose**: Designs mentorship programs with matching criteria, meeting structures, goal frameworks, and progress tracking.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete mentorship program document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Mentorship Program support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Mentorship Program or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 110. menu-design-brief
- **purpose**: Creates restaurant menu design briefs with item descriptions, pricing psychology, layout hierarchy, and dietary labeling. Use when designing or redesigning a restaurant menu.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete menu design brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Menu Design Brief support under the Food & Restaurant domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Menu Design Brief or when more specialized Food & Restaurant tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 111. merch-design-brief
- **purpose**: Creates merchandise design briefs for branded swag with product selection, design placement, vendor specs, and budget planning. Use when producing branded merchandise.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete merch design brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Merch Design Brief support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Merch Design Brief or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 112. meta-ads
- **purpose**: Meta Ads API for Facebook/Instagram advertising. Use when user mentions
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete meta ads document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Meta Ads support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Meta Ads or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 113. meta-tag-optimizer
- **purpose**: Optimizes title tags and meta descriptions for a batch of pages with character counts and CTR optimization. Use when improving your site's search appearance.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete meta tag optimizer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 114. metric-definition-guide
- **purpose**: Creates metric glossaries defining how each business KPI is calculated, tracked, and interpreted with formulas, data sources, and ownership. Use for team alignment on numbers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete metric definition guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Metric Definition Guide support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Metric Definition Guide or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 115. micro-course
- **purpose**: Creates bite-sized micro-courses under 30 minutes with focused learning objectives and immediate application exercises.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete micro course document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Micro Course support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Micro Course or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 116. microcopy-writer
- **purpose**: Writes UX microcopy for buttons, tooltips, error messages, empty states, and onboarding flows. Use when you need clear, human interface text that guides users through your product.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete microcopy writer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Microcopy Writer support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Microcopy Writer or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 117. milestone-email
- **purpose**: Creates automated milestone celebration emails for anniversaries, purchase counts, and achievements to boost customer retention and loyalty.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete milestone email document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 118. mission-statement
- **purpose**: Crafts organization mission, vision, and values statements with stakeholder input process and alignment exercises.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete mission statement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Mission Statement support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Mission Statement or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 119. morning-routine-builder
- **purpose**: Designs personalized morning routines for entrepreneurs with time blocks, habits, and productivity triggers tailored to energy levels and business goals.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete morning routine builder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Morning Routine Builder support under the Health & Wellness domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Morning Routine Builder or when more specialized Health & Wellness tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 120. naming-workshop
- **purpose**: Facilitates business or product naming with brainstorming frameworks, evaluation criteria, domain checks, and trademark considerations. Use when naming anything new.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete naming workshop document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Naming Workshop support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Naming Workshop or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 121. nda-template
- **purpose**: Generates mutual and unilateral NDA templates with customizable confidentiality terms, exclusions, and duration. Use this skill when a user needs a non-disclosure agreement for sharing sensitive information with potential partners, contractors, investors, or collaborators.
- **inputs**:
- `party_a` (string, required): First party (disclosing party)
- `party_b` (string, required): Second party (receiving party)
- `purpose` (string, required): Purpose of disclosure
- `nda_type` (string, required): Type: mutual|one-way
- `duration` (string, optional): Confidentiality duration (e.g., 2 years)
- `jurisdiction` (string, optional): Governing law jurisdiction
- **outputs**:
- `nda_document` (string): Complete NDA agreement
- `key_clauses` (array): Key clauses and their purposes
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 122. neighborhood-guide
- **purpose**: Writes neighborhood guides with local amenities, schools, transportation, demographics, and lifestyle descriptions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete neighborhood guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When writing high-converting property listings, building neighborhood guides, or analyzing rental property ROIs.
- **avoid when**: When drafting general technology software documentation or engineering cloud pipelines.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 123. networking-event-plan
- **purpose**: Plans networking events with icebreaker activities, facilitation guides, and connection-making structures.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete networking event plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Networking Event Plan support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Networking Event Plan or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 124. networking-strategy
- **purpose**: Creates strategic networking plans with target contacts, outreach templates, relationship nurture sequences, and event calendar.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete networking strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Networking Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Networking Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 125. newsletter-builder
- **purpose**: Creates complete newsletters from editorial brief to final visual layout, planning content in Notion and generating the designed version in Canva. Use when a user needs to produce a recurring newsletter issue, build a newsletter from scratch, or transform raw ideas into a polished send-ready newsletter.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete newsletter builder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Newsletter Builder support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Newsletter Builder or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 126. newsletter-strategy
- **purpose**: Plans newsletter cadence, content themes, growth tactics, and monetization strategy for email publications. Use when launching or restructuring an email newsletter for your business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete newsletter strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Newsletter Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Newsletter Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 127. no-code-app-plan
- **purpose**: Plans no-code application builds with tool selection, feature mapping, and user flow design. Use when building apps or tools without writing code.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete no code app plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic No Code App Plan support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to No Code App Plan or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 128. non-compete-agreement
- **purpose**: Creates non-compete agreements with reasonable scope, duration, geographic limits, and enforceability notes. Use when protecting business interests from competition.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete non compete agreement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 129. nonprofit-board-packet
- **purpose**: Creates board meeting packets with agenda, financial summaries, program updates, and vote items for nonprofit governance.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete nonprofit board packet document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Nonprofit Board Packet support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Nonprofit Board Packet or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 130. nonprofit-fundraising-letter
- **purpose**: Writes fundraising appeal letters with storytelling, impact data, donation asks, and follow-up sequences.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete nonprofit fundraising letter document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Nonprofit Fundraising Letter support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Nonprofit Fundraising Letter or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 131. nps-survey
- **purpose**: Creates Net Promoter Score surveys with follow-up questions, segmentation logic, and response action plans to measure customer loyalty.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete nps survey document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Nps Survey support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Nps Survey or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 132. nutrition-content-plan
- **purpose**: Creates nutrition-focused content plans with topic ideas, recipe structures, and disclaimer templates for wellness brands.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete nutrition content plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Nutrition Content Plan support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Nutrition Content Plan or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 133. objection-handler
- **purpose**: Builds sales objection response playbooks with rebuttals organized by objection category, empathetic acknowledgments, and reframing techniques. Use when a user keeps hearing the same objections on sales calls, wants to train a team on handling pushback, or needs confidence dealing with price, timing, and trust concerns.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete objection handler document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 134. offboarding-checklist
- **purpose**: Creates offboarding procedures with access revocation, knowledge transfer, equipment return, and exit interview templates for clean transitions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete offboarding checklist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Offboarding Checklist support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Offboarding Checklist or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 135. offer-letter
- **purpose**: Drafts employment offer letters with position details, compensation, benefits, start date, and key terms for professional hiring communication.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete offer letter document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Offer Letter support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Offer Letter or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 136. offer-strategy-architect
- **purpose**: Shape offers, pricing presentation, conversion paths, CTA structures, urgency logic, page strategy, and product packaging. Use proactively whenever a user needs help with offer design, pricing strategy, CTA hierarchy, urgency mechanics, page strategy, checkout optimization, or packaging of products and programs. Best for LMS, education, e-commerce, consulting, and lead-to-purchase businesses. Trigger on offer strategy, pricing, CTA, urgency, checkout, packaging, conversion path, or objection handling.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete offer strategy architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Offer Strategy Architect support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Offer Strategy Architect or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 137. okr-builder
- **purpose**: Creates OKR frameworks with objective setting, key result definition, scoring rubrics, and progress tracking for goal-driven businesses.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete okr builder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Okr Builder support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Okr Builder or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 138. onboarding-checklist
- **purpose**: Creates employee or contractor onboarding checklists with day-by-day tasks, tool access setup, and training schedules for smooth starts.
- **inputs**:
- `role_type` (string, required): Role being onboarded: employee|contractor|client|vendor
- `company_name` (string, required): Company name
- `duration` (string, optional): Onboarding duration: 30-day|60-day|90-day
- `department` (string, optional): Department or team
- `tools_used` (array, optional): Tools the new person needs access to
- **outputs**:
- `onboarding_checklist` (array): Day-by-day onboarding checklist
- `welcome_message` (string): Welcome email template
- `resources_list` (array): Resources and links to share
- **best used when**: When requiring strategic Onboarding Checklist support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Onboarding Checklist or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 139. onboarding-flow
- **purpose**: Designs customer onboarding flows with welcome steps, milestone triggers, and success checkpoints to reduce churn and speed time-to-value.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete onboarding flow document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Onboarding Flow support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Onboarding Flow or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 140. one-on-one-template
- **purpose**: Designs 1:1 meeting templates with check-in questions, career development discussion, and action items for effective manager conversations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete one on one template document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic One On One Template support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to One On One Template or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 141. open-house-plan
- **purpose**: Plans open house events with preparation checklist, visitor registration, follow-up sequences, and feedback collection.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete open house plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When writing high-converting property listings, building neighborhood guides, or analyzing rental property ROIs.
- **avoid when**: When drafting general technology software documentation or engineering cloud pipelines.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 142. order-bump-copy
- **purpose**: Writes order bump offers for checkout pages with benefit-focused copy and pricing psychology. Use when you need to increase average order value at checkout.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete order bump copy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 143. packaging-brief
- **purpose**: Writes product packaging design briefs with dimensions, material considerations, messaging hierarchy, compliance requirements, and vendor specs. Use when designing physical packaging.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete packaging brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Packaging Brief support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Packaging Brief or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 144. page-cro
- **purpose**: When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete page cro document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Page Cro support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Page Cro or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 145. paid-media-plan-architect
- **purpose**: لعمل media plans أقوى، أسرع، وأوضح. يساعد فريق الإعلانات يبني خطة مفهومة بالأرقام، الجمهور، القنوات، الرسائل، والميزانية
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete paid media plan architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Paid Media Plan Architect support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Paid Media Plan Architect or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**:
  - primary_output
  - summary
  - next_steps

#### 146. paid-media-plan-pack
- **purpose**: Use when the user needs paid media planning, acquisition strategy, funnel design, campaign architecture, budget allocation, active campaign decisions, creative scaling, benchmark refresh, performance reporting from ad data, MCP feeds, or a logic layer for AI tools. Supports planning prompts such as “media plan”, “paid ads strategy”, “خطة إعلانات”; reporting prompts such as “analyze ad data”, “performance report”, “حلل بيانات الإعلانات”; decision prompts such as “pause or scale”, “أوقف إيه وأزود
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete paid media plan pack document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Paid Media Plan Pack support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Paid Media Plan Pack or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 147. partnership-agreement
- **purpose**: Drafts business partnership agreements with roles, profit sharing, decision-making, and exit provisions. Use when forming a business partnership or joint venture.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete partnership agreement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 148. partnership-proposal
- **purpose**: Creates strategic partnership pitch documents with mutual value propositions, deal structures, and terms. Use this skill when a user wants to propose a joint venture, co-marketing deal, revenue share, or strategic alliance to another business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete partnership proposal document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Partnership Proposal support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Partnership Proposal or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 149. payment-plan-offer
- **purpose**: Designs payment plan structures with terms, messaging, and implementation guidelines. Use when you want to offer installment pricing to increase conversions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete payment plan offer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 150. payment-terms-policy
- **purpose**: Creates payment terms and collections policies with net terms, late fee structures, and escalation procedures. Use when establishing how and when clients must pay.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete payment terms policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 151. performance-analyst
- **purpose**: للتقارير، قراءة الأرقام، استخراج insights قابلة للتنفيذ، وتحويل البيانات إلى قرارات مفهومة للفريق والعميل
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete performance analyst document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Performance Analyst support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Performance Analyst or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 152. performance-report
- **purpose**: Build a marketing performance report with key metrics, trend analysis, wins and misses, and prioritized optimization recommendations. Use when wrapping a campaign, when preparing weekly, monthly, or quarterly channel summaries for stakeholders, or when you need data translated into an executive summary with next-period priorities.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete performance report document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Performance Report support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Performance Report or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**:
  - primary_output
  - summary
  - next_steps

#### 153. performance-review
- **purpose**: Builds performance review templates with self-assessment sections, manager feedback, goal setting, and development planning for team growth.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete performance review document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Performance Review support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Performance Review or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 154. personal-brand-strategy
- **purpose**: Creates personal branding strategies with positioning, platform selection, content pillars, and visibility plan.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete personal brand strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Personal Brand Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Personal Brand Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 155. pillar-page
- **purpose**: Creates comprehensive pillar pages (3,000+ words) that serve as content hubs linking to related cluster content. Use when building an SEO topic cluster strategy with a cornerstone page.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete pillar page document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 156. pinterest-strategy
- **purpose**: Develops Pinterest marketing plans with board structures, pin templates, keyword research, and scheduling cadence. Use when leveraging Pinterest as a search-driven traffic source for your business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete pinterest strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Pinterest Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Pinterest Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 157. pip-template
- **purpose**: Creates performance improvement plan templates with specific goals, timeline, resources, and consequences for underperforming team members.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete pip template document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Pip Template support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Pip Template or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 158. pitch-deck
- **purpose**: Creates professional investor or client pitch decks in Canva from a conversational brief about the business, product, or service. Use when a user needs a presentation for fundraising, client proposals, partnership pitches, or keynote talks.
- **inputs**:
- `company_name` (string, required): Company name
- `one_liner` (string, required): One-sentence description
- `problem` (string, required): Problem being solved
- `solution` (string, required): Your solution
- `market_size` (string, required): Total addressable market
- `revenue_model` (string, required): How you make money
- `traction` (string, optional): Current traction and metrics
- `team` (array, optional): Key team members
- `ask` (string, optional): Funding amount and use of funds
- **outputs**:
- `slide_outline` (array): Slide-by-slide outline with content
- `key_narratives` (object): Core story arcs for each section
- `data_to_source` (array): Data and stats needed to complete deck
- **best used when**: When requiring strategic Pitch Deck support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Pitch Deck or when more specialized Strategy & Planning tools are available.
- **example prompt**: "Execute PrePilot task for 'Pitch Deck' (ID: pitch-deck) to generate a premium strategic deliverable with inputs: company_name='Standard company_name brief', one_liner='Standard one_liner brief', problem='Standard problem brief', solution='Standard solution brief', market_size='Standard market_size brief', revenue_model='Standard revenue_model brief'."
- **expected result**: 
```json
{
  "slide_outline": [
    "Validated slide_outline milestone 1",
    "Validated slide_outline milestone 2"
  ],
  "key_narratives": {
    "status": "APPROVED",
    "score": 95,
    "remarks": "This generated key_narratives satisfies all professional-tier constraints."
  },
  "data_to_source": [
    "Validated data_to_source milestone 1",
    "Validated data_to_source milestone 2"
  ]
}
```

#### 159. pitch-deck-architect
- **purpose**: للعروض البيعية، pitch decks، RFP responses، وترتيب القصة التجارية بصرياً ومنطقياً
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete pitch deck architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Pitch Deck Architect support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Pitch Deck Architect or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 160. planning-analyst
- **purpose**: This skill was automatically generated from the `plans` infrastructure directory.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete planning analyst document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Planning Analyst support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Planning Analyst or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 161. platform-community-guidelines
- **purpose**: Writes platform community guidelines with acceptable use, content policies, and enforcement procedures. Use when establishing rules for marketplace or community platforms.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete platform community guidelines document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Platform Community Guidelines support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Platform Community Guidelines or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 162. platform-help-center
- **purpose**: Structures platform help centers with separate buyer/seller sections, video tutorials, and contact escalation. Use when building self-serve support for marketplace platforms.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete platform help center document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Platform Help Center support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Platform Help Center or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 163. platform-migration
- **purpose**: Plans social media platform migrations with audience notification sequences, content transfer strategies, and timeline. Use when moving your audience from one platform to another.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete platform migration document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Platform Migration support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Platform Migration or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 164. platform-partnership
- **purpose**: Designs platform partnership programs with integration benefits, co-marketing, and revenue sharing. Use when building strategic partnerships for marketplace or SaaS platforms.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete platform partnership document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Platform Partnership support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Platform Partnership or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 165. platform-trust-system
- **purpose**: Designs trust and safety systems with review policies, dispute resolution, and fraud prevention measures. Use when building trust infrastructure for marketplace platforms.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete platform trust system document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Platform Trust System support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Platform Trust System or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 166. pm-skills-main
- **purpose**: Pm Skills Main — Professional-grade general skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete pm skills main document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Pm Skills Main support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Pm Skills Main or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 167. podcast-ad-script
- **purpose**: Writes host-read and pre-produced podcast ad scripts with natural integration points and tracking URLs. Use when creating podcast advertising spots or sponsorship reads.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete podcast ad script document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Podcast Ad Script support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Podcast Ad Script or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 168. podcast-guest-pitch
- **purpose**: Writes podcast guest pitches with topic angles, talking points, audience alignment, and one-sheet creation.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete podcast guest pitch document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Podcast Guest Pitch support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Podcast Guest Pitch or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 169. podcast-launch
- **purpose**: Plans podcast launches from concept and format through branding, equipment recommendations, and first 5 episode outlines. Use when a user wants to start a podcast, needs to plan their show format and content strategy, or is ready to launch but doesn't know where to begin.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete podcast launch document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Podcast Launch support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Podcast Launch or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 170. podcast-one-sheet
- **purpose**: Creates podcast one-sheets for guest bookings with show description, host bio, audience stats, and sponsorship rates. Use when pitching sponsors or recruiting high-profile guests.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete podcast one sheet document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Podcast One Sheet support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Podcast One Sheet or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 171. podcast-show-notes
- **purpose**: Transforms podcast or video transcripts into structured show notes with timestamps, key takeaways, resource links, guest bios, pull quotes, and SEO-optimized episode descriptions. Use when a user has a transcript or recording summary and needs polished show notes for their podcast episode page.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete podcast show notes document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Podcast Show Notes support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Podcast Show Notes or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 172. portfolio-page
- **purpose**: Writes compelling portfolio page copy with project descriptions, results, testimonials, and CTAs for freelancers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete portfolio page document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Portfolio Page support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Portfolio Page or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 173. pr-crisis-expert
- **purpose**: للـ press materials، البيانات الرسمية، إدارة السمعة، وتجهيز ردود هادئة وقت المواقف الحساسة
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete pr crisis expert document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Pr Crisis Expert support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Pr Crisis Expert or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 174. pr-pitch
- **purpose**: Writes media pitches to journalists with compelling angles, hooks, supporting data, and follow-up sequences. Use when a user has a newsworthy story, is launching a product, reaching a milestone, or wants to get featured in publications and podcasts.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete pr pitch document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Pr Pitch support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Pr Pitch or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 175. prepilot-landing-page-generator
- **purpose**: Generate Claude-ready, conversion-focused, interactive SaaS landing pages using the PrePilot page architecture, tracking model, WhatsApp handoff, checkout flow, RTL UI rules, and QA gates.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete prepilot landing page generator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 176. prepilot-partner-card-funnel-strategist
- **purpose**: Build, audit, refine, or implement the PrePilot Partner Card sample-to-paid funnel. Use for PrePilot Partner Card, 14$ card, 79$ product, media buyers, free sample, 5 of 17 media plan sections, tripwire funnel, endowed progress, landing page, ad copy, email sequence, retargeting, Meta Pixel, CAPI, WhatsApp payment, Instapay, VF Cash, Barq, tracking, KPIs, or funnel audit tasks.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete prepilot partner card funnel strategist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 177. presentation-template-guide
- **purpose**: Creates brand-aligned presentation template guidelines with slide layouts, color usage, font hierarchies, and do's and don'ts. Use when standardizing team presentations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete presentation template guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Presentation Template Guide support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Presentation Template Guide or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 178. press-kit
- **purpose**: Creates comprehensive press kits with company backgrounder, founder bio, high-res assets, fact sheets, and media contacts. Use when preparing for media outreach or PR campaigns.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete press kit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Press Kit support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Press Kit or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 179. press-release
- **purpose**: Writes professional press releases following AP style with headline, dateline, lead paragraph, body, boilerplate, and media contact sections. Use when a user is launching a product, announcing a milestone, making a hire, forming a partnership, or has any newsworthy event to share with media outlets.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete press release document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Press Release support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Press Release or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 180. price-increase-notice
- **purpose**: Writes price increase announcements with justification, grandfather clauses, and urgency elements. Use when raising prices on existing products or services.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete price increase notice document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Price Increase Notice support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Price Increase Notice or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 181. pricing-analysis
- **purpose**: Analyzes pricing effectiveness with elasticity estimates, competitor benchmarking, value perception, and optimization recommendations. Use when evaluating or adjusting your pricing.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete pricing analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Pricing Analysis support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Pricing Analysis or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 182. pricing-calculator
- **purpose**: Builds pricing models, comparison tables, and rate calculators for services, products, and subscriptions with profit margin analysis and competitive positioning. Use when a user needs to set prices for their offerings, wants to create tiered pricing, or needs to calculate freelance rates, project fees, or subscription pricing.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete pricing calculator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Pricing Calculator support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Pricing Calculator or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 183. pricing-page-copy
- **purpose**: Writes SaaS pricing page copy with tier descriptions, feature comparisons, and objection-handling FAQ. Use when launching or redesigning a pricing page.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete pricing page copy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Pricing Page Copy support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Pricing Page Copy or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 184. pricing-strategy
- **purpose**: Develops pricing strategies with market positioning, perceived value analysis, and price sensitivity testing. Use when setting or revising prices for products or services.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete pricing strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Pricing Strategy support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Pricing Strategy or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 185. privacy-policy
- **purpose**: Writes GDPR and CCPA-compliant privacy policies for websites, apps, and online businesses with plain-language annotations explaining each section. Use when a user is launching a website, setting up e-commerce, collecting customer data, or needs to update an outdated privacy policy.
- **inputs**:
- `business_name` (string, required): Legal business name
- `website_url` (string, required): Website URL
- `data_collected` (array, required): Types of data collected (email, name, payment, etc.)
- `country` (string, required): Country of operation (affects GDPR, CCPA, etc.)
- `third_party_tools` (array, optional): Third-party tools used (GA, Stripe, Mailchimp, etc.)
- `audience_minors` (boolean, optional): Does site target users under 13?
- **outputs**:
- `privacy_policy` (string): Complete Privacy Policy document
- `compliance_notes` (array): Specific compliance requirements noted
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 186. process-automation-audit
- **purpose**: Identifies automation opportunities in business processes with tool recommendations, ROI estimates, and implementation priority rankings.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete process automation audit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Process Automation Audit support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Process Automation Audit or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 187. product-changelog
- **purpose**: Creates product changelog formats with version notes, categorization (new, improved, fixed), and user-friendly language. Use when documenting product updates for users.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product changelog document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product Changelog support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Changelog or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 188. product-comparison
- **purpose**: Creates product comparison pages with feature matrices, pros/cons, and recommendation logic. Use this skill when a user needs to create comparison content for their website, sales materials, landing page, or blog post that helps buyers evaluate options and make confident purchase decisions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product comparison document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product Comparison support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Comparison or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 189. product-description
- **purpose**: Writes conversion-optimized product descriptions for e-commerce platforms with benefit-driven copy, SEO keywords, and platform-specific formatting for Shopify, Amazon, Etsy, and WooCommerce. Use when a user needs product listings, wants to improve existing product copy, or is launching products on an e-commerce platform.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product description document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product Description support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Description or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 190. product-faq
- **purpose**: Generates product-specific FAQ sections addressing common pre-purchase questions, objections, and concerns to increase conversion rates. Use when reducing buyer hesitation.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product faq document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product Faq support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Faq or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 191. product-feedback-loop
- **purpose**: Designs product feedback loops connecting customer input to product decisions with transparency and communication. Use when systematizing how feedback drives your roadmap.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product feedback loop document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product Feedback Loop support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Feedback Loop or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 192. product-hunt-launch
- **purpose**: Plans Product Hunt launches with teaser strategy, maker comments, upvote coordination, and post-launch follow-up. Use when launching a product on Product Hunt.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product hunt launch document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product Hunt Launch support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Hunt Launch or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 193. product-launch-email
- **purpose**: Writes a high-converting product launch email with subject line variants, preview text, and segmentation notes. Use when announcing a new product, feature, or offer to your email list.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product launch email document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 194. product-launch-plan
- **purpose**: Plans product launches with teaser campaigns, launch day tactics, and post-launch optimization for existing e-commerce stores.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product launch plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product Launch Plan support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Launch Plan or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps


### Chunk 3 Skills Index

#### 1. product-listing-optimizer
- **purpose**: Optimizes e-commerce product listings with titles, bullet points, descriptions, backend keywords, and images for Amazon, Shopify, and other platforms. Use to increase conversions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product listing optimizer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product Listing Optimizer support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Listing Optimizer or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 2. product-photography-brief
- **purpose**: Creates e-commerce product photography shot lists with angles, lighting notes, and styling direction. Use this skill when a user needs to prepare for product photos, brief a photographer for e-commerce images, or plan product shots that drive conversions for their online store.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product photography brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product Photography Brief support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Photography Brief or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 3. product-recall-plan
- **purpose**: Creates product recall communication plans with customer notification, return procedures, and reputation management strategies.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product recall plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product Recall Plan support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Recall Plan or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 4. product-roadmap
- **purpose**: Creates product roadmaps in Notion with milestones, feature priorities, release timelines, and status tracking for SaaS products, apps, courses, or any product with iterative development. Use when a user needs to plan product development, wants to communicate a roadmap to stakeholders, or needs to prioritize features for upcoming releases.
- **inputs**:
- `product_name` (string, required): Product name
- `current_stage` (string, required): Stage: idea|mvp|growth|scale
- `goals` (array, required): Strategic product goals
- `features_backlog` (array, optional): Existing feature backlog
- `resources` (string, optional): Team size and available resources
- `timeframe` (string, optional): Roadmap timeframe: 6-months|1-year|18-months
- **outputs**:
- `roadmap` (array): Quarterly roadmap with themes and features
- `prioritization_matrix` (object): Feature priority matrix
- `milestones` (array): Key milestones and success criteria
- **best used when**: When requiring strategic Product Roadmap support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Roadmap or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 5. product-sourcing-brief
- **purpose**: Writes product sourcing briefs with specifications, quality requirements, MOQs, supplier evaluation criteria, and negotiation guidelines. Use when finding manufacturers for a product.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete product sourcing brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Product Sourcing Brief support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Product Sourcing Brief or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 6. professional-bio
- **purpose**: Writes professional bios in multiple lengths for different platforms and contexts with consistent personal branding.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete professional bio document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Professional Bio support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Professional Bio or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 7. profit-loss-report
- **purpose**: Generates monthly or quarterly profit and loss statements from transaction data with revenue breakdowns, expense categories, and margin analysis. Use this skill when a solopreneur or small business owner needs to understand if they are actually profitable, wants a formatted P&L report, or needs to review financial performance over a period.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete profit loss report document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Profit Loss Report support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Profit Loss Report or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 8. project-scope-change
- **purpose**: Writes scope change request documents with impact assessment, revised timeline, and cost adjustments for client projects.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete project scope change document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Project Scope Change support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Project Scope Change or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 9. project-tracker
- **purpose**: Creates a project management database in Notion with tasks, statuses, owners, due dates, and priorities, pre-populated from a project brief or scope document. Use when a user needs to set up project tracking for a new engagement, wants to replace spreadsheet-based task management, or needs a lightweight PM system without paid software.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete project tracker document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Project Tracker support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Project Tracker or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 10. prompt-library
- **purpose**: Organizes and documents reusable prompt libraries with categories, variables, and quality scoring. Use when building a structured collection of AI prompts for your business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete prompt library document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Prompt Library support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Prompt Library or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 11. prompt-master
- **purpose**: Generates optimized prompts for AI tools. Activates only when the user explicitly asks to write, fix, improve, or adapt a prompt for a specific AI tool (LLM, Cursor, Midjourney, image AI, video AI, coding agents, etc.). Does not activate for general conversation, coding tasks, document writing, or other non-prompt-engineering work.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete prompt master document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Prompt Master support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Prompt Master or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 12. prompt-master-main
- **purpose**: Generates optimized prompts for AI tools. Activates only when the user explicitly asks to write, fix, improve, or adapt a prompt for a specific AI tool (LLM, Cursor, Midjourney, image AI, video AI, coding agents, etc.). Does not activate for general conversation, coding tasks, document writing, or other non-prompt-engineering work.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete prompt master main document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Prompt Master Main support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Prompt Master Main or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 13. property-listing
- **purpose**: Writes compelling property listing descriptions with features, neighborhood highlights, and buyer-targeted copy.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete property listing document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When writing high-converting property listings, building neighborhood guides, or analyzing rental property ROIs.
- **avoid when**: When drafting general technology software documentation or engineering cloud pipelines.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 14. property-management-sop
- **purpose**: Builds property management SOPs for maintenance requests, inspections, rent collection, and tenant communication.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete property management sop document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Property Management Sop support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Property Management Sop or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 15. proposal-writer
- **purpose**: Generates complete client proposals from a conversational scope discussion, producing a professional document with executive summary, problem statement, proposed solution, deliverables, pricing, timeline, and terms. Use when a user needs to send a proposal to a prospect, formalize a project scope, or respond to an RFP.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete proposal writer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Proposal Writer support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Proposal Writer or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**:
  - primary_output
  - summary
  - next_steps

#### 16. proposals-specialist
- **purpose**: للعروض الفنية والمالية، ترتيب الأفكار، صياغة الحل، وتحويل المتطلبات إلى proposal واضح ومقنع
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete proposals specialist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Proposals Specialist support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Proposals Specialist or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 17. quality-assurance-checklist
- **purpose**: Creates QA checklists for products, services, or content with pass/fail criteria, review workflows, and quality standards documentation.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete quality assurance checklist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Quality Assurance Checklist support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Quality Assurance Checklist or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 18. quarterly-review
- **purpose**: Creates quarterly business review documents with metric analysis, goal tracking, and strategic adjustments. Use when conducting end-of-quarter business performance reviews.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete quarterly review document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Quarterly Review support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Quarterly Review or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 19. quiz-generator
- **purpose**: Generates quizzes and assessments with multiple choice, true/false, and short answer questions with answer keys.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete quiz generator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Quiz Generator support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Quiz Generator or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 20. rate-negotiation-script
- **purpose**: Creates rate negotiation scripts for freelancers and consultants with value anchoring and objection responses.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete rate negotiation script document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 21. re-engagement-email
- **purpose**: Creates re-engagement campaigns for dormant subscribers with segmentation rules and sunset policy. Use when cleaning your email list and winning back inactive subscribers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete re engagement email document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 22. real-estate-crm-setup
- **purpose**: Sets up real estate CRM systems with pipeline stages, lead scoring, and automated follow-up sequences.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete real estate crm setup document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When writing high-converting property listings, building neighborhood guides, or analyzing rental property ROIs.
- **avoid when**: When drafting general technology software documentation or engineering cloud pipelines.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 23. real-estate-newsletter
- **purpose**: Creates real estate market update newsletters with local data analysis, buying/selling tips, and featured listings.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete real estate newsletter document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Real Estate Newsletter support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Real Estate Newsletter or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 24. realtime_research
- **purpose**: Binding methodology for real-time web search and social listening. Uses a strict-rules engine to run targeted multi-platform searches (Reddit, Hacker News, X/Twitter, YouTube) over the last 30 days. Use whenever a user asks about latest trends, what people are saying, news, sentiment, or comparisons. Trigger on: "what are people saying about", "latest on", "trends in", "compare", "sentiment", "آخر أخبار", "ما رأي الناس في", "ابحث عن".
- **inputs**:
- `query` (string, required): The topic, person, product, or comparison to research
- `query_type` (string, optional): One of: GENERAL, NEWS, RECOMMENDATIONS, COMPARISON, PROMPTING
- **outputs**:
- `findings` (string): Synthesized research findings with inline citations
- `key_patterns` (array): Numbered list of core trends from the research
- **best used when**: When requiring strategic Real-Time Research & Social Listening support under the Research & Intelligence domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Real-Time Research & Social Listening or when more specialized Research & Intelligence tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 25. rebrand-plan
- **purpose**: Plans brand refreshes and full rebrands with phased rollout, stakeholder communication, asset transition checklists, and timeline management. Use when evolving your brand identity.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete rebrand plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Rebrand Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Rebrand Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 26. recipe-card
- **purpose**: Creates professional recipe cards with ingredient lists, step-by-step instructions, and scaling calculations. Use when documenting recipes for customers, content, or operations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete recipe card document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Recipe Card support under the Food & Restaurant domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Recipe Card or when more specialized Food & Restaurant tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 27. reddit-strategy
- **purpose**: Creates Reddit engagement plans with subreddit targeting, value-first posting guidelines, and community building tactics. Use when leveraging Reddit for traffic, research, or brand visibility.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete reddit strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Reddit Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Reddit Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 28. referral-bonus-plan
- **purpose**: Designs employee referral bonus programs with incentive tiers, eligibility rules, payout timelines, and tracking systems. Use when building a referral-based hiring pipeline.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete referral bonus plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Referral Bonus Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Referral Bonus Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 29. referral-program
- **purpose**: Designs customer referral systems with incentive tiers, tracking mechanisms, and promotional messaging. Use when a user wants to grow through word-of-mouth, needs a structured refer-a-friend program, or wants to reward existing customers for bringing in new business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete referral program document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Referral Program support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Referral Program or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 30. release-notes
- **purpose**: Writes user-friendly release notes with categorized changes, migration guides, and known issues. Use when communicating software updates to users and stakeholders.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete release notes document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Release Notes support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Release Notes or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 31. remote-team-handbook
- **purpose**: Writes handbooks for remote teams covering tools, communication norms, time zones, async practices, and collaboration guidelines. Use when building or scaling a distributed team.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete remote team handbook document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Remote Team Handbook support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Remote Team Handbook or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 32. remote-work-policy
- **purpose**: Creates comprehensive remote work policies with expectations, tools, communication norms, and performance standards for distributed teams.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete remote work policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 33. renewal-campaign
- **purpose**: Builds subscription renewal campaigns with reminder sequences, incentives, and save offers. Use when reducing churn and increasing subscription retention rates.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete renewal campaign document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Renewal Campaign support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Renewal Campaign or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 34. rental-listing
- **purpose**: Writes rental property listings with amenity highlights, qualification requirements, and application instructions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete rental listing document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When writing high-converting property listings, building neighborhood guides, or analyzing rental property ROIs.
- **avoid when**: When drafting general technology software documentation or engineering cloud pipelines.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 35. report-automation
- **purpose**: Designs automated reporting workflows with data sources, schedules, distribution lists, and template standardization. Use when eliminating manual reporting work.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete report automation document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Report Automation support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Report Automation or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 36. restaurant-marketing-plan
- **purpose**: Plans restaurant marketing with local SEO, social media content, loyalty programs, and seasonal promotions. Use when growing a restaurant's customer base and revenue.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete restaurant marketing plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Restaurant Marketing Plan support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Restaurant Marketing Plan or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 37. restaurant-review-response
- **purpose**: Writes professional restaurant review responses for positive, negative, and mixed reviews across platforms. Use when managing online reputation for a food business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete restaurant review response document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Restaurant Review Response support under the Food & Restaurant domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Restaurant Review Response or when more specialized Food & Restaurant tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 38. restaurant-sop
- **purpose**: Builds restaurant SOPs for kitchen operations, front-of-house service, food safety, and opening/closing procedures. Use when standardizing restaurant operations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete restaurant sop document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Restaurant Sop support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Restaurant Sop or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 39. retainer-agreement
- **purpose**: Drafts retainer agreement templates with scope, hours, rollover policies, and termination terms for service providers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete retainer agreement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 40. retargeting-strategy
- **purpose**: Designs retargeting campaigns with audience segmentation, messaging by funnel stage, and frequency caps. Use when re-engaging website visitors who didn't convert.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete retargeting strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Retargeting Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Retargeting Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 41. retreat-planner
- **purpose**: Plans wellness retreats with itinerary, accommodation logistics, activity scheduling, and participant communications.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete retreat planner document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Retreat Planner support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Retreat Planner or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 42. retrospective
- **purpose**: Facilitates project and sprint retrospectives using structured frameworks like Start/Stop/Continue, 4Ls, and Sailboat, producing actionable improvement plans with owners and deadlines. Use when a user wants to learn from a completed project, improve team processes, run a post-mortem, or reflect on what went well and what did not after any initiative.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete retrospective document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Retrospective support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Retrospective or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 43. return-policy
- **purpose**: Writes clear, customer-friendly return and refund policies for e-commerce stores, digital products, and service businesses with plain-language clauses and platform-specific formatting. Use when a user needs a return policy for their online store, wants to update their refund terms, or needs policies for digital products, subscriptions, or services.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete return policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 44. revenue-forecast
- **purpose**: Projects revenue with multiple scenarios using historical data and market factors. Use when forecasting future revenue for planning or reporting.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete revenue forecast document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Revenue Forecast support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Revenue Forecast or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 45. revenue-model
- **purpose**: Designs revenue models with pricing tiers, unit economics, LTV calculations, and growth projections. Use when planning or validating your business revenue strategy.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete revenue model document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Revenue Model support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Revenue Model or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 46. review-response
- **purpose**: Writes professional responses to positive and negative online reviews across Google, Yelp, and social platforms to build trust and reputation.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete review response document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Review Response support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Review Response or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 47. risk-assessment
- **purpose**: Conducts business risk assessments with likelihood and impact scoring, mitigation strategies, and monitoring plans for proactive risk management.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete risk assessment document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Risk Assessment support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Risk Assessment or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 48. roi-calculator
- **purpose**: Builds ROI calculators for business decisions with cost inputs, benefit projections, and payback period analysis. Use when evaluating whether a business investment is worth it.
- **inputs**:
- `investment_name` (string, required): What is being invested in
- `investment_cost` (number, required): Total investment cost
- `expected_revenue` (number, required): Expected revenue or gain
- `time_period` (string, required): Time period for ROI calculation
- `additional_costs` (array, optional): Additional ongoing costs
- **outputs**:
- `roi_percentage` (number): Calculated ROI percentage
- `payback_period` (string): Time to recoup investment
- `break_even_analysis` (object): Breakeven point analysis
- `sensitivity_analysis` (array): Best/base/worst case scenarios
- **best used when**: When requiring strategic Roi Calculator support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Roi Calculator or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 49. saas-agreement
- **purpose**: Drafts SaaS subscription agreements with service levels, data ownership, and termination provisions. Use when creating terms for a software-as-a-service product.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete saas agreement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 50. saas-cancellation-flow
- **purpose**: Designs cancellation flows with retention offers, feedback collection, and win-back sequence triggers. Use when building or optimizing subscription cancellation experiences.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete saas cancellation flow document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Saas Cancellation Flow support under the Product domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Saas Cancellation Flow or when more specialized Product tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 51. saas-evaluation
- **purpose**: Evaluates SaaS tools for business adoption with feature comparison, pricing analysis, and migration planning. Use when choosing between software options for your business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete saas evaluation document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Saas Evaluation support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Saas Evaluation or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 52. saas-metrics-dashboard
- **purpose**: Sets up SaaS metrics dashboards tracking MRR, churn, LTV, CAC, expansion revenue, and cohort retention. Use when building or improving subscription business analytics.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete saas metrics dashboard document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Saas Metrics Dashboard support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Saas Metrics Dashboard or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 53. saas-onboarding-flow
- **purpose**: Designs SaaS user onboarding flows with activation milestones, tooltip sequences, and success metrics. Use when building or improving new user onboarding experiences.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete saas onboarding flow document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Saas Onboarding Flow support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Saas Onboarding Flow or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 54. sales-battlecard
- **purpose**: Creates competitive sales battlecards with objection responses, feature comparisons, and win/loss insights. Use when your team needs to sell against competitors.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete sales battlecard document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 55. sales-deck
- **purpose**: Creates sales presentation decks with discovery integration, ROI slides, and competitive positioning. Use when you need a persuasive slide deck for sales meetings.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete sales deck document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 56. sales-email-template
- **purpose**: Writes individual sales email templates for follow-up, proposal, negotiation, and close scenarios. Use when you need ready-to-send sales emails for specific situations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete sales email template document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 57. sales-funnel-builder
- **purpose**: Maps complete sales funnels with stages, conversion points, content, and optimization opportunities. Use when you need to design or audit your customer acquisition path.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete sales funnel builder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 58. sales-page
- **purpose**: Writes high-converting long-form sales pages using the Problem-Agitate-Solution framework with benefit stacking, objection handling, social proof sections, and urgency elements. Use when a user needs a sales page for a digital product, course, service, or membership that converts visitors into buyers.
- **inputs**:
- `product_name` (string, required): Product or service name
- `price` (string, required): Price point and pricing model
- `target_audience` (string, required): Ideal customer profile
- `transformation` (string, required): Before/after transformation the product delivers
- `top_benefits` (array, required): Top 5-7 benefits (not features)
- `objections` (array, optional): Known customer objections to address
- `testimonials` (array, optional): Social proof / testimonials
- `guarantee` (string, optional): Money-back or satisfaction guarantee details
- `urgency` (string, optional): Scarcity or urgency element
- **outputs**:
- `sales_page` (string): Full long-form sales page copy
- `headline_variants` (array): 3-5 headline options to A/B test
- `cta_variants` (array): 3 CTA button copy variants
- `cro_notes` (string): Conversion optimization recommendations
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 59. sales-script
- **purpose**: Creates phone, video, and DM sales call scripts with discovery questions, pitch flow, objection handling, and closing techniques. Use when a user needs to prepare for sales calls, wants a repeatable sales conversation framework, or is training a team on consultative selling.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete sales script document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 60. satisfaction-survey
- **purpose**: Creates customer satisfaction (CSAT) surveys with touchpoint-specific questions and benchmarking frameworks for measuring service quality.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete satisfaction survey document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Satisfaction Survey support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Satisfaction Survey or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 61. saudi-content-creator
- **purpose**: The smartest Saudi content creation system with authentic dialect architecture, CITC compliance, and platform-specific strategies. Use whenever creating ANY content for Saudi audiences: social media (X, TikTok, Snap, IG), ads (Google, Meta, Snap Ads), articles, brand materials, corporate comms, or PR. Trigger on: 'Saudi content,' 'KSA marketing,' 'Saudi dialect,' 'نجدي,' 'حجازي,' 'خليجي,' 'Vision 2030,' 'محتوى سعودي,' 'كتابة محتوى للسعودية,' or any content for the Saudi market. Covers 5 dialect zones, 5-level formality spectrum, cultural sensitivity, regulatory awareness, seasonal planning (Ramadan, Hajj, National Day, Founding Day), and Saudi audience behavior per platform. Even for simple requests like 'write a Saudi post' or 'I need KSA content,' use this skill.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete saudi content creator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Saudi Content Creator support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Saudi Content Creator or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 62. saudi-marketer-content-creator
- **purpose**: مخصص للسوق السعودي باللغة، الحس المحلي، طبيعة الجهات، وسياق التواصل التجاري في المملكة
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete saudi marketer content creator document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Saudi Marketer Content Creator support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Saudi Marketer Content Creator or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 63. schema-markup-guide
- **purpose**: Generates schema markup recommendations with JSON-LD code for articles, products, FAQs, and local businesses. Use when adding structured data to your website.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete schema markup guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 64. scope-of-work
- **purpose**: Creates detailed scope of work documents with deliverables, milestones, assumptions, and exclusions for client projects.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete scope of work document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Scope Of Work support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Scope Of Work or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 65. script-automation-manager
- **purpose**: Manages validation scripts and automation tasks.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete script automation manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Script Automation Manager support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Script Automation Manager or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 66. script-to-blog
- **purpose**: Converts video or podcast transcripts into polished, SEO-optimized blog posts with proper formatting. Use when repurposing audio/video content into written articles.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete script to blog document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Script To Blog support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Script To Blog or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 67. seasonal-campaign
- **purpose**: Plans seasonal and holiday marketing campaigns with timelines, creative themes, and channel strategies. Use this skill when a user needs to plan a campaign around a holiday, seasonal event, back-to-school period, or any time-bound buying moment for their e-commerce or service business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete seasonal campaign document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Seasonal Campaign support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Seasonal Campaign or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 68. seasonal-inventory-plan
- **purpose**: Plans seasonal inventory with demand forecasting, ordering timelines, and clearance strategy to maximize revenue and minimize dead stock.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete seasonal inventory plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Seasonal Inventory Plan support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Seasonal Inventory Plan or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 69. seasonal-menu-plan
- **purpose**: Plans seasonal menu rotations with ingredient sourcing, pricing adjustments, and launch marketing. Use when updating restaurant menus for seasonal relevance.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete seasonal menu plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Seasonal Menu Plan support under the Food & Restaurant domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Seasonal Menu Plan or when more specialized Food & Restaurant tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 70. self-service-portal
- **purpose**: Designs self-service portal structures with knowledge base, ticketing, account management, and resource libraries for customer independence.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete self service portal document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Self Service Portal support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Self Service Portal or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 71. seller-onboarding
- **purpose**: Creates seller onboarding programs for marketplaces with verification, listing guides, and success milestones. Use when building seller activation flows for platform businesses.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete seller onboarding document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Seller Onboarding support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Seller Onboarding or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 72. sentiment-analysis
- **purpose**: Analyzes customer sentiment from reviews, social media, and support tickets with trend tracking, theme categorization, and alert recommendations. Use for brand health monitoring.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete sentiment analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Sentiment Analysis support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Sentiment Analysis or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 73. seo-aeo-geo-superhero
- **purpose**: للـ search visibility، المقالات، صفحات الهبوط، وتحسين قابلية الظهور في محركات البحث وإجابات الـ AI
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete seo aeo geo superhero document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**:
  - primary_output
  - summary
  - next_steps

#### 74. seo-audit
- **purpose**: Conducts on-page SEO analysis with title tags, meta descriptions, heading structure, keyword gaps, and technical recommendations. Use when a user wants to improve their website's search rankings, is launching a new site, or needs to diagnose why their pages aren't ranking.
- **inputs**:
- `website_url` (string, required): Website URL to audit
- `business_type` (string, required): Type of business
- `current_rankings` (array, optional): Current keyword rankings
- `competitors` (array, optional): Main competitor URLs
- `audit_focus` (string, optional): Focus: technical|content|links|all
- **outputs**:
- `audit_score` (integer): Overall SEO health score (0-100)
- `critical_issues` (array): High-priority issues to fix immediately
- `recommendations` (array): Prioritized action items
- `quick_wins` (array): Easy wins for immediate improvement
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 75. seo-competitor-analysis
- **purpose**: Analyzes competitor SEO strategies with keyword overlap, content gaps, backlink profiles, and ranking comparisons. Use when you need to benchmark against competitors.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete seo competitor analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Seo Competitor Analysis support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Seo Competitor Analysis or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 76. seo-content-brief
- **purpose**: Writes SEO content briefs with target keywords, competitor analysis, SERP feature opportunities, and outline structure. Use when assigning content to writers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete seo content brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 77. seo-migration-plan
- **purpose**: Plans website migrations with redirect mapping, risk assessment, and monitoring checklist. Use when changing domains, platforms, or redesigning your site.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete seo migration plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 78. seo-reporting-template
- **purpose**: Creates SEO reporting templates with KPI tracking, ranking changes, traffic analysis, and conversion attribution. Use when building regular SEO performance reports.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete seo reporting template document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 79. service-guarantee
- **purpose**: Creates service guarantees and satisfaction commitments with specific terms, exclusions, and claim procedures.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete service guarantee document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Service Guarantee support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Service Guarantee or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 80. service-level-agreement
- **purpose**: Drafts service level agreements with response times, uptime commitments, penalty and credit structures, and performance metrics.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete service level agreement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 81. service-productization
- **purpose**: Converts custom services into productized offerings with fixed scope, pricing, and delivery processes for scalable revenue.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete service productization document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Service Productization support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Service Productization or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 82. service-recovery-plan
- **purpose**: Designs service recovery protocols for when things go wrong with response scripts, compensation guidelines, and follow-up procedures.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete service recovery plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Service Recovery Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Service Recovery Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 83. shipping-policy
- **purpose**: Writes clear shipping and delivery policies with rate tables, timelines, and international terms. Use this skill when a user needs a shipping policy for their e-commerce store, wants to document delivery timelines, or needs professional shipping and returns documentation for their website.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete shipping policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 84. short-form-video-plan
- **purpose**: Creates a 30-day short-form video content plan with hooks, formats, trending audio cues, and repurposing notes. Use when planning a month of TikToks, Reels, or YouTube Shorts.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete short form video plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Short Form Video Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Short Form Video Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 85. signage-brief
- **purpose**: Creates signage and environmental graphics briefs with location specs, materials, messaging, compliance requirements, and vendor specifications. Use when planning physical signage.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete signage brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Signage Brief support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Signage Brief or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 86. signature-talk
- **purpose**: Develops signature keynote talks with modular sections, audience customization guides, and delivery notes. Use when building a repeatable talk for stages, summits, or webinars.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete signature talk document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Signature Talk support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Signature Talk or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 87. site-architecture-plan
- **purpose**: Plans website information architecture with URL structure, internal linking strategy, and content hierarchy. Use when building or restructuring a website for SEO.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete site architecture plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Site Architecture Plan support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Site Architecture Plan or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 88. size-guide
- **purpose**: Creates product size guides with measurement instructions, comparison charts, fit recommendations, and international conversions. Use when reducing size-related returns.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete size guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Size Guide support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Size Guide or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 89. skill-assessment
- **purpose**: Builds skill assessment tools with competency levels, evaluation rubrics, and development recommendations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete skill assessment document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Skill Assessment support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Skill Assessment or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 90. social-impact-measurement
- **purpose**: Designs social impact measurement frameworks with indicators, data collection methods, and reporting templates.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete social impact measurement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Social Impact Measurement support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Social Impact Measurement or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 91. social-listening-plan
- **purpose**: Designs social listening frameworks for monitoring brand mentions, competitor activity, and industry conversations. Use when setting up systematic monitoring of online conversations about your brand.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete social listening plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Social Listening Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Social Listening Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 92. social-media-audit
- **purpose**: Conducts a structured social media presence audit across platforms with profile optimization checks, content analysis, engagement assessment, and actionable improvement recommendations. Use when a user wants to evaluate their social media performance, needs to identify what's working and what's not, or is preparing a social media strategy refresh.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete social media audit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Social Media Audit support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Social Media Audit or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 93. social-media-calendar
- **purpose**: Creates platform-specific social media calendars with daily themes, content types, and optimal posting times. Use when planning your social content for the week or month ahead.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete social media calendar document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Social Media Calendar support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Social Media Calendar or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 94. social-media-graphics
- **purpose**: Generates coordinated multi-platform social media graphics from a single creative brief using Canva. Use when a user needs consistent branded visuals across Instagram, Facebook, X/Twitter, LinkedIn, or Pinterest from one design concept.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete social media graphics document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Social Media Graphics support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Social Media Graphics or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 95. social-media-policy
- **purpose**: Writes social media policies for businesses covering employee guidelines, brand voice, crisis protocols, and compliance. Use when formalizing how your business and team behave on social media.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete social media policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 96. social-media-specialist
- **purpose**: لإدارة المحتوى الاجتماعي، كتابة posts، بناء content calendars، وتحويل الأفكار اليومية إلى خطة واضحة
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete social media specialist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Social Media Specialist support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Social Media Specialist or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 97. social-media-strategy
- **purpose**: Creates a comprehensive social media strategy with platform selection, posting cadence, content mix, and growth targets. Use when building or overhauling your social media presence.
- **inputs**:
- `business_type` (string, required): Type of business
- `current_platforms` (array, required): Active social platforms
- `target_audience` (string, required): Primary audience description
- `goals` (array, required): Goals: followers|engagement|leads|sales
- `resources` (string, optional): Team and budget available
- `competitors` (array, optional): Main competitor accounts
- **outputs**:
- `platform_strategy` (object): Strategy per platform
- `content_pillars` (array): 3-5 content pillars
- `90_day_plan` (array): 90-day action plan
- `kpis` (array): Success metrics and targets
- **best used when**: When requiring strategic Social Media Strategy support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Social Media Strategy or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 98. social-proof-collector
- **purpose**: Creates systems for collecting and displaying social proof: screenshots, reviews, UGC, and metrics badges. Use when building a process to gather testimonials and credibility signals.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete social proof collector document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Social Proof Collector support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Social Proof Collector or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 99. sop-builder
- **purpose**: Builds standard operating procedures from a conversational interview about any business process and publishes the structured SOP to Notion. Use when a user wants to document a repeatable process, onboard team members, or systematize operations they currently do from memory.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete sop builder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Sop Builder support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Sop Builder or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 100. speaker-outreach
- **purpose**: Writes speaker recruitment emails with event details, compensation, audience profile, and logistics information.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete speaker outreach document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Speaker Outreach support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Speaker Outreach or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 101. speaking-one-sheet
- **purpose**: Creates professional speaker one-sheets with topics, bio, testimonials, headshot specs, and booking information.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete speaking one sheet document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Speaking One Sheet support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Speaking One Sheet or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 102. speaking-proposal
- **purpose**: Creates conference speaking proposals with talk descriptions, speaker bios, audience takeaways, and AV requirements.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete speaking proposal document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Speaking Proposal support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Speaking Proposal or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 103. spec-kit-architect
- **purpose**: This skill was automatically generated from the `.spec-kit` infrastructure directory.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete spec kit architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Spec Kit Architect support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Spec Kit Architect or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 104. specify-config-manager
- **purpose**: Manages Specify app cheat sheets and integrations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete specify config manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Specify Config Manager support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Specify Config Manager or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 105. speckit-commands-manager
- **purpose**: Handles SpecKit command definitions (analyze, plan, specify).
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete speckit commands manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Speckit Commands Manager support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Speckit Commands Manager or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 106. speech-writer
- **purpose**: Writes keynotes, conference talks, and podcast guest talking points with timing, delivery notes, and audience engagement techniques. Use when a user is preparing for a speaking engagement, guest podcast appearance, panel discussion, or needs to structure their ideas into a compelling talk.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete speech writer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Speech Writer support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Speech Writer or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 107. sponsor-pitch
- **purpose**: Writes sponsorship pitch decks for podcasts, newsletters, or events with audience data, pricing, and package options. Use when seeking sponsors for your media properties.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete sponsor pitch document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Sponsor Pitch support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Sponsor Pitch or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 108. sponsor-thank-you
- **purpose**: Creates sponsor and donor thank-you communications with personalization, impact updates, and continued engagement.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete sponsor thank you document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Sponsor Thank You support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Sponsor Thank You or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 109. status-update-template
- **purpose**: Creates reusable status update templates for projects, clients, or stakeholders with progress indicators and clear formatting.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete status update template document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Status Update Template support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Status Update Template or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 110. store-launch-plan
- **purpose**: Plans e-commerce store launches with pre-launch checklist, marketing calendar, launch day playbook, and post-launch optimization priorities. Use when opening an online store.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete store launch plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Store Launch Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Store Launch Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 111. store-page-audit
- **purpose**: Audits e-commerce store pages for conversion optimization with layout, copy, trust signals, and technical recommendations.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete store page audit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Store Page Audit support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Store Page Audit or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 112. strategic-alliance-plan
- **purpose**: Designs strategic alliance frameworks with partner evaluation, mutual benefit mapping, and governance structure.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete strategic alliance plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Strategic Alliance Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Strategic Alliance Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 113. student-feedback-form
- **purpose**: Creates course evaluation forms with rating scales, open-ended questions, and improvement-focused categories for gathering actionable student feedback.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete student feedback form document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Student Feedback Form support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Student Feedback Form or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 114. study-guide
- **purpose**: Writes study guides with key concepts, review questions, memory aids, and exam preparation strategies.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete study guide document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Study Guide support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Study Guide or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 115. style-tile
- **purpose**: Creates style tiles for web design projects with typography, colors, UI elements, textures, and mood references. Use when aligning on visual direction before full design.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete style tile document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Style Tile support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Style Tile or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 116. subcontractor-agreement
- **purpose**: Drafts subcontractor agreements with scope delegation, payment terms, and quality requirements for service businesses.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete subcontractor agreement document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 117. subscription-box-plan
- **purpose**: Plans subscription box businesses with curation strategy, pricing, fulfillment logistics, and retention tactics for recurring revenue growth.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete subscription box plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Subscription Box Plan support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Subscription Box Plan or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 118. subscription-metrics
- **purpose**: Calculates and reports on subscription metrics including MRR, ARR, churn rate, LTV, and CAC. Use when tracking the health of a subscription-based business.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete subscription metrics document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Subscription Metrics support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Subscription Metrics or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 119. succession-plan
- **purpose**: Creates succession planning frameworks for key roles with readiness assessments, development paths, risk analysis, and transition timelines. Use when preparing for leadership continuity.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete succession plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Succession Plan support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Succession Plan or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 120. supplement-disclaimer
- **purpose**: Writes supplement and product disclaimers with FDA compliance language and health claim boundaries.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete supplement disclaimer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 121. support-response-templates
- **purpose**: Writes customer support response templates for common scenarios with tone guidelines, personalization cues, and escalation triggers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete support response templates document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Support Response Templates support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Support Response Templates or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 122. survey-analysis
- **purpose**: Analyzes survey results with statistical summaries, cross-tabulations, trend identification, and actionable insight recommendations. Use when interpreting survey data for decisions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete survey analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Survey Analysis support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Survey Analysis or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 123. survey-builder
- **purpose**: Creates customer feedback surveys with strategically ordered questions, response scales, and analysis frameworks for measuring satisfaction, gathering product feedback, or validating new ideas. Use when a user needs to collect customer feedback, wants to run a Net Promoter Score survey, or needs to validate a product idea before building it.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete survey builder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Survey Builder support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Survey Builder or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 124. swot-analysis
- **purpose**: Conducts structured SWOT analyses with prioritized strengths, weaknesses, opportunities, and threats, cross-referenced into strategic action items. Use when a user needs to evaluate their business position, is planning a new venture, making a strategic decision, or preparing for a planning session.
- **inputs**:
- `business_name` (string, required): Business or project name
- `industry` (string, required): Industry or sector
- `context` (string, required): Specific context: expansion|launch|competitive|pivot
- `known_strengths` (array, optional): Known strengths to include
- `known_weaknesses` (array, optional): Known weaknesses to include
- **outputs**:
- `swot_matrix` (object): Full SWOT matrix
- `strategic_options` (array): SO, WO, ST, WT strategies
- `priority_actions` (array): Top priority actions from analysis
- **best used when**: When requiring strategic Swot Analysis support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Swot Analysis or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 125. task-prioritization
- **purpose**: Creates task prioritization frameworks using Eisenhower matrix, ICE scoring, or MoSCoW method to help entrepreneurs focus on highest-impact work.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete task prioritization document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Task Prioritization support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Task Prioritization or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 126. tax-deduction-finder
- **purpose**: Identifies commonly missed business tax deductions by industry and entity type with category lists and documentation requirements. Use this skill when a freelancer or small business owner is preparing for tax season, wants to reduce their tax bill, or needs to know what business expenses are deductible.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tax deduction finder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Tax Deduction Finder support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Tax Deduction Finder or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 127. tax-prep-checklist
- **purpose**: Creates tax preparation checklists organized by entity type with document gathering and deadline tracking. Use when preparing for business tax filing season.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tax prep checklist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Tax Prep Checklist support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Tax Prep Checklist or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 128. team-building-plan
- **purpose**: Plans team building activities and events with objectives, activity options, budget considerations, logistics, and follow-up evaluation. Use when organizing team bonding, offsites, or morale-boosting events.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete team building plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Team Building Plan support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Team Building Plan or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 129. team-charter
- **purpose**: Creates team charters with mission, roles, decision-making processes, and communication agreements for aligned and effective teamwork.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete team charter document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Team Charter support under the HR & People domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Team Charter or when more specialized HR & People tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 130. tech-stack-recommendation
- **purpose**: Recommends tech stacks for specific business types with tool selection rationale, costs, and implementation order. Use when building your business software foundation.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tech stack recommendation document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Tech Stack Recommendation support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Tech Stack Recommendation or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 131. technical-seo-checklist
- **purpose**: Creates technical SEO audit checklists covering crawlability, indexation, Core Web Vitals, and structured data. Use when auditing your website's technical health.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete technical seo checklist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Technical Seo Checklist support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Technical Seo Checklist or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 132. ted-talk-outline
- **purpose**: Structures TED-style talk outlines with narrative arc, audience engagement points, and timing markers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ted talk outline document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Ted Talk Outline support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ted Talk Outline or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 133. tenant-screening-checklist
- **purpose**: Creates tenant screening checklists with verification steps, reference check questions, and evaluation criteria.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tenant screening checklist document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Tenant Screening Checklist support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Tenant Screening Checklist or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 134. terms-of-service
- **purpose**: Creates terms of service documents for websites, SaaS products, and digital platforms with plain-language annotations. Use when a user is launching a website, app, or online service and needs legal terms governing usage, liability, and user conduct.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete terms of service document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 135. terms-of-use-app
- **purpose**: Creates terms of use specifically for mobile apps with license grants, restrictions, and app store compliance. Use when launching or updating a mobile application.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete terms of use app document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 136. test-kit-architect
- **purpose**: Manages the testing bootstrap, frameworks, and QA processes.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete test kit architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Test Kit Architect support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Test Kit Architect or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 137. testimonial-collector
- **purpose**: Builds a complete testimonial collection system with request email templates, follow-up sequences, structured capture formats, and strategic placement guidelines. Use when a user wants to systematically collect client testimonials, needs social proof for their website or sales pages, or wants to turn happy customers into case studies.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete testimonial collector document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Testimonial Collector support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Testimonial Collector or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 138. thank-you-campaign
- **purpose**: Creates customer appreciation campaigns with personalized messaging, gifts, and milestone recognition. Use this skill when a user wants to build a thank-you campaign, customer appreciation program, retention-focused gratitude initiative, or milestone celebration sequence to delight and retain customers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete thank you campaign document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Thank You Campaign support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Thank You Campaign or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 139. thought-leader-content-plan
- **purpose**: Plans thought leadership content across articles, talks, social posts, and interviews with consistent messaging.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete thought leader content plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Thought Leader Content Plan support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Thought Leader Content Plan or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 140. thought-leadership
- **purpose**: Writes opinion pieces and thought leadership articles that position the author as an industry authority. Use when you need to publish a strong perspective on an industry topic.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete thought leadership document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Thought Leadership support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Thought Leadership or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 141. thread-hook-writer
- **purpose**: Writes scroll-stopping first lines for social media threads optimized by platform (X, LinkedIn, Threads). Use when you need compelling opening hooks that earn the click and the read.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete thread hook writer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Thread Hook Writer support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Thread Hook Writer or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 142. tiktok-ad-script
- **purpose**: Creates TikTok ad scripts that feel native to the platform with trending hooks, UGC style, and spark ad recommendations. Use when writing video ad scripts for TikTok campaigns.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tiktok ad script document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Tiktok Ad Script support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Tiktok Ad Script or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 143. tiktok-script
- **purpose**: Writes short-form vertical video scripts with hooks, transitions, text overlays, and trending audio suggestions. Use when you need TikTok or Reels video scripts that capture attention fast.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tiktok script document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Tiktok Script support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Tiktok Script or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 144. time-audit
- **purpose**: Analyzes time allocation across activities and recommends optimization strategies with categorization, value scoring, and reallocation plans. Use when a freelancer or solopreneur feels busy but unproductive, wants to find where their time goes, needs to free up hours for higher-value work, or suspects they are spending too much time on low-impact tasks.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete time audit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Time Audit support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Time Audit or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 145. tool-stack-audit
- **purpose**: Audits business technology stacks for redundancy, cost optimization, and integration opportunities. Use when reviewing and optimizing your business software spend.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tool stack audit document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Tool Stack Audit support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Tool Stack Audit or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 146. tracking-attribution-architect
- **purpose**: Design tracking plans, event architectures, attribution setups, KPI measurement models, dashboard designs, and reporting logic. Use proactively whenever a user needs a tracking plan, conversion event schema, attribution model, pixel setup plan, dashboard structure, or reporting framework for paid media, LMS, e-commerce, or lead-gen funnels. Trigger on tracking plan, event architecture, attribution, conversion tracking, pixel setup, GA4 setup, dashboard design, reporting logic, or measurement framework.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tracking attribution architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Tracking Attribution Architect support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Tracking Attribution Architect or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 147. trademark-application
- **purpose**: Guides trademark application preparation with class selection, specimen requirements, and filing checklists. Use when preparing to file a trademark with the USPTO.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete trademark application document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 148. training-manual
- **purpose**: Writes training manuals with step-by-step instructions, visual aids, knowledge checks, and reference sections.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete training manual document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Training Manual support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Training Manual or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 149. training-plan
- **purpose**: Designs employee training programs with learning objectives, curriculum structure, delivery methods, assessment criteria, and completion tracking. Use when upskilling your team.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete training plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Training Plan support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Training Plan or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 150. transactional-email
- **purpose**: Writes transactional emails (order confirmations, shipping updates, receipts) with brand voice and upsell opportunities. Use when creating or improving automated emails triggered by customer actions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete transactional email document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 151. trial-to-paid-email
- **purpose**: Writes trial-to-paid conversion email sequences with feature education, social proof, and urgency progression. Use when optimizing free trial conversion rates.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete trial to paid email document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 152. tripwire-offer
- **purpose**: Creates low-ticket tripwire offers with pricing strategy, delivery mechanism, and upsell path. Use when you need to convert leads into buyers with a small first purchase.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tripwire offer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 153. tutorial-writer
- **purpose**: Creates step-by-step tutorials with screenshot placeholders, code snippets, and troubleshooting sections. Use this skill when a user needs to write a how-to guide, help documentation, onboarding walkthrough, or educational tutorial for their product, tool, or process.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete tutorial writer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Tutorial Writer support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Tutorial Writer or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 154. twitter-thread
- **purpose**: Creates viral-format Twitter/X threads with numbered hooks, engagement bait, and a pinned summary tweet. Use when you need to break down ideas into a compelling multi-tweet thread.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete twitter thread document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Twitter Thread support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Twitter Thread or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 155. two-sided-email-strategy
- **purpose**: Creates email strategies for two-sided marketplaces with separate buyer and seller communication tracks. Use when designing email programs for platform businesses.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete two sided email strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Two Sided Email Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Two Sided Email Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 156. ugc-script-writer
- **purpose**: لكتابة UGC hooks, scripts, creator directions، وزوايا فيديوهات مناسبة للإعلانات والسوشيال
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete ugc script writer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Ugc Script Writer support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Ugc Script Writer or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 157. unboxing-experience
- **purpose**: Designs unboxing experiences with packaging sequence, insert cards, thank-you notes, and social sharing prompts to increase retention and word-of-mouth. Use for e-commerce brands.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete unboxing experience document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Unboxing Experience support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Unboxing Experience or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 158. unit-economics
- **purpose**: Calculates unit economics for products and services with contribution margin, payback period, and LTV:CAC ratios. Use when evaluating the profitability of each customer or unit.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete unit economics document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Unit Economics support under the Finance & Analytics domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Unit Economics or when more specialized Finance & Analytics tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 159. upsell-sequence
- **purpose**: Builds post-purchase upsell and cross-sell email sequences that increase average order value through complementary offers, upgrades, and bundles timed to the customer journey. Use when a user wants to increase revenue from existing customers, needs a post-purchase email flow, or wants to promote upgrades, add-ons, or complementary products after an initial sale.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete upsell sequence document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Upsell Sequence support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Upsell Sequence or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 160. user-generated-content
- **purpose**: Creates UGC campaigns with submission guidelines, incentive structures, rights management, and curation workflows. Use when planning campaigns that encourage customers to create content for your brand.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete user generated content document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic User Generated Content support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to User Generated Content or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 161. user-research-plan
- **purpose**: Plans user research studies with recruitment, interview scripts, survey design, and insight synthesis frameworks. Use when gathering customer insights to inform decisions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete user research plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic User Research Plan support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to User Research Plan or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 162. value-proposition-canvas
- **purpose**: Maps value propositions using the Value Proposition Canvas framework with customer jobs, pains, and gains. Use when refining your product-market fit messaging.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete value proposition canvas document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Value Proposition Canvas support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Value Proposition Canvas or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 163. vendor-evaluation
- **purpose**: Creates structured vendor and tool comparison matrices with weighted scoring, cost analysis, and recommendation summaries for making informed purchasing decisions. Use when a user needs to choose between software tools, service providers, or vendors and wants a systematic evaluation rather than a gut decision.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete vendor evaluation document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Vendor Evaluation support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Vendor Evaluation or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 164. vendor-onboarding
- **purpose**: Creates vendor onboarding checklists with documentation requirements, compliance checks, and setup procedures for smooth partnerships.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete vendor onboarding document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Vendor Onboarding support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Vendor Onboarding or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 165. vibe-coding-playbook
- **purpose**: Vibe Coding Playbook — Professional-grade content skill for the PrePilot Agency Suite.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete vibe coding playbook document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Vibe Coding Playbook support under the System domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Vibe Coding Playbook or when more specialized System tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 166. vibe-design-md-architect
- **purpose**: Create, audit, and amplify PRODUCT.md and DESIGN.md before UI work; automatically install Impeccable with npx impeccable skills install when shell access exists; repair old or weak design.md files into stronger agent-ready design systems; run an intake session before design decisions with a mandatory first question selecting a design system baseline; run a 2026-aligned standards search gate; enforce strict rules engines and multi-stage quality gates; use Impeccable workflows, anti-AI slop rules, RTL checks, and evals for SaaS, web apps, dashboards, and landing pages.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete vibe design md architect document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Vibe Design Md Architect support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Vibe Design Md Architect or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 167. video-script
- **purpose**: Writes ready-to-film video scripts with hooks, segment breakdowns, B-roll cues, text overlay notes, timing estimates, and shot lists. Use when a user needs a script for YouTube, TikTok, Instagram Reels, course content, or any video format where a structured script improves production quality.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete video script document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Video Script support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Video Script or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 168. viral-content-engine
- **purpose**: Arabic-first viral content system built on reverse-engineered patterns from real high-performing posts (26K+ impressions, 593 comments, 2.24% comment rate) on LinkedIn and Facebook. Use this skill EVERY TIME the user wants to create content that spreads, get ideas for posts, build hooks, develop content pillars, generate image prompts, or write captions for social media. Trigger on: "اعملي بوست", "عايز محتوى", "فكرة بوست", "hook", "كابشن", "go viral", "اعملي content", "بوست لينكدإن", "بوست فيسبو
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete viral content engine document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Viral Content Engine support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Viral Content Engine or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 169. viral-content-formula
- **purpose**: Analyzes viral content patterns and creates frameworks for engineering shareable content across platforms. Use when designing content with maximum share potential and organic reach.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete viral content formula document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Viral Content Formula support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Viral Content Formula or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 170. virtual-event-platform
- **purpose**: Plans virtual event setups with platform selection criteria, engagement features, and technical requirements.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete virtual event platform document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Virtual Event Platform support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Virtual Event Platform or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 171. visual-identity-brief
- **purpose**: Creates briefs for designers with mood board direction, style references, do's and don'ts, and deliverable specifications. Use when hiring a designer for brand work.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete visual identity brief document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Visual Identity Brief support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Visual Identity Brief or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 172. voice-of-customer
- **purpose**: Builds Voice of Customer programs with collection methods, analysis frameworks, and insight distribution to drive customer-centric decisions.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete voice of customer document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Voice Of Customer support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Voice Of Customer or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 173. volunteer-recruitment
- **purpose**: Creates volunteer recruitment campaigns with role descriptions, application processes, and onboarding materials.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete volunteer recruitment document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Volunteer Recruitment support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Volunteer Recruitment or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 174. vscode-workspace-manager
- **purpose**: Manages VS Code workspace settings, tasks, and snippets.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete vscode workspace manager document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Vscode Workspace Manager support under the Technology domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Vscode Workspace Manager or when more specialized Technology tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 175. waitlist-builder
- **purpose**: Creates waitlist landing pages and email sequences to build demand before product availability. Use when launching a product and want to build anticipation.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete waitlist builder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Waitlist Builder support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Waitlist Builder or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 176. waiver-release
- **purpose**: Drafts liability waivers and release forms for events, services, and activities. Use when you need participants to acknowledge and accept risks.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete waiver release document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 177. webinar-email-sequence
- **purpose**: Writes pre-webinar, reminder, live, replay, and follow-up email sequences with registration optimization. Use when promoting and following up on webinars.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete webinar email sequence document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 178. webinar-planner
- **purpose**: Plans webinars end-to-end with content outlines, slide structures, promotional email sequences, registration page copy, and post-webinar follow-up, with optional planning pages in Notion and promotional graphics in Canva. Use when a user is hosting a webinar, live workshop, or virtual event and needs the full content and promotional package.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete webinar planner document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Webinar Planner support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Webinar Planner or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 179. webinar-sales-script
- **purpose**: Creates webinar presentation scripts designed to sell, with teaching content, transition, and pitch sections. Use when building a webinar that converts to sales.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete webinar sales script document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When building sales funnels, high-ticket sales copy, outbound sequences, or preparing objection-handling sheets.
- **avoid when**: When drafting basic internal administrative memos that have no commercial conversion objective.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 180. weekly-report
- **purpose**: Transforms bullet-point inputs into structured weekly reports with executive summary, metrics tables, wins, blockers with proposed solutions, and next-week priorities. Use when a user needs to compile a weekly status update, wants to present progress to clients or stakeholders, or needs to document team accomplishments and blockers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete weekly report document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Weekly Report support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Weekly Report or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 181. welcome-sequence
- **purpose**: Builds new customer and subscriber welcome experiences with email series, onboarding steps, and quick wins. Use when a user has new subscribers joining an email list, customers purchasing a product, or members signing up for a program and needs a structured first-impression sequence.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete welcome sequence document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When designing automated email workflows, writing welcome sequences, abandoned cart recovery drip series, or optimizing deliverability.
- **avoid when**: When drafting formal employee agreements or building web application frontends.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 182. wellness-assessment
- **purpose**: Builds wellness intake assessments with health history, goal setting, and lifestyle evaluation questionnaires.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete wellness assessment document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Wellness Assessment support under the Health & Wellness domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Wellness Assessment or when more specialized Health & Wellness tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 183. wellness-workshop-plan
- **purpose**: Plans wellness workshops with curriculum, activity guides, handouts, and post-workshop resource lists.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete wellness workshop plan document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Wellness Workshop Plan support under the Health & Wellness domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Wellness Workshop Plan or when more specialized Health & Wellness tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 184. white-paper
- **purpose**: Writes authoritative white papers with executive summary, research sections, data visualization suggestions, and lead-gen CTA. Use when you need a long-form thought leadership asset for B2B lead generation or industry authority building.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete white paper document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic White Paper support under the Content Creation domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to White Paper or when more specialized Content Creation tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 185. wholesale-catalog
- **purpose**: Creates wholesale catalogs with product listings, tiered pricing, MOQs, and ordering information for retail buyers.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete wholesale catalog document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Wholesale Catalog support under the General domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Wholesale Catalog or when more specialized General tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 186. win-back-campaign
- **purpose**: Builds re-engagement email and message sequences to win back churned subscribers, lapsed customers, or inactive users with personalized triggers, incentive strategies, and graceful exit paths. Use when a user has inactive email subscribers, lapsed customers who stopped buying, or churned users they want to re-engage.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete win back campaign document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Win Back Campaign support under the Marketing domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Win Back Campaign or when more specialized Marketing tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 187. win-loss-analysis
- **purpose**: Creates win/loss analysis frameworks with interview questions, pattern identification, and action plans. Use when you need to understand why deals close or fall through.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete win loss analysis document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Win Loss Analysis support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Win Loss Analysis or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 188. workflow-mapper
- **purpose**: Maps business processes into text-based flowcharts with decision points, handoffs, and timing estimates, then identifies bottlenecks and automation opportunities. Use when a user wants to document how their business actually works, find inefficiencies, visualize a process, or decide what to automate.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete workflow mapper document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Workflow Mapper support under the Operations domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Workflow Mapper or when more specialized Operations tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 189. workplace-policy
- **purpose**: Creates workplace policies covering remote work, equipment, communication, and professional conduct. Use when establishing rules and expectations for your team.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete workplace policy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When drafting compliance policies, NDAs, privacy declarations, terms of services, or data processing agreements.
- **avoid when**: When creating casual promotional content or brainstorming viral marketing ideas.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 190. workshop-builder
- **purpose**: Designs complete workshop curricula including agendas, exercises, handouts, and facilitator guides. Use when a user wants to plan a paid or free workshop, training session, webinar with interactive elements, or live educational event and needs a structured curriculum with timing and materials.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete workshop builder document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Workshop Builder support under the Events domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Workshop Builder or when more specialized Events tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 191. workshop-handout
- **purpose**: Creates workshop handout materials with exercises, reference sheets, templates, and post-workshop action items.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete workshop handout document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Workshop Handout support under the Education & Training domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Workshop Handout or when more specialized Education & Training tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 192. youtube-ad-script
- **purpose**: Writes YouTube ad scripts for pre-roll, mid-roll, and bumper formats with hooks, messaging, and CTA variations. Use when creating video ad scripts for YouTube advertising campaigns.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete youtube ad script document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Youtube Ad Script support under the Advertising domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Youtube Ad Script or when more specialized Advertising tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 193. youtube-seo
- **purpose**: Optimizes YouTube videos for search with titles, descriptions, tags, chapters, and thumbnail recommendations. Use when maximizing video discoverability on YouTube.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete youtube seo document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When auditing website SEO, planning local search strategies, optimizing meta tags, or generating search-engine-friendly content.
- **avoid when**: When designing creative brand logos or writing offline event scripts.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 194. youtube-strategy
- **purpose**: Plans YouTube channel strategy with content pillars, upload schedule, thumbnail guidelines, and growth milestones. Use when launching or restructuring a YouTube channel for business growth.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete youtube strategy document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Youtube Strategy support under the Strategy & Planning domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Youtube Strategy or when more specialized Strategy & Planning tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

#### 195. youtube-thumbnail
- **purpose**: Generates three YouTube thumbnail options optimized for click-through rate using Canva, applying high-contrast colors, emotional expressions, and concise text overlays. Use when a user needs a thumbnail for a YouTube video, wants to A/B test thumbnail designs, or needs click-optimized visual assets at 1280x720.
- **inputs**:
- `brief` (string, required): Description of what you need
- `target_audience` (string, optional): Who this is for
- `brand_voice` (string, optional): Tone and style preferences
- `context` (string, optional): Business context and background
- `constraints` (string, optional): Any limitations or requirements
- **outputs**:
- `primary_output` (string): Complete youtube thumbnail document
- `summary` (string): Executive summary
- `next_steps` (array): Recommended next steps
- **best used when**: When requiring strategic Youtube Thumbnail support under the Creative & Design domain to ensure professional-grade delivery.
- **avoid when**: For ad-hoc tasks unrelated to Youtube Thumbnail or when more specialized Creative & Design tools are available.
- **example prompt**: Not provided
- **expected result schema**: primary_output, summary, next_steps

## Recipes
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core

## Changelog
Source: internal
Last reviewed: 2026-06-20
Audience: agents
Priority: core

## Summary
Actionable recovery pathways and diagnostic procedures for common PrePilot operational errors, connection drops, rate-limiting, and verification failures.

## Key facts
- Network interruptions on SSE routes are typically caused by Cloud Run connection timeouts or client proxy limits.
- Status code 429 indicates credit pool depletion rather than server hardware overloads.
- Visual widget rendering issues are usually resolved by correcting Content Security Policies (CSP) or MIME-type configurations.

## Content
Follow these diagnostic procedures to resolve common failure modes.

### 1. Connection Drops & SSE Timeouts (HTTP 504 / Connection Interrupted)
- **Problem**: Long-running LLM tasks or complex skill executions time out, causing the client to drop the SSE connection.
- **Diagnostics**: Check Cloud Run logs for request execution times exceeding 300 seconds.
- **Resolution**:
  - Increase the Google Cloud Run timeout limit to 900 seconds (`cloudrun.deploy.sh` configuration: `--timeout=900`).
  - Configure the client command to automatically reconnect. For Claude Desktop, append keep-alive headers or use the reconnect flag with `npx @mcp-use/cli`.
  - Verify that intermediate heartbeats are being emitted by the FastAPI server every 15 seconds.

### 2. Rate Limits & Balance Depletion (HTTP 429 - `CREDIT_DEPLETED`)
- **Problem**: Tool calls are blocked; server responds with an explicit balance depletion error.
- **Diagnostics**: Execute the `check_credits` MCP tool or review your token metadata.
- **Resolution**:
  - Instruct the user to browse to `https://prepilot-system-agency.space/status` to log in and review their credit usage.
  - Redirect the user to the official WhatsApp support channel for credit refills and licensing queries:
    **Support (WhatsApp): +20 150 190 3990 — https://wa.me/201501903990**

### 3. JWT Invalid or Expired (HTTP 401 - `UNAUTHORIZED`)
- **Problem**: Client requests fail with unauthorized authentication messages.
- **Diagnostics**: Verify if the `Authorization: Bearer <token>` header contains a valid, non-expired JWT.
- **Resolution**:
  - Re-run the OAuth token exchange flow. If using Claude Desktop, open `claude_desktop_config.json` and replace the token with a freshly generated Bearer JWT.
  - Ensure the client system clock is synchronized to prevent NTP drift validation errors in `TokenVerifierMiddleware`.

### 4. Widget Rendering Failures (Blank Screen / CSP Blocks)
- **Problem**: The visual ChatKit card is blank or blocked inside ChatGPT or Claude UI.
- **Diagnostics**: Open browser developer console (F12) and inspect Content Security Policy (CSP) errors.
- **Resolution**:
  - Ensure that the Custom GPT Action schema contains `openai/widgetCSP` pointing explicitly to `https://prepilot-system-agency.space`.
  - Check that files in `Backend/app/widgets/` are served with `Content-Type: text/javascript` or `Content-Type: text/css` rather than raw `text/plain`.

### 5. State Verification Failures (HTTP 400 - `GATE_FAILED` / `WRONG_ARTIFACT`)
- **Problem**: The call to `validate_stage_gate` or `finalize_deliverable` is rejected by the server.
- **Diagnostics**: Look at the error payload returned by the FastAPI server; it will specify if the progress token is mismatched or if required checklist fields are missing.
- **Resolution**:
  - Ensure that **every** key in the stage's outline checklist is represented in `gate_checklist_json` as a boolean (do not omit keys).
  - Verify that you are passing the **latest** rotated progress token returned by the previous tool call. Stale tokens are rejected immediately.
  - Always call `get_section` for a stage before executing it to ensure full compliance with the specific stage prompt.

## Agent notes
- Keep this troubleshooting reference active in your context during development to handle API failures gracefully.
- Related pages: `docs/errors` for complete error dictionaries, `docs/recipes` for standard execution states.
- Known caveats: Running multiple parallel tool execution loops can cause race conditions on credit deduction; serialize complex chains where possible.