content-creation
This Claude Code skill provides templates and formatting guidelines for drafting marketing content across multiple channels including blog posts, social media, email newsletters, landing pages, press releases, and case studies. Use it when creating any marketing material that requires channel-specific structure, SEO optimization, audience-appropriate tone, or strategic calls to action.
git clone --depth 1 https://github.com/openyak/openyak /tmp/content-creation && cp -r /tmp/content-creation/backend/app/data/plugins/marketing/skills/content-creation ~/.claude/skills/content-creationSKILL.md
# Content Creation Skill Guidelines and frameworks for creating effective marketing content across channels. ## Content Type Templates ### Blog Post Structure 1. **Headline** — clear, benefit-driven, includes primary keyword (aim for 60 characters or less for SEO) 2. **Introduction** (100-150 words) — hook the reader with a question, statistic, bold claim, or relatable scenario. State what the post will cover. Include primary keyword. 3. **Body sections** (3-5 sections) — each with a descriptive subheading (H2). Use H3 for subsections. One core idea per section with supporting evidence, examples, or data. 4. **Conclusion** (75-100 words) — summarize key takeaways, reinforce the main message, include a call to action. 5. **Meta description** — under 160 characters, includes primary keyword, compels the click. ### Social Media Post Structure - **Hook** — first line grabs attention (question, bold statement, number) - **Body** — 2-4 concise points or a short narrative - **CTA** — what should the reader do next (comment, click, share, tag) - **Hashtags** — 3-5 relevant hashtags (platform-dependent) ### Email Newsletter Structure - **Subject line** — under 50 characters, creates curiosity or states clear value - **Preview text** — complements the subject line, does not repeat it - **Header/hero** — visual anchor and one-line value statement - **Body sections** — 2-3 content blocks, each scannable with a bold intro sentence - **Primary CTA** — one clear action per email - **Footer** — unsubscribe link, company info, social links ### Landing Page Structure - **Headline** — primary benefit in under 10 words - **Subheadline** — elaborates on the headline with supporting context - **Hero section** — headline, subheadline, primary CTA, supporting image or video - **Value propositions** — 3-4 benefit-driven sections with icons or images - **Social proof** — testimonials, logos, stats, case study snippets - **Objection handling** — FAQ or trust signals - **Final CTA** — repeat the primary call to action ### Press Release Structure - **Headline** — factual, newsworthy, under 80 characters - **Subheadline** — optional, adds context - **Dateline** — city, state, date - **Lead paragraph** — who, what, when, where, why in 2-3 sentences - **Body paragraphs** — supporting details, quotes, context - **Boilerplate** — company description (standardized) - **Media contact** — name, email, phone ### Case Study Structure - **Title** — "[Customer] achieves [result] with [product]" - **Snapshot** — customer name, industry, company size, product used, key result (sidebar or callout box) - **Challenge** — what problem the customer faced - **Solution** — what was implemented and how - **Results** — quantified outcomes with specific metrics - **Quote** — customer testimonial - **CTA** — learn more, get a demo, read more case studies ## Writing Best Practices by Channel ### Blog - Write at an 8th-grade reading level for broad audiences; adjust up for technical audiences - Use short paragraphs (2-4 sentences) - Include subheadings every 200-300 words - Use bullet points and numbered lists to break up text - Include at least one data point, example, or quote per section - Write in active voice - Front-load key information in each section ### Social Media - **LinkedIn**: professional but human, paragraph breaks for readability, personal stories and lessons perform well, 1,300 characters is the sweet spot before "see more" - **Twitter/X**: concise and punchy, strong opening words, threads for longer narratives, engage with replies - **Instagram**: visual-first captions, storytelling hooks, line breaks for readability, hashtags in first comment or at end - **Facebook**: conversational tone, questions drive comments, shorter posts (under 80 characters) get more engagement for links ### Email - Write subject lines that create urgency, curiosity, or state clear value - Personalize where possible (name, company, behavior) - One primary CTA per email — make it visually distinct - Keep body copy scannable: bold key phrases, short paragraphs, bullet points - Test everything: subject lines, send times, CTA copy, layout - Mobile-first: most email is read on mobile ### Web (Landing Pages, Product Pages) - Lead with benefits, not features - Use "you" language — speak to the reader directly - Minimize jargon unless the audience expects it - Every section should answer "so what?" from the reader's perspective - Reduce friction: fewer form fields, clear next steps, trust signals near CTAs ## SEO Fundamentals for Content ### Keyword Strategy - Identify one primary keyword and 2-3 secondary keywords per piece - Use the primary keyword in: headline, first paragraph, one subheading, meta description, URL slug - Use secondary keywords naturally in body copy and subheadings - Do not keyword-stuff — write for humans first ### On-Page SEO Checklist - Title tag: under 60 characters, includes primary keyword - Meta description: under 160 characters, includes primary keyword, compels click - URL slug: short, descriptive, includes primary keyword - H1: one per page, matches or closely reflects the title tag - H2/H3: descriptive, include secondary keywords where natural - Image alt text: descriptive, includes keyword where relevant - Internal links: 2-3 links to related content on your site - External links: 1-2 links to authoritative sources ### Content-SEO Integration - Aim for comprehensive coverage of the topic (search engines reward depth) - Answer related questions (check "People Also Ask" for ideas) - Update and refresh high-performing content regularly - Structure content for featured snippets: definition paragraphs, numbered lists, tables ## Headline and Hook Formulas ### Headline Formulas - **How to [achieve result] [without common obstacle]** — "How to Double Your Email Open Rates Without Sending More Emails" - **[Number] [adjective] ways to [achieve result]** — "7 Proven Ways to Reduce Customer Churn" - **Why [common be
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full ASM JSON, flattened CSV for easy import, and exportable Python code for data engineers. Common triggers include converting instrument files, standardizing lab data, preparing data for upload to LIMS/ELN systems, or generating parser code for production pipelines.
Run nf-core bioinformatics pipelines (rnaseq, sarek, atacseq) on sequencing data. Use when analyzing RNA-seq, WGS/WES, or ATAC-seq data—either local FASTQs or public datasets from GEO/SRA. Triggers on nf-core, Nextflow, FASTQ analysis, variant calling, gene expression, differential expression, GEO reanalysis, GSE/GSM/SRR accessions, or samplesheet creation.
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
Deep learning for single-cell analysis using scvi-tools. This skill should be used when users need (1) data integration and batch correction with scVI/scANVI, (2) ATAC-seq analysis with PeakVI, (3) CITE-seq multi-modal analysis with totalVI, (4) multiome RNA+ATAC analysis with MultiVI, (5) spatial transcriptomics deconvolution with DestVI, (6) label transfer and reference mapping with scANVI/scArches, (7) RNA velocity with veloVI, or (8) any deep learning-based single-cell method. Triggers include mentions of scVI, scANVI, totalVI, PeakVI, MultiVI, DestVI, veloVI, sysVI, scArches, variational autoencoder, VAE, batch correction, data integration, multi-modal, CITE-seq, multiome, reference mapping, latent space.
Performs quality control on single-cell RNA-seq data (.h5ad or .h5 files) using scverse best practices with MAD-based filtering and comprehensive visualizations. Use when users request QC analysis, filtering low-quality cells, assessing data quality, or following scverse/scanpy best practices for single-cell analysis.
Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.
>
>