← ClaudeAtlas

consulting-decklisted

Build business/IT consulting slide decks the way a strategy consultant builds them — framework-driven narrative, message-first slide titles, every number sourced, and a disciplined, brand-neutral visual system you can skin with your own identity. Use this skill whenever the user asks for a consulting deck, market research report, industry analysis, competitive landscape, PEST/SWOT/4P/value-chain analysis, digital transformation or AI proposal, bidding/pitch deck, client-facing PPT, "外部调研报告", "行业分析", "投标方案", or wants an existing deck restructured, condensed, or made presentable. Also use it when the user has raw evidence (screenshots, interview notes, survey exports, scraped data) and needs it turned into slides, or when they ask to "make this deck less cluttered", "combine these pages", or "make this look professional". Trigger even if they never say the word "consulting" — if the deliverable is a .pptx that has to persuade a client or an executive, this is the skill.
BotTony329/consulting-deck-skill · ★ 1 · Data & Documents · score 72
Install: claude install-skill BotTony329/consulting-deck-skill
# Consulting Deck You are building the kind of deck that gets shown to a client's leadership team. That context drives everything: the audience is impatient, skeptical, and will ask "says who?" about every number. A deck that survives that room has a spine, states its conclusions out loud, and shows its sources. This skill encodes a specific working style, extracted from real strategy-consulting engagement decks. Follow it rather than inventing your own structure — the conventions here are what make consecutive slides feel like one argument instead of a pile of pages. ## When to use this skill Use it when the requested deliverable is an editable, executive-facing PowerPoint whose argument, evidence, and visual hierarchy matter: a consulting analysis, proposal, pitch, research report, recommendation, transformation case, or substantial rewrite of an existing deck. Do not use it for a casual image slideshow, a document or spreadsheet, a request for a static design mock-up only, or a task where the user explicitly wants a different presentation system or a non-editable output. ## Inputs and local setup Before building, obtain or state assumptions for the audience, decision, objective, core question, final message, evidence standard, visual identity, language, desired length, output path, and any source files. Treat supplied files as local user data: read only what the task needs, never upload confidential material without explicit approval, do not overwrite source files, a