- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Illyism/seo-skills --skill intro -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Illyism/seo-skills --skill intro -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Illyism/seo-skills --skill intro -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Illyism/seo-skills --skill intro -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/Illyism/seo-skills/tree/HEAD/content/introFrom the publisher
Write engaging blog intros in the style of high-performing SEO listicles and guides (examples.md).
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.
Say: "Tell me a bit about your content and I'll write an intro for it."
Gather enough to match intent:
If the user already pasted an outline or draft, use it. Do not invent stats, market share, or legal claims unless they provided them.
I will:
Pick the pattern that fits the article type.
Reference: listicle example
grouped by type, in no particular order).Or jump straight to our [FAQs](#anchor).Reference: how-to example
Reference: definition example
Reference: debate example
three proven ways, five common mistakes).What Is X?) right after the intro.Unless the user asks for full, slug, title, or alt, return only the intro: the markdown body paragraphs, ready to paste under frontmatter.
Use when the user asks for full or everything in one pass. Reference: full output example.
**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):
Rules for full output:
In this guide, you'll learn: (or a close variant the user prefers).Before returning, confirm:
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, lis
---name: introdescription: Write short, Semrush-style blog post intros with journey teasers, practical relevance, and reader intent…---# content/intro/SKILL.mdOverview
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.
FAQ
Download content/intro/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/Illyism/seo-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.