| name | cv-content-generator |
| description | Generate case studies, blog posts, experience updates, and variant content from the knowledge base. Use when user wants to create new CV content, write articles, or generate job-specific variants. |
CV Content Generator
Overview
This skill generates new content for the Universal CV portfolio by querying the knowledge base (content/knowledge/) and producing structured output ready for the portfolio.
When Claude Should Use This
Activate this skill when the user:
- Wants to write a new case study
- Needs to create a blog post from experience
- Wants to generate a job-specific variant
- Needs to update experience highlights
- Asks for content based on achievements or stories
Knowledge Base Structure
content/knowledge/
โโโ index.yaml # Entities and relationships graph
โโโ achievements/ # Atomic accomplishments (STAR format)
โโโ stories/ # Extended narratives
โโโ metrics/ # Quantified results
โโโ raw/ # Unstructured source material
Content Generation Workflow
Step 1: Understand the Request
Determine output type:
case-study โ Full markdown with frontmatter for content/case-studies/blog-post โ Markdown with frontmatter for content/blog/variant โ YAML overrides for content/variants/experience-update โ YAML additions for content/experience/
Step 2: Query Knowledge Base
- Read
content/knowledge/index.yaml for entity definitions and relationships
- Find relevant achievements in
content/knowledge/achievements/
- Find related stories in
content/knowledge/stories/
- Cross-reference themes and skills for comprehensive context
Step 3: Generate Content
For Case Studies
Use this structure:
---
id: [next number]
slug: [kebab-case-slug]
title: [Title]
company: [Company]
year: [Year]
tags: [relevant tags]
duration: [duration]
role: [role]
hook:
headline: [3-second grab]
impactMetric:
value: "[X]"
label: [metric type]
subMetrics:
- value: "[Y]"
label: [secondary metric]
thumbnail: null
cta:
headline: [Call to action question]
subtext: [Supporting text]
action: calendly
linkText: Let's talk โ
---
[Opening hook - why this matters, stakes involved]
## The Challenge
[Problem statement with constraints]
## The Approach
[Hypothesis and alternatives considered table]
## Key Decision
[Critical decision point with trade-offs]
## Execution
[Phases with specific actions]
## Results
[Quantified outcomes]
## What I Learned
[Reflections - what worked, what didn't, key quote]
For Blog Posts
---
slug: [slug]
title: [Title]
date: [YYYY-MM-DD]
tags: [tags]
excerpt: [1-2 sentence summary]
---
[Content following narrative structure from stories]
For Variants
metadata:
company: "[Company]"
role: "[Role]"
slug: "[company-role]"
generatedAt: "[ISO timestamp]"
jobDescription: "[JD summary]"
overrides:
hero:
status: "[Customized status]"
subheadline: "[Tailored pitch]"
about:
tagline: "[Role-specific tagline]"
bio: [Customized paragraphs]
stats: [Relevant stats]
relevance:
caseStudies:
- slug: "[most relevant]"
relevanceScore: 0.95
reasoning: "[Why this matters for role]"
Step 4: Validate Output
- Check all required frontmatter fields
- Ensure metrics are quantified
- Verify skills/themes match knowledge base
- Confirm narrative follows STAR format
Examples
Example 1: Generate Case Study
User: "Create a case study about the Ankr revenue growth"
Action:
- Read
content/knowledge/achievements/ankr-15x-revenue.yaml
- Read
content/knowledge/index.yaml for Ankr relationships
- Generate full case study markdown
- Output to
content/case-studies/ with proper frontmatter
Example 2: Generate Variant
User: "Create a variant for a Technical PM role at Stripe"
Action:
- Query achievements with themes:
[infrastructure, revenue-growth]
- Find skills:
[api-design, compliance]
- Customize hero/about with payments/fintech angle
- Score case studies by relevance to Stripe's domain
- Output YAML + JSON variant files
Output Locations
| Content Type | Output Path | Format |
|---|
| Case Study | content/case-studies/[##-slug].md | Markdown |
| Blog Post | content/blog/[date-slug].md | Markdown |
| Variant | content/variants/[company-role].yaml | YAML + JSON |
| Experience | content/experience/index.yaml | YAML (append) |
Quality Checklist
Before outputting content:
