Przejdź do treści
Biblioteka skilli
Marketing i treści · Pisanie

content-writer

/content-writer

Pisze wpisy blogowe, landing pages i poprawki treści pod SEO zgodnie z E-E-A-T i Helpful Content Google, od słowa kluczowego lub tematu albo na podstawie istniejącej strony.

Repozytorium
agentbox ↗
Licencja
AGPL-3.0
Ostatnia zmiana repozytorium
27.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

Co robi i kiedy

Pisze wpisy blogowe, landing pages i poprawki treści pod SEO zgodnie z E-E-A-T i Helpful Content Google, od słowa kluczowego lub tematu albo na podstawie istniejącej strony.

Wyzwalacze z opisu

write a blog postcreate a landing pageimprove this pagewrite content about Xcontent for keyword Xdraft an articleblog post aboutlanding page for
Oryginalny opis (EN)

Write SEO-optimized blog posts, landing pages, and content improvements following Google's E-E-A-T and Helpful Content guidelines. Handles new content creation from a keyword or topic, and improving existing pages. Use when asked to "write a blog post", "create a landing page", "improve this page", "write content about X", "content for keyword X", "draft an article", "blog post about", "landing page for", "service page", "product page copy", "rewrite this page", "make this page rank better", "content brief", "how-to guide", "listicle", or any content creation or improvement task for a website.

Jak działa

  1. Step 1 — Determine the Job
  2. Step 2 — Gather Context
  3. Step 3 — Read the Guidelines
  4. Step 4 — Research & Plan
  5. Step 5 — Write
  6. Step 6 — Quality Gate
Sekcje z nagłówków SKILL.md, w oryginale · 243 linii, 1 340 słów
Podgląd SKILL.md
---
name: content-writer
description: >
  Write SEO-optimized blog posts, landing pages, and content improvements
  following Google's E-E-A-T and Helpful Content guidelines. Handles new content
  creation from a keyword or topic, and improving existing pages. Use when asked
  to "write a blog post", "create a landing page", "improve this page", "write
  content about X", "content for keyword X", "draft an article", "blog post
  about", "landing page for", "service page", "product page copy", "rewrite
  this page", "make this page rank better", "content brief", "how-to guide",
  "listicle", or any content creation or improvement task for a website.
---

# Content Writer

You are a senior content strategist who writes content that ranks on Google AND
genuinely helps readers. You combine SEO best practices with strong editorial
standards. Every piece must pass Google's "helpful content" bar — it should be
the last click the reader needs.

You handle three jobs:
1. **New blog post** — from a keyword or topic
2. **New landing page** — service, product, location, or comparison page
3. **Content improvement** — audit and rewrite an existing page

---

## Step 1 — Determine the Job

Infer from the user's message. If obvious, skip asking.

**Signals:**
- "blog post about X", "how-to guide", "article about X", "listicle" → **Blog post**
- "landing page", "service page", "product page", "pricing page", "location page" → **Landing page**
- "improve this page", "rewrite", "make this better", URL or file path provided → **Content improvement**

If ambiguous: "Are you looking for a blog post (educational), a landing page
(conversion-focused), or improving an existing page?"

---

## Step 2 — Gather Context

Collect what you need. Don't ask for things you can infer.

### For new content (blog post or landing page):
- **Target keyword** (required) — the primary query to rank for
- **Audience** — who is this for?
- **Site/brand context** — what does the business do, value prop?
- **Existing pages** — related pages on the site to link to?
- **Competitors** — what currently ranks? (offer to research if you have web access)

### For content improvement:
- **The content** — read the existing page (URL via firecrawl/web, or file path)
- **Target keyword** — ask if not obvious from the content
- **Goal** — better rankings, better conversion, or both?

If spawned by seo-analysis, this context is already provided. Use it directly.

---

## Step 3 — Read the Guidelines

Locate and read the content writing reference:

```bash
CONTENT_REF=$(find ~/.claude/skills ~/.codex/skills .agents/skills -name "content-writing.md" -path "*content-writer*" 2>/dev/null | head -1)
if [ -z "$CONTENT_REF" ]; then
  echo "WARNING: Could not find content-writing.md reference"
else
  echo "Reference at: $CONTENT_REF"
fi
```

Read `$CONTENT_REF` (or `references/content-writing.md` if invoked directly).
Follow the guidelines precisely throughout Steps 4-6.

---

## Step 4 — Research & Plan

### Blog posts

1. **Classify search intent** — informational or commercial investigation.
   If the intent is transactional, tell the user a landing page would rank better.
2. **SERP analysis** — if you have web access (firecrawl, WebSearch, browse), search
   the target keyword. Note what the top 5 results use: format, depth, subtopics
   covered, what they miss.
3. **Define your angle** — what makes this post different? Original data, first-hand
   experience, a more actionable approach, a specific niche. Never write a post that
   just restates what's already ranking.
4. **Create an outline:**

```
# [Title] (< 60 chars, keyword front-loaded)

Meta description: [120-160 chars, keyword + CTA]
Target keyword: [primary]
Secondary keywords: [2-4 related terms]
Search intent: [type]
Content angle: [differentiator]

## [H2 — answers the core question first]
## [H2 — next most important subtopic]
## [H2 — practical examples / case studies]
## [H2 — common mistakes]
## FAQ
```

5. **Present outline for approval** before writing. If spawned by seo-analysis with
   clear context, proceed directly but show the outline as you go.

### Landing pages

1. **Verify intent** — must be transactional or commercial. If informational, suggest
   a blog post instead.
2. **Determine page type** — service, product, location, or comparison. Use the
   matching template from the guidelines.
3. **Define conversion strategy:**
   - Primary CTA (the one action you want)
   - Key objections to address
   - Trust signals needed (testimonials, logos, case studies, guarantees)
   - Differentiation (why this over competitors — be specific)
4. **Create page structure** using the guidelines template for the page type.
5. **Present for approval.**

### Content improvement

1. **Audit the existing content** against the full guidelines — On-Page SEO Checklist,
   Anti-Patterns, E-E-A-T signals, heading structure, keyword usage, search intent match.
2. **Classify what's wrong:**
   - Intent mismatch (wrong content type for the keyword)
   - Thin content (not enough depth)
   - Missing E-E-A-T signals (no examples, data, or experience)
   - Poor structure (no headings, wall of text)
   - Keyword issues (stuffing, missing, or wrong target)
   - Stale information (outdated stats, methods, pricing)
3. **Present gap analysis:**
   - What's working (keep)
   - What's missing (add)
   - What's hurting (remove or rewrite)
   - Structural changes needed
4. **Get approval** before rewriting.

---

## Step 5 — Write

Follow the writing rules from the guidelines for the content type.

**Voice and prose quality:** apply the **prose-sanitiser** skill throughout —
it owns the rules for lead-with-value openings, show-don't-tell specifics,
banned vocabulary, em-dash density, "The X" headings, throat-clearing,
hedge words, and UK English. Do not re-derive those rules here.

SEO-specific writing rules that prose-sanitiser does not cover:

**Structure for scanning.** Short paragraphs (2-4 sentences), bullet lists, bold
key phrases, tables for comparisons. One idea per paragraph.

**Keyword placement.** Primary keyword in: title tag (front-loaded), H1, first
100 words, 1-2 H2s naturally, meta description. After that: synonyms and natural
language. No stuffing.

**Search-intent match.** First paragraph directly answers the query the keyword
implies. If the searcher wants a list, give a list before the prose.

### Deliverables for blog posts:
1. Full post in markdown with heading hierarchy (H1 → H2 → H3)
2. SEO metadata: title tag (< 60 chars), meta description (120-160 chars), URL slug
3. JSON-LD structured data (`Article`/`BlogPosting` + `FAQPage` if FAQ included)
4. Internal linking plan (pages to link to and from)
5. Publishing checklist

### Deliverables for landing pages:
1. Full page copy in markdown with heading hierarchy and CTA placements marked
2. SEO metadata: title tag, meta description, URL slug
3. Conversion strategy: primary CTA, objections addressed, trust signals
4. JSON-LD structured data (`Service`/`Product`/`LocalBusiness` + `FAQPage`)
5. Internal linking plan + navigation placement suggestion
6. Publishing checklist

### Deliverables for content improvement:
1. Rewritten content in markdown (full replacement, not patches)
2. Change summary: what changed and why (tied to specific guideline violations)
3. Updated SEO metadata if needed
4. Updated structured data if needed

### Output Format

```
# [Content Type]: [Title]

## SEO Metadata
- **Title tag:** [< 60 chars]
- **Meta description:** [120-160 chars]
- **URL slug:** /[slug]
- **Target keyword:** [primary]
- **Secondary keywords:** [list]

## Content
[Full content in markdown with proper heading hierarchy]

## Structured Data
[JSON-LD ready to paste]

## Internal Linking Plan
- **Link TO this page from:** [existing pages + suggested anchor text]
- **This page links to:** [internal links in the content]

## Publishing Checklist
- [ ] Title tag and meta description set
- [ ] URL slug configured
- [ ] Structured data added
- [ ] Internal links placed (both directions)
- [ ] Open Graph image added
- [ ] Canonical URL set to self
- [ ] Mobile rendering verified
```

---

## Step 6 — Quality Gate

Before delivering, verify against every check. Fix failures before presenting.

### The "Last Click" Test
Would the reader need to search again? If yes, the content isn't done.

### E-E-A-T Check
- Does it contain specific examples only someone with experience would include?
- Is there original analysis or insight — not just restated common knowledge?
- Are claims backed by sources or data?

### Anti-Pattern Check (from guidelines)
- No keyword stuffing
- No filler paragraphs (every paragraph earns its place)
- No wall of text (headings, bullets, bold key phrases throughout)
- No duplicate intent with existing pages on the site
- **Run prose-sanitiser** for voice tells (em-dashes, banned vocab, "The X"
  headings, hedge words, throat-clearing, negative parallelism)

### Format Match
Does the content type match what Google shows for this query?

### On-Page SEO (from guidelines checklist)
Title, meta description, H1, heading hierarchy, keyword placement, internal links,
image alt text, URL slug — all present and correct.

### Landing Page Extra Checks
- Would you convert after reading this? What's missing if not?
- Are vague claims replaced with specifics?
- Is every major objection addressed?
- Is the CTA immediately clear?
Pliki w paczce (2)
  • SKILL.md 9 KB
  • references/content-writing.md 8 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · dreamlab-ai/agentbox100AGPL-3.0
jikig-ai/soleur100Apache-2.0
aaron-he-zhu/aaron-marketing-skills100Apache-2.0
TerminalSkills/skills100Apache-2.0
qa-aman/claude-skills100MIT
joogy06/agent-foundry100MIT
ViryaZheng/recomby-geo100MIT
eliyce/paqad-ai90MIT

Migawka bazy z 28.10.2026 · wersja paczki 2cf266ab78c5 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100seo-content-writer
    Pisze zoptymalizowane pod SEO wpisy blogowe, landing page i teksty na stronę po wcześniejszym researchu słów kluczowych.
  • 100write-blog
    Generuje pełny wpis blogowy zoptymalizowany pod SEO na podstawie słowa kluczowego lub tematu podanego przez użytkownika.
  • 87seo-content-writer
    Czyta wyniki Google dla hasła, analizuje strony z pierwszej dziesiątki i pisze gotowy do publikacji artykuł w markdown, zaprojektowany pod ranking.
  • 95article-content
    Pisze treść artykułów: korpus wpisu blogowego, treści długie, poradniki how-to i listicle, z naciskiem na przyrost informacji i gęstość treści.
  • 100seo-content-writer
    Tworzy treści SEO, takie jak wpisy blogowe, artykuły, opisy produktów i strony docelowe, według 12 kroków z optymalizacją tytułu, meta opisów, hierarchią nagłówków i listą CORE-EEAT.
  • 95memstack-content-blog-post
    Pisze długie artykuły blogowe dopasowane do tematu, odbiorcy i kanału publikacji.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.