---
name: intro
description: Write short, Semrush-style blog post intros with journey teasers, practical relevance, and reader intent matching. Use when the user asks for /intro, a blog intro, opening paragraph, article lead, listicle intro, or hook copy for a post.
metadata:
  version: 1.0.0
  author: illyism
  source: https://il.ly/skills/intro
title: intro
canonical_url: https://skilld.dev/gh/illyism/seo-skills/intro
last_updated: 2026-11-21T21:01:40.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [examples.md](https://skilld.dev/api/skills-raw/illyism/seo-skills/intro/examples.md).
>
> If the user asked to install this Skill, run `npx skilld install illyism/seo-skills/intro`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/intro`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/illyism/seo-skills/intro) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/intro`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/intro --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/intro --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Blog intro writer

Write short blog intros in the style of SEO listicles and guides that rank ([examples.md](https://skilld.dev/api/skills-raw/illyism/seo-skills/intro/examples.md#contents)).

## When this applies

The user invoked **`/intro`**, or asked for a blog intro, opening paragraph, or lead copy for a post.

Works on its own or after title work (see the `seo-title-optimization` skill). If the slug or title is missing, ask briefly or propose one.

## First step

Say: "Tell me a bit about your content and I'll write an intro for it."

Gather enough to match intent:

- Topic, primary keyword, and search intent (informational, listicle, how-to, comparison)
- Target reader and their goal
- Article shape: listicle count, H2/H3 outline, or key sections
- Product angle, if the post promotes one
- Optional: chosen title, slug, featured image subject

If the user already pasted an outline or draft, use it. Do not invent stats, market share, or legal claims unless they provided them.

## What every intro does

- Matches the reader's intent
- Says what the topic is and why it matters in practice (**explain why**)
- Ties the topic to the reader's goal
- Ends with a **journey teaser**: the steps or sections ahead

## Intro patterns

Pick the pattern that fits the article type.

### Listicle (e.g. "21 Best Search Engines")

Reference: [listicle example](https://skilld.dev/api/skills-raw/illyism/seo-skills/intro/examples.md#listicle-search-engines)

1. One sentence: what the thing is.
2. One sentence: why the default option is not enough, or why the list matters.
3. Journey teaser: what the list covers and how it is organized (`grouped by type`, `in no particular order`).
4. Optional jump line: `Or jump straight to our [FAQs](#anchor).`

### How-to / guide (e.g. reverse image search)

Reference: [how-to example](https://skilld.dev/api/skills-raw/illyism/seo-skills/intro/examples.md#how-to-reverse-image-search)

1. Lead with the task or problem in plain language.
2. **Explain why** in one or two short sentences.
3. Optional bullet list of outcomes (3–5 items) when it clarifies value.
4. Journey teaser: what platforms or steps the article covers.
5. Close with what they will learn by the end (one short sentence).

### Definition-first (e.g. "What Is SEO?")

Reference: [definition example](https://skilld.dev/api/skills-raw/illyism/seo-skills/intro/examples.md#definition-what-is-seo)

1. Open with the term and a tight definition (expand acronyms on first use).
2. One sentence on the user need and outcome (visibility, traffic, accuracy).
3. Optional short bullet list of what the practice involves.
4. Journey teaser: the main sections ahead.

### Debate / evidence piece

Reference: [debate example](https://skilld.dev/api/skills-raw/illyism/seo-skills/intro/examples.md#debate-intro-frame-a-fight)

1. Frame two extremes the reader has heard.
2. Position the article as the level-headed referee and name the method.
3. Promise a concrete payoff.
4. List the questions the article answers, in the order the H2s answer them.

## Writing rules

- **Short sentences.** Prefer 8–15 words. Break long lines into two sentences.
- **Keep it short.** 2–4 short paragraphs or 80–120 words unless the user asks for more.
- **Listicles:** mirror the count in the title (`three proven ways`, `five common mistakes`).
- **Voice:** direct, practical, confident. No hype words.
- **Emphasis (sparingly):** **bold** 2–4 hook words per intro (primary keyword, pain point, or outcome). Use _italic_ for one short aside or contrast. Never both on the same phrase.
- **No H2 in the intro** unless the outline starts with a definition block (`What Is X?`) right after the intro.
- The intro is the first prose block after frontmatter, not the meta description or excerpt.

## Slug, title, and image alt

- **Slug and title:** use the ones the user has. If not, propose one slug and one title that fit the intro.
- **Image alt:** describe the featured image for accessibility: subject plus context (mock UI, diagram, before/after). One sentence, under 125 characters when possible.

## Default output

Unless the user asks for `full`, `slug`, `title`, or `alt`, return only the intro: the markdown body paragraphs, ready to paste under frontmatter.

## Full output format

Use when the user asks for **`full`** or everything in one pass. Reference: [full output example](https://skilld.dev/api/skills-raw/illyism/seo-skills/intro/examples.md#full-output-definition-guide-ai-seo-style).

```markdown
**Slug:** `[slug]`

**Title:** [title]

**Image alt:** [one sentence, under 125 characters when possible]

**Intro:**

[1–2 sentences: definition or what the thing is]

[Optional: "That means…" + 2–4 short bullets: outcomes or jobs to be done]

[1–2 sentences: **explain why**, the practical stakes; use stats only if the user provided them]

**In this guide, you'll learn:**

- [Section or outcome 1](#heading-anchor)
- [Section or outcome 2](#another-anchor)
- [Section or outcome 3](#another-anchor)
- [Section or outcome 4](#another-anchor)

[One short closing line. Vary it; do not default to "Let's dive in."]
```

**Closing lines (pick one that fits; avoid repeating across a batch):**

- Here's how it works.
- Below is the full walkthrough.
- We'll break down each approach below.
- Here's what to know before you build.
- Use the sections below as your playbook.
- Read on for the step-by-step workflow.
- Here's how each platform compares.
- The rest of this guide covers it in order.

Rules for full output:

- Label fields with **Slug**, **Title**, **Image alt**, **Intro** so they are easy to copy.
- Use the heading **`In this guide, you'll learn:`** (or a close variant the user prefers).
- **Link each journey bullet** to the matching H2 anchor on the same post when the heading slugs are known. Anchors must match the live post.

## Quality check

Before returning, confirm:

- [ ] Reader intent matches the listicle, how-to, definition, or debate pattern
- [ ] Why the topic matters (practical, not abstract)
- [ ] Relevance to the reader's goal is clear
- [ ] Journey teaser names sections or outcomes
- [ ] Journey bullets link to real anchors in full output for existing posts
- [ ] 2–4 **bold** hooks and at most one _italic_ aside
- [ ] Sentences are short; total length is tight
- [ ] No fabricated data or competitor claims
