- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add Illyism/seo-skills --skill intro -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add Illyism/seo-skills --skill intro -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add Illyism/seo-skills --skill intro -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add Illyism/seo-skills --skill intro -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/Illyism/seo-skills/tree/HEAD/content/intro게시자 제공
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.md개요
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
게시자에게서 content/intro/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/Illyism/seo-skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.