cv-content-generator
About
This skill generates new CV portfolio content like case studies and blog posts by querying a knowledge base. It activates when users need to create content from their experience or produce job-specific variants. Key capabilities include structured output generation and integration with variant workflows.
Quick Install
Claude Code
Recommended/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/cv-content-generatorCopy and paste this command in Claude Code to install this skill
Documentation
CV Content Generator
<purpose> Generate new content for the Universal CV portfolio by querying the knowledge base and producing structured output ready for the portfolio. </purpose><when_to_activate> Activate 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 (redirect to
generate-variantfor full workflow) - Needs to update experience highlights
- Asks for content based on achievements or stories
Trigger phrases: "create case study", "write blog post", "new content", "generate [content type]" </when_to_activate>
<edge_cases>
| Scenario | Action |
|---|---|
| Full variant generation | Redirect to generate-variant skill for complete pipeline |
| Missing knowledge base data | Run cv-data-ingestion first |
| Content editing (not creation) | Use cv-content-editor instead |
| Writing style needed | Invoke dmitrii-writing-style before generating prose |
| </edge_cases> |
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 forcontent/case-studies/blog-post→ Markdown with frontmatter forcontent/blog/variant→ YAML overrides forcontent/variants/experience-update→ YAML additions forcontent/experience/
Step 2: Query Knowledge Base
Use deterministic scripts first — faster and more consistent:
# Search by topic
npm run search:evidence -- --terms "revenue,growth,api"
# For variant generation with JD analysis
npm run analyze:jd -- --file source-data/jd-{company}.txt --save
npm run search:evidence -- --jd-analysis capstone/develop/jd-analysis/{slug}.yaml
For deeper exploration:
- Read
content/knowledge/index.yamlfor 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.yamlfor 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"
⚠️ For full variant workflow, use the generate-variant skill instead.
Quick variant with scripts:
# 1. Analyze the JD
npm run analyze:jd -- --file source-data/jd-stripe.txt --save
# 2. Search for matching evidence
npm run search:evidence -- --jd-analysis capstone/develop/jd-analysis/stripe.yaml
# 3. Check bullet coverage
npm run check:coverage
Action (manual):
- 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:
- All metrics are specific and quantified
- STAR format is complete (Situation, Task, Action, Result)
- Key quote/insight is memorable
- Tags align with knowledge base themes
- Frontmatter validates against schema
GitHub Repository
Related Skills
algorithmic-art
MetaThis Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
executing-plans
DesignUse the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
cost-optimization
OtherThis Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.
