Claude Code Skills Pack

Claude Code Skills Pack — Content Creator Edition

By cloudwithsingh.ca

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've got an AI-powered content machine.

---

What's 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 + 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 + 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 + Buffer	buffer.com/developers
BUFFER_LINKEDIN_PROFILE_ID	LinkedIn + Buffer	Auto-discovered on first run (see skill)
NOTION_API_KEY	Content Writing + Notion	notion.so/my-integrations
NOTION_CONTENT_DB_ID	Content Writing + 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 → n8n publishes to WordPress + cross-posts to Dev.to + tweets a thread
• Draft social content → n8n schedules it across LinkedIn, Twitter, and Instagram
• Create a newsletter → n8n sends it via ConvertKit/Mailchimp

Includes:

• 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 + 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

Includes:

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

---

Content Writing + 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's coming up
• Batch-create content entries for planning

Includes:

• 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/Stack Overflow
• Audit competitor content to find gaps you can fill
• Generate a keyword-backed content brief with recommended angles

Includes:

• 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 don't require any code installation — they're just .md files
• Each skill is self-contained with its own prerequisites and troubleshooting
• Skills can chain together (e.g., 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 table at the bottom. Common customizations:

• Voice and tone: Edit the writing guidelines to match your brand
• Post templates: Add your own LinkedIn/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               ← You are here
├── LICENSE                  ← MIT License
├── .env.example             ← Template for required environment variables
└── skills/
    ├── n8n-automation.md           ← n8n webhook automation skill
    ├── linkedin-buffer.md          ← LinkedIn posting via Buffer
    ├── content-writing-notion.md   ← Content writing with Notion integration
    └── content-research.md         ← Topic research and content briefs

---

Contributing

Found a bug? Have a skill idea? PRs welcome.

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

---

License

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

---

Built by cloudwithsingh.ca