- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add Illyism/seo-skills --skill intro -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add Illyism/seo-skills --skill intro -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add Illyism/seo-skills --skill intro -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add Illyism/seo-skills --skill intro -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/Illyism/seo-skills/tree/HEAD/content/introDe l'éditeur
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.mdVue d'ensemble
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
Téléchargez content/intro/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/Illyism/seo-skills.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.