Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use this skill when a file has been uploaded but its content is NOT in your context — only its path at /mnt/user-data/uploads/ is listed in an uploaded_files block. This skill is a router: it tells you which tool to use for each file type (pdf, docx, xlsx, csv, json, images, archives, ebooks) so you read the right amount the right way instead of blindly running cat on a binary. Triggers: any mention of /mnt/user-data/uploads/, an uploaded_files section, a file_path tag, or a user asking about an uploaded file you have not yet read. Do NOT use this skill if the file content is already visible in your context inside a documents block — you already have it.
Use this skill when you need to read, inspect, or extract content from PDF files — especially when file content is NOT in your context and you need to read it from disk. Covers content inventory, text extraction, page rasterization for visual inspection, embedded image/attachment/table/form-field extraction, and choosing the right reading strategy for different document types (text-heavy, scanned, slide-decks, forms, data-heavy). Do NOT use this skill for PDF creation, form filling, merging, splitting, watermarking, or encryption — use the pdf skill instead.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Run this skill whenever the user wants to analyze competitors, understand the competitive landscape, find market gaps, or position their product against others. Trigger on phrases like "who are my competitors", "competitive analysis", "how do I differentiate", "what's the competition doing", "competitor mapping", "market positioning", "where's the gap in the market", or "how do I stand out". Produces a senior analyst-level competitive intelligence report with positioning maps, moat analysis, and strategic recommendations.
Generates a complete Cursor AI IDE project starter kit — 7 documents — from a brainstorming conversation with the user. Use this skill whenever the user wants to start a new project, says "let's start a new project", "I have a project idea", "help me plan a new app/system/tool", "set up my Cursor project", or wants to brainstorm and immediately get working project files. Also trigger when the user says things like "I want to build X from scratch" or "help me plan out X before I start coding". Always use this skill proactively when a new project is being initiated — don't wait for the user to ask for documentation explicitly.
Run this skill whenever the user wants to map the customer experience, understand touchpoints, identify where users drop off, reduce churn, or improve retention. Trigger on phrases like "customer journey", "user journey", "where do I lose customers", "touchpoint mapping", "funnel analysis", "customer lifecycle", "why do customers churn", "onboarding experience", "retention problem", or "map the experience". Produces a McKinsey-style 7-stage customer journey map with emotional curve, churn signals, and delight opportunities.