Planning

Naver AI Briefing Writing

Write posts that search and the Naver AI briefing can quote: answer-first summary, question headings, FAQ and honest sources.

Naver AI Briefing Writing
Works with Claude, GPT and GeminiInstall any one of them in VS Code →ClaudeClaude CodeGPTCodexGeminiAntigravity

How to use

  1. 1

    Download the ZIP

    Get the skill file with the button below. No sign-up.

  2. 2

    Unzip and open

    Unzip it into a folder and open that folder in VS Code.

  3. 3

    Just ask

    Tell your AI agent ‘Run the automation pipeline in this folder’.

When to use it

Try saying

“이 주제로 네이버 AI 브리핑에 인용되기 쉬운 글 써줘”Write this post in the AI-briefing-friendly structure
“내 글을 이 구조로 다시 정리해줘”Restructure my draft this way

What you get

  1. 01A full post with summary, headings, FAQ and sources
  2. 0210-15 tags
  3. 03A pre-publish check

Tips

Get it free now

No sign-up, just one ZIP. Edit it freely for personal or commercial use.

Download ZIP (2KB)

Installation

Claude.ai / Desktop app (ZIP upload)

  1. Download the ZIP below.
  2. Upload it under Settings → Capabilities → Skills.
  3. Turn the skill on and start a chat with one of the "Try saying" lines.

Claude Code (copy the folder)

  1. Unzip it. You'll get a folder named after the skill.
  2. Put that folder inside ~/.claude/skills/ (or .claude/skills/ for a single project).
  3. Restart Claude Code.

Menu names may differ slightly depending on your environment. If you can't see the menu, check that skills are enabled on your plan.

Files and preview

Included files

SKILL.md
README.txt

Preview of SKILL.md

---
name: naver-ai-briefing-writing
description: Write a Naver blog post structured so search and the Naver AI briefing can quote it - answer-first summary, question subheadings, FAQ, sources, honest hedging, plus a pre-publish checklist. 네이버 AI 브리핑에 인용되기 쉬운 블로그 글쓰기.
---

# Naver AI-Briefing-Friendly Writing

Use this to **write or rewrite one post** so each section can stand alone as a clear answer. It is based on the structure used on a real Naver blog whose posts were cited many times by the Naver AI briefing. It does **not** guarantee a ranking or home-feed placement; Naver decides that.

## Post structure
1. **Title**: main keyword first (see `naver-blog-topic-picker`), 35-50 characters, a concrete question or promise, plus one short twist that makes the reader think "oh, really?". If the title has no twist, rewrite it.
2. **One-line summary** at the very top (quote style): 2-3 complete sentences with the keyword that make sense even if read alone. This is the part most likely to be quoted.
3. **Hook and promise**: one friendly opening line, then "after reading this you will know: 1, 2, 3".
4. **Sections** (5 short or 8 full): each has
   - an H2 written as a real search question ("How hot is X?");
   - the **answer in the first line** (bold, a full sentence with its subject);
   - a plain-language explanation (write as if for a smart 12-year-old);
   - at most one highlighted line per section, and one or two "fun fact" boxes per post.
5. **A light reaction question** after the opening part (two easy choices, "reply with a number"), and a **different** choice question at the end. Open questions get no replies; two easy choices do.
6. **Summary table** of key numbers and dates.
7. **FAQ**: 2-3 questions with short answers.
8. **Sources**: the organization or paper name, and the real URL **only if you opened it**. Never invent a URL.
9. **Related posts**: 3 links to your own published posts.

## Rules
- Write for readers, not for the algorithm. No keyword stuffing; the keyword appears naturally in the title, the first summary and a few subheadings.
- Check every number and date against a source. If it is uncertain, write "about" or "reported", and say when sources differ. Do not state a debated claim as settled.
- Disclose paid or affiliate links in a visible sentence near the top, not only at the bottom.
- No fake personal experience, no invented quotes, no copied text from other blogs.
- Center alignment, 15px body text, headings as real H2, a few emoji are fine.
- AI-made images must have the AI-use mark switched on in the editor (see `naver-editor-assembly`).

## Pre-publish checklist
- [ ] Main keyword is at the start of the title and in the summary.
- [ ] The first line of each section answers its heading.
- [ ] Numbers and dates were checked; uncertain ones are hedged.
- [ ] Sources listed are real and were opened.
- [ ] FAQ has 2-3 items; two different reply questions (middle and end).
- [ ] Related links point only to published posts.
- [ ] Tags: 10 or more, without hyphens (a hyphen can break tag input in the editor).

You may also like

This skill is a set of instructions Claude loads on its own. You are responsible for how you use the results. The instructions inside the ZIP are written in Korean. Terms of Use