菜单
Create, import, edit, or review posts for the official Flutter blog at flutter.dev/blog, including metadata, media, authors, and publication checks.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/flutter/website --skill contribute-blog命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Write or review clear, consistent, and accessible prose for Dart and Flutter developer documentation. Use for tutorials, API references, UI text, error messages, code comments, and terminology or style reviews.
Write or edit well-structured Markdown and MDX. Use for front matter, headings, lists, code fences, links, tables, other Markdown mechanics, and site-specific extensions. Pair with the write-technical-docs skill when changing prose.
Write, review, or refactor correct, idiomatic Dart code. Use for Dart source, packages, snippets, tests, public APIs, documentation examples, and modern language features. Pair with the write-flutter skill for Flutter-specific concerns.
| name | contribute-blog |
| description | Create, import, edit, or review posts for the official Flutter blog at flutter.dev/blog, including metadata, media, authors, and publication checks. |
Preserve the author's voice, intent, and requested scope. First person, contractions, anecdotes, humor, enthusiasm, and future-facing announcements can all be appropriate. Don't rewrite them merely to match documentation conventions.
Apply write-technical-docs and format-markdown selectively for clarity,
accuracy, accessibility, links, code formatting, and sound structure.
Their documentation-specific preferences aren't blanket blog requirements:
semantic line breaks and an 80-character limit aren't required,
especially when importing or lightly editing an existing post.
Fix or flag substantive issues with source fidelity, technical accuracy, accessibility, metadata, or rendering. Treat preference-only rewrites as suggestions unless copyediting was requested.
A small prose-only correction might need no reference.
Consult sites/www/content/blog/data.yaml,
sites/www/content/blog/authors.yaml, comparable recent posts,
or implementation source when a convention is unclear.
write-dart and write-flutter as relevant.
Validate complete examples when practical and
label intentional omissions or pseudocode clearly.TODO, TBD, or placeholder notes.
Report intentional markers or blockers instead of silently removing them.For a new post or a change to metadata or content, run the build and link-reference checks:
dart run dash_site --site=www build
dart run dash_site --site=www check-link-references
When layout, media, metadata, or content significantly changes, consider previewing the site locally:
dart run dash_site --site=www serve
For a prose-only edit that doesn't change links, direct inspection of the content can be enough.