Insight · April 25, 2026 · 7 min read

Claude Skills

Claude Code Skills Pack — Content Creator Edition

A collection of ready to use Claude Code skills for content creators, indie hackers, and solo operators who want to automate their content pipeline from the terminal.

Each skill is a standalone .md file that teaches Claude Code how to perform a specific workflow. Copy them into your project, customize the variables, and you have an AI powered content machine.

What is inside

Skill	File	What it does
n8n Automation	`skills/n8n-automation.md`	Trigger n8n workflows from Claude Code. Distribute content to multiple platforms via webhook. Includes starter workflow JSON.
LinkedIn and Buffer	`skills/linkedin-buffer.md`	Draft LinkedIn posts (single, carousel, batch) and schedule them directly to Buffer. Includes post templates and batch queueing.
Content Writing and Notion	`skills/content-writing-notion.md`	Write blog posts and articles, then push drafts to a Notion database with full metadata. Manage an editorial calendar.
Content Research	`skills/content-research.md`	Research any topic — web search, community mining, competitor audit, keyword data — and produce a structured research brief.

Quick start

1. Clone the repo

git clone https://github.com/YOUR_USERNAME/claude-code-skills-pack.git

2. Copy skills into your project

Claude Code loads skills from your project's .claude/skills/ directory, or you can reference them from anywhere.

Option A — Copy into your project:

mkdir -p your-project/.claude/skills
cp claude-code-skills-pack/skills/*.md your-project/.claude/skills/

Option B — Symlink (keeps skills updated when you pull):

ln -s /path/to claude-code-skills-pack/skills your-project/.claude/skills

Option C — Reference directly in CLAUDE.md:
Add to your project's CLAUDE.md:

## Skills
Load skills from: /path/to/claude-code-skills-pack/skills/

3. Set up environment variables

Copy the example env file and fill in your values:

cp .env.example .env
# Edit .env with your actual tokens
source .env

4. Use the skills

Open Claude Code in your project and invoke skills naturally:

> research kubernetes security best practices
> write a blog post about API gateway patterns and save it to Notion
> draft a LinkedIn post about my latest project and schedule it for Monday
> send this content to n8n for distribution

Environment variables

Each skill needs specific API tokens. Set only the ones for skills you use.

Variable	Required for	Where to get it
`N8N_WEBHOOK_URL`	n8n Automation	Your n8n instance → Webhook node URL
`N8N_API_KEY`	n8n Automation (optional)	n8n Settings → API Keys
`BUFFER_ACCESS_TOKEN`	LinkedIn and Buffer	buffer.com/developers
`BUFFER_LINKEDIN_PROFILE_ID`	LinkedIn and Buffer	Auto discovered on first run (see skill)
`NOTION_API_KEY`	Content Writing and Notion	notion.so/my-integrations
`NOTION_CONTENT_DB_ID`	Content Writing and Notion	From your Notion database URL

Skill details

n8n Automation

Connects Claude Code to your n8n instance via webhooks. You write the content in Claude Code, and n8n handles the distribution.

Use cases:

Write a blog post and n8n publishes to WordPress, cross posts to Dev.to, and tweets a thread
Draft social content and n8n schedules it across LinkedIn, Twitter, and Instagram
Create a newsletter and n8n sends it via ConvertKit or Mailchimp

What is included:

Standard webhook payload schema (build your n8n workflows once, reuse forever)
Starter n8n workflow JSON you can import directly
Recommended n8n workflow architectures for content pipelines

LinkedIn and Buffer

Draft LinkedIn posts with proven templates and schedule them through Buffer's API — no browser needed.

Use cases:

Write and schedule a single LinkedIn post
Batch create a week's worth of posts in one session
Build carousel slide content
Check your Buffer queue status

What is included:

Post format templates (Lesson Learned, How To, Hot Take, Carousel)
LinkedIn best practices for hook, length, hashtags, and CTA
Batch posting workflow for weekly content planning
Buffer API commands for queue management

Content Writing and Notion

Full content writing pipeline from brief to outline to draft to Notion. Claude writes it, Notion manages it.

Use cases:

Write a blog post from a topic and push the draft to Notion
Create content outlines and track them through Draft → Review → Published
Query your editorial calendar to see what is coming up
Batch create content entries for planning

What is included:

Content brief framework
Structured outline templates
Markdown to Notion block conversion (headings, code, lists, quotes)
Editorial calendar query commands
Status update commands for pipeline management

Content Research

Research any topic before writing. Pulls from web search, developer communities, competitor sites, and optionally Ahrefs keyword data.

Use cases:

Research a topic before writing a blog post
Find out what questions your audience is asking on Reddit or Stack Overflow
Audit competitor content to find gaps you can fill
Generate a keyword backed content brief with recommended angles

What is included:

Multi source research workflow (web, Reddit, HN, Stack Overflow, Dev.to)
Competitor content audit framework
Research brief template with sources and angles
Three depth levels: Quick Scan, Standard, Deep Dive

How skills work in Claude Code

Skills are markdown files that act as specialized prompts. When you invoke a skill (either through a slash command or by describing what you want), Claude Code reads the skill file and follows its workflow.

Think of each skill as a runbook that Claude follows — it knows what to ask you, what APIs to call, and how to format the output.

Key points:

Skills do not require any code installation — they are just .md files
Each skill is self contained with its own prerequisites and troubleshooting
Skills can chain together (for example: research → write → publish to Notion → distribute via n8n)
You can customize any skill by editing the markdown

Customizing skills

Every skill has a Customization Points section at the bottom. Common customizations:

Voice and tone — Edit the writing guidelines to match your brand
Post templates — Add your own LinkedIn and social templates
Database schema — Adjust Notion properties to match your setup
Webhook payloads — Add custom fields for your n8n workflows
Research sources — Add niche specific communities or sites

Chaining skills together

The real power is combining skills in a single session:

> research "serverless cold starts" deep dive
> now write a blog post using that research, save to Notion
> also draft a LinkedIn post summarizing the key takeaway, schedule for Tuesday
> send the blog post to n8n for cross posting

Each skill builds on the output of the previous one. The research brief informs the blog post, the blog post informs the LinkedIn summary, and everything flows through your automation pipeline.

Project structure

claude-code-skills-pack/
├── README.md
├── LICENSE
├── .env.example
└── skills/
    ├── n8n-automation.md
    ├── linkedin-buffer.md
    ├── content-writing-notion.md
    └── content-research.md

Contributing

Found a bug or have a skill idea? Pull requests are welcome.

Fork the repo
Create a new skill in skills/your-skill-name.md
Follow the existing skill structure (When to Use, Prerequisites, Workflow, Customization, Troubleshooting)
Submit a PR

License

MIT — use it, fork it, sell it, whatever. Just build cool stuff.

Built by cloudwithsingh.ca

Read this article as markdown