Help us improve
Share bugs, ideas, or general feedback.
From tigerdata-marketing-skills
Create Tiger Data case study interview prep documents. Gathers customer information via DM to the @eon Slack bot and user-provided Google Docs, then aligns all known information against the 8 standard Tiger Data Case Study Questions, producing a .docx with status ratings (Complete/Partial/Missing), draft answers, gap analysis, a 30-minute interview guide, and draft pull quotes. MANDATORY TRIGGERS: case study, interview prep, case study prep, customer story, customer interview, case study questions, ClickHouse takeout, competitive win story. Use when the user asks to prepare for a customer case study interview, create a case study prep doc, or align existing customer notes against the Tiger Data case study questions template.
npx claudepluginhub timescale/marketing-skills --plugin tigerdata-marketing-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/tigerdata-marketing-skills:case-study-prepThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produce a .docx case study prep document for a given customer by gathering all available
Generates customer case studies and success stories using interview guides, StoryBrand structure, metrics validation, and publish-ready format. Activates for 'write a case study' or customer success requests.
Generates PPTX case study presentations from raw data like transcripts, notes, or interviews. Collaboratively extracts narrative, validates sections, applies brand styles, and renders slides using PptxGenJS.
Generates scannable HTML account dossiers and call prep documents for internal sales use from company domains, person emails, or contexts, tailored to occasions like discovery, demo, or QBR.
Share bugs, ideas, or general feedback.
Produce a .docx case study prep document for a given customer by gathering all available information and aligning it to the 8 Tiger Data Case Study Questions.
Read REFERENCES.md from the plugin root and run the pre-flight check described there. Call list_marketing_references() to verify Tiger Den is reachable. If it fails or the tool is not found, STOP — do not continue. Follow the error handling in REFERENCES.md.
Also fetch the No Fly List before doing any work:
get_marketing_reference(slug: "no-fly-list")
This is a list of customers who cannot be publicly referenced. If the customer you are preparing a case study for appears on the No Fly List, stop immediately and inform the user that this customer cannot be publicly referenced. If a No Fly List name appears in source material you are working from, omit it from all outputs.
Determine from the user:
Read CONFIG.md from the plugin root to get the current eon bot user ID.
channel_id): Summarize current use case and metrics for customer {Company Name}message_ts and channel_id from the send responsechannel_id and message_ts to capture eon's responseFetch all user-provided Google Docs using google_drive_fetch. Also read any uploaded files.
Before generating the document, fetch the two reference docs from Tiger Den:
get_marketing_context(slugs: ["case-study-questions", "case-study-output-format"])
case-study-questions — the 8 standard Tiger Data Case Study Questionscase-study-output-format — document structure and styling for the prep docIf Tiger Den is not connected, do not proceed — tell the user to run /setup. See REFERENCES.md in the plugin root for details and error handling.
Also read the docx skill for .docx generation best practices (critical for correct docx-js usage).
For each of the 8 case study questions:
Create a Word document using docx-js following the structure in case-study-output-format:
Save to the outputs folder as {Company}_Case_Study_Prep.docx.
Validate with the docx skill's validate.py script.
Share the document link and a quick summary showing each question's status at a glance.