blog-style
Use when drafting or editing a blog post or long-form article in the house voice.
- License 许可
- Apache-2.0
- 所属仓库
- vercel/eve
- 最近更新
- 2026-11-15
- Stars
- ★ 5.9k
- Forks
- 656
01 前言 Front Matter
- description
- Use when drafting or editing a blog post or long-form article in the house voice.
02 资源文件 5
- 参考文档references/ai-phrases-to-avoid.md5.9 KB
- 参考文档references/banned-words.json147 B
- 参考文档references/best-practices.md5.9 KB
- 参考文档references/format-specs.md3.3 KB
- 参考文档references/plain-english-alternatives.md7.9 KB
03 SKILL.md 正文
Blog voice & style
When writing or editing a blog post:
- Lead with the reader's problem, not the product. Most people scan and read maybe a quarter of the words, so front-load the point — first in the post, first in each section and paragraph.
- Short paragraphs, 2–4 sentences, one idea each. White space is a feature, not filler.
- Descriptive subheads that read as a map: skim only the H2s and you should get the gist. Break up any section that runs past ~300 words. Use lists for steps or anything parallel.
- Most sentences under ~20 words. Active voice. Cut hedges: "just", "simply", "very", "really".
- Concrete over abstract; show an example before stating a principle.
- No exclamation points; no "in today's fast-paced world" openers.
- Match length to what the question needs — there's no magic word count. A quick answer can be a few hundred words; a real guide earns its length. Don't pad to hit a number.
- Mind the SEO surface: one descriptive title (~50–60 chars, keyword near the front), a short
hyphenated slug, 3–5 internal links with real anchor text, and alt text on meaningful images.
See
references/format-specs.mdfor the numbers.
Structure
- Hook — the problem or tension, in the reader's words; promise the payoff and preview it.
- Stakes — why it matters now.
- Payoff — the idea/solution, with one concrete example.
- Close — the single takeaway, then one focused next step. No "in conclusion".
References
references/best-practices.md— sourced checklist of current blog tactics (scanning, hook, structure, readability, length, SEO basics, close).references/format-specs.md— concrete specs: title/meta length, heading hierarchy, word-count ranges, readability targets, slug, alt text, internal links.references/banned-words.json— the list of words to avoid. Read it once up front for awareness, then run thecheck_styletool on your draft to check it against this file before proposing the draft to the writer.
Shared references
Shared global references for all skills in the content agent. These apply regardless of the content type.
references/ai-phrases-to-avoid.md— AI-tell words, phrases, and punctuation to avoid.references/plain-english-alternatives.md— plain-English swaps for bloated or vague wording.
04 同仓库更多 Skills
writing-quality
The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.
writing-quality
Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.
seo-aeo-best-practices
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity/functions, @sanity/blueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.
portable-text-serialization
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.
portable-text-conversion
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext/markdown (markdownToPortableText), @portabletext/block-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.