cook-the-blog

Name: cook-the-blog
Author: Varnan-Tech

22installs59forks

How to install cook-the-blog?

varnan-tech/opendirectory/cook-the-blog

$npx -y skills add Varnan-Tech/opendirectory --skill cook-the-blog

Installs into the current project.

Summary

Generate high-converting, deep-dive growth case studies in MDX format. Use this skill when asked to write a case study or blog post about a company's growth, tech stack, or product-led strategy. It handles the full pipeline (researching the company via Tavily, generating a 16:9 c

Files · 1

View on GitHub

SKILL.md

1	# cook-the-blog Workflow
2
3	Follow these steps exactly when asked to generate a case study for a company.
4
5	MANDATORY SETUP CHECK: Before starting, ensure you have the required environment variables and target destinations configured (Target Repo, Image Bucket/Storage, Author Email, etc.). If any are missing, STOP and ask the user for them.
6
7	MANDATORY QA CHECK AT EACH STEP: After completing every single step below, you MUST perform a strict, self-critical QA check. If a step fails or is hallucinated, you MUST retry until it succeeds. Do not fake success.
8
9	## 1. Deep Research (Tavily)
10	- Use the `tavily` tool (via MCP) and standard web searches to deeply research the company. Note: Always check if the registered business name differs from the product name. Search Reddit and other relevant forums for authentic developer insights.
11	- QA Tester: Did you actually extract real, hard metrics and specific details about their GTM strategy, or is it generic fluff? If fluff, research deeper.
12
13	## 2. SEO Keyword Research (Google Trends via SerpApi)
14	- Run the python script: `export SERPAPI_KEY="[YOUR_SERPAPI_KEY]" && python3 [PATH_TO_SEO_SCRIPT] "[Company Name]"`
15	- Identify the breakout and high-growth keywords from the output.
16	- QA Tester: Did the script succeed? Are the keywords real and high-volume? If not, retry or adjust the query.
17
18	## 3. Title & Cover Generation
19	- Title: Format: `"How [Company] [Achieved X] by [Core Strategy]"`. Make it specific and highly descriptive.
20	- Cover: Use the `blog-cover-cli generate` command to generate the cover image. CRITICAL: The title passed to the cover image generator using the `-t` flag should contain around 7-10 words total. Do NOT use newlines (`\n`) in the string. Just provide a normal, single-line string and let the CLI handle the text wrapping automatically! Write a concise, aggressive title (e.g., `blog-cover-cli generate -t "How Baseten Scaled AI Infrastructure To a 5 Billion Valuation" -l "domain.com" -o "./cover.png"`).
21	- QA Tester: Was the image actually generated and saved? Verify the file exists.
22
23	## 4. MDX Assembly
24	Synthesize the research and write the case study in a strict MDX format.
25	Writing Rules (Use the `stop-slop` skill):
26	- Tone: Sharp, analytical, founder-focused. No fluff. Every sentence should teach something.
27	- Audience: Early-stage startup founders, AI/developer tool builders, product-led growth enthusiasts.
28	- Length: 1,200-1,800 words.
29	- POV: Third-person analysis, like a smart investor memo written for a builder audience.
30	- Do not ever use em-dashes (—).
31	- Always use simple and conversational English with connector words. Avoid corporate jargon ("synergy," "leverage," "ecosystem play," "disruption" -> replace with plain language).
32	- Every claim must feel backed by evidence or logic. Use specific numbers.
33	- Each H3 sub-section should start with a concept sentence, then explain the mechanism, then give 1 example.
34	- Do not repeat the title in the MDX body. The title should only exist in the frontmatter. Do NOT include an `<h1>` or `# [Title]` just before the TL;DR.
35	- Never write a conclusion section. End on the takeaway paragraph or the FAQ.
36
37	The MDX must follow this exact structure:
38
39	```mdx
40	---
41	title: "How [Company] [Achieved X] by [Core Strategy]"
42	description: "[1-2 sentence compelling summary with hard numbers]"
43	date: "YYYY-MM-DD"
44	slug: "[URL-friendly-slug-e.g.-company-name-case-study]"
45	image: "[PUBLIC_IMAGE_URL]"
46	readingTime: "[X] Min"
47	published: true
48	---
49
50	<div style={{ textAlign: 'left' }}>
51
52	TL;DR
53	* Challenge: [The core painful problem in the market they addressed]
54	* Solution: [What they specifically built or did differently]
55	* Results: [2–3 hard metrics — downloads, revenue, users, growth %]
56	* Investment/Strategy: [The one key strategic bet they made]
57
58	## The Problem
59	[Paint the before-state: What was the world like before this company's solution? Who was suffering, and what were they forced to do instead? Make it visceral use developer/founder language. Length: 2-3 paragraphs. No bullet points.]
60
61	## The Execution & GTM Strategy
62	[Break into 2–4 H3 sub-sections picking from: a) THE DISTRIBUTION STRATEGY, b) THE MONETIZATION LAYER, c) THE TECHNICAL / PRODUCT MOAT, d) THE INTERNAL DOGFOODING MOMENT, e) THE TIMING INSIGHT]
63	### [H3 Sub-section]
64	[Concept sentence. Mechanism. 1 Example.]
65
66	## The Results & Takeaways
67	[3–5 hard metrics in bullet points (downloads, revenue, customers, conversions, time saved)]
68
69	**What a small sta

People who liked this also viewed

6 picks

Type

cook-the-blog

22installs59forks

View on GitHub

How to install cook-the-blog?

varnan-tech/opendirectory/cook-the-blog

$npx -y skills add Varnan-Tech/opendirectory --skill cook-the-blog

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# cook-the-blog Workflow
2
3	Follow these steps exactly when asked to generate a case study for a company.
4
5	MANDATORY SETUP CHECK: Before starting, ensure you have the required environment variables and target destinations configured (Target Repo, Image Bucket/Storage, Author Email, etc.). If any are missing, STOP and ask the user for them.
6
7	MANDATORY QA CHECK AT EACH STEP: After completing every single step below, you MUST perform a strict, self-critical QA check. If a step fails or is hallucinated, you MUST retry until it succeeds. Do not fake success.
8
9	## 1. Deep Research (Tavily)
10	- Use the `tavily` tool (via MCP) and standard web searches to deeply research the company. Note: Always check if the registered business name differs from the product name. Search Reddit and other relevant forums for authentic developer insights.
11	- QA Tester: Did you actually extract real, hard metrics and specific details about their GTM strategy, or is it generic fluff? If fluff, research deeper.
12
13	## 2. SEO Keyword Research (Google Trends via SerpApi)
14	- Run the python script: `export SERPAPI_KEY="[YOUR_SERPAPI_KEY]" && python3 [PATH_TO_SEO_SCRIPT] "[Company Name]"`
15	- Identify the breakout and high-growth keywords from the output.
16	- QA Tester: Did the script succeed? Are the keywords real and high-volume? If not, retry or adjust the query.
17
18	## 3. Title & Cover Generation
19	- Title: Format: `"How [Company] [Achieved X] by [Core Strategy]"`. Make it specific and highly descriptive.
20	- Cover: Use the `blog-cover-cli generate` command to generate the cover image. CRITICAL: The title passed to the cover image generator using the `-t` flag should contain around 7-10 words total. Do NOT use newlines (`\n`) in the string. Just provide a normal, single-line string and let the CLI handle the text wrapping automatically! Write a concise, aggressive title (e.g., `blog-cover-cli generate -t "How Baseten Scaled AI Infrastructure To a 5 Billion Valuation" -l "domain.com" -o "./cover.png"`).
21	- QA Tester: Was the image actually generated and saved? Verify the file exists.
22
23	## 4. MDX Assembly
24	Synthesize the research and write the case study in a strict MDX format.
25	Writing Rules (Use the `stop-slop` skill):
26	- Tone: Sharp, analytical, founder-focused. No fluff. Every sentence should teach something.
27	- Audience: Early-stage startup founders, AI/developer tool builders, product-led growth enthusiasts.
28	- Length: 1,200-1,800 words.
29	- POV: Third-person analysis, like a smart investor memo written for a builder audience.
30	- Do not ever use em-dashes (—).
31	- Always use simple and conversational English with connector words. Avoid corporate jargon ("synergy," "leverage," "ecosystem play," "disruption" -> replace with plain language).
32	- Every claim must feel backed by evidence or logic. Use specific numbers.
33	- Each H3 sub-section should start with a concept sentence, then explain the mechanism, then give 1 example.
34	- Do not repeat the title in the MDX body. The title should only exist in the frontmatter. Do NOT include an `<h1>` or `# [Title]` just before the TL;DR.
35	- Never write a conclusion section. End on the takeaway paragraph or the FAQ.
36
37	The MDX must follow this exact structure:
38
39	```mdx
40	---
41	title: "How [Company] [Achieved X] by [Core Strategy]"
42	description: "[1-2 sentence compelling summary with hard numbers]"
43	date: "YYYY-MM-DD"
44	slug: "[URL-friendly-slug-e.g.-company-name-case-study]"
45	image: "[PUBLIC_IMAGE_URL]"
46	readingTime: "[X] Min"
47	published: true
48	---
49
50	<div style={{ textAlign: 'left' }}>
51
52	TL;DR
53	* Challenge: [The core painful problem in the market they addressed]
54	* Solution: [What they specifically built or did differently]
55	* Results: [2–3 hard metrics — downloads, revenue, users, growth %]
56	* Investment/Strategy: [The one key strategic bet they made]
57
58	## The Problem
59	[Paint the before-state: What was the world like before this company's solution? Who was suffering, and what were they forced to do instead? Make it visceral use developer/founder language. Length: 2-3 paragraphs. No bullet points.]
60
61	## The Execution & GTM Strategy
62	[Break into 2–4 H3 sub-sections picking from: a) THE DISTRIBUTION STRATEGY, b) THE MONETIZATION LAYER, c) THE TECHNICAL / PRODUCT MOAT, d) THE INTERNAL DOGFOODING MOMENT, e) THE TIMING INSIGHT]
63	### [H3 Sub-section]
64	[Concept sentence. Mechanism. 1 Example.]
65
66	## The Results & Takeaways
67	[3–5 hard metrics in bullet points (downloads, revenue, customers, conversions, time saved)]
68
69	**What a small sta

People who liked this also viewed

6 picks

Type