Flutter Pub Release
MixinNetwork/flutter-plugins
Prepare and draft a pub.dev release for a package in the flutter-plugins monorepo.
Contains well-defined rules for creating natural, accurate, and readable writing.
Install Natural Writing
$ npx skills add flutter/flutter --skill natural-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install flutter/flutter natural-writing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/flutter/flutter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/agents/reidbaker-agent/skills/natural-writing .claude/skills/natural-writing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "natural-writing" agent skill from https://github.com/flutter/flutter/tree/master/.agents/agents/reidbaker-agent/skills/natural-writing into .claude/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/flutter/flutter/tree/master/.agents/agents/reidbaker-agent/skills/natural-writingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add flutter/flutter --skill natural-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install flutter/flutter natural-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/agents/reidbaker-agent/skills/natural-writing .agents/skills/natural-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "natural-writing" agent skill from https://github.com/flutter/flutter/tree/master/.agents/agents/reidbaker-agent/skills/natural-writing into .agents/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flutter/flutter --skill natural-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install flutter/flutter natural-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/agents/reidbaker-agent/skills/natural-writing .cursor/skills/natural-writing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "natural-writing" agent skill from https://github.com/flutter/flutter/tree/master/.agents/agents/reidbaker-agent/skills/natural-writing into .cursor/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/flutter/flutter.git --path .agents/agents/reidbaker-agent/skills/natural-writing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add flutter/flutter --skill natural-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install flutter/flutter natural-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/agents/reidbaker-agent/skills/natural-writing .gemini/skills/natural-writing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "natural-writing" agent skill from https://github.com/flutter/flutter/tree/master/.agents/agents/reidbaker-agent/skills/natural-writing into .gemini/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install flutter/flutter natural-writingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add flutter/flutter --skill natural-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/flutter/flutter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/agents/reidbaker-agent/skills/natural-writing .github/skills/natural-writing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "natural-writing" agent skill from https://github.com/flutter/flutter/tree/master/.agents/agents/reidbaker-agent/skills/natural-writing into .github/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flutter/flutter --skill natural-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install flutter/flutter natural-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flutter/flutter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/agents/reidbaker-agent/skills/natural-writing .opencode/skills/natural-writing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "natural-writing" agent skill from https://github.com/flutter/flutter/tree/master/.agents/agents/reidbaker-agent/skills/natural-writing into .opencode/skills/natural-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "natural-writing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
natural-writing- GitHub stars
- 179k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 1,028 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Contains well-defined rules for creating natural, accurate, and readable writing.
- Works in 6 steps: Vocabulary & Phrasing Controls → Content & Tone → Sentence Structure → …
- Authoring longer text
- SKILL.md covers 1. Vocabulary & Phrasing…, 2. Content & Tone, 3. Sentence Structure and 4. Structure & Formatting, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Natural Writing is an agent skill from flutter/flutter. Contains well-defined rules for creating natural, accurate, and readable writing. Use whenever authoring longer text, like analysis documents, PR or CL descriptions, or documentation.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Humanizing AI text and Cross-platform mobile apps. It works with Flutter and Dart. The repository describes itself as: Flutter makes it easy and fast to build beautiful apps for mobile and beyond. The licence is BSD-3-Clause.
When your agent uses it
- Authoring longer text
- Like analysis documents
- CL descriptions
Example prompts
- “Use the natural-writing skill to contain well-defined rules for creating natural, accurate, and readable writing”
- “/natural-writing”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit fe75cab. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Natural Writing loads about 1.9k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 1,028 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from flutter/flutter at commit fe75cab, republished under its BSD-3-Clause licence (© flutter). 1,028 words, ~1,926 tokens.
Download SKILL.mdSave it as
.claude/skills/natural-writing/SKILL.md (or your agent's skills folder).- name
- natural-writing
- description
- Contains well-defined rules for creating natural, accurate, and readable writing. Use whenever authoring longer text, like analysis documents, PR or CL descriptions, or documentation.
Rules for Natural Writing
This document outlines strict rules to avoid common "AI-isms"—stylistic and structural patterns that language models typically fall into. Follow these rules to produce content that is more understandable, and reads as natural, human-authored text.
1. Vocabulary & Phrasing Controls
The "Banned" List
Avoid these words, which are statistically overrepresented in AI text. Use simpler, more direct alternatives.
- Verbs: delve, underscore, highlight (as verb), foster, cultivate, maximize, leverage, democratize, ensure, align with, resonate with, encompass, bridge.
- Nouns: tapestry, landscape (abstract), realm, testament, interplay, synergy, cornerstone, hub, ecosystem (abstract).
- Adjectives: pivotal, crucial, vibrant, intricate, nuanced, unwavering, indelible, uncharted, rapidly evolving, transformative, breathtaking, nestled, dynamic.
Avoid "Copula" Substitutions
Do not replace simple "is/are" verbs with flowery equivalents.
- Bad: "The library serves as a center for learning."
- Bad: "The statue stands as a monument to..."
- Good: "The library is a center for learning."
- Good: "The statue is a monument to..."
Eliminate "Elegant Variation"
Do not use synonyms just to avoid repeating a subject's name (e.g., "the eponymous character," "the titular protagonist," "the celebrated author"). It is acceptable to repeat the name or use pronouns naturally.
Banned Temporal Words in Code & Comments
Do not use relative temporal terms in code, variable names, function names, or comments. These words lose their meaning as the codebase evolves over time.
- Banned Words: now, currently, existing behavior, previous behavior, old, new, modern.
- Bad:
// This function now uses the config parser instead of hardcoding. - Good:
// Resolves paths via [ConfigParser.loadConfig] to support custom config locations.
2. Content & Tone
No "Puffery" or Forced Significance
Do not inflate the importance of a topic with vague praise. If a subject is important, the facts should demonstrate it without help.
- Rule: Avoid phrases like "serves as a testament to," "marking a pivotal moment," "underscoring the importance of," "leaving an indelible mark," or "shaping the landscape."
- Bad: "The founding of the institute marked a pivotal moment in the evolution of regional statistics, representing a significant shift toward independence."
- Good: "The institute was founded in 1989 to collect regional statistics."
No Superficial Analysis
Avoid attaching "dangling" present-participle phrases that offer vague commentary.
- Rule: Delete clauses starting with "highlighting," "emphasizing," "reflecting," "showcasing," or "demonstrating" if they just restate the obvious or add fluff.
- Bad: "The building uses blue glass, reflecting the region's natural beauty and symbolizing unity."
- Good: "The building uses blue glass."
Avoid Promotional Language
Maintain a neutral tone. Avoid "advertisement" words.
- Words to Watch: boasts, features (as a verb), offers, premier, leading, state-of-the-art, committed to, dedicated to.
- Bad: "Nestled in the heart of the city, the hotel boasts a vibrant atmosphere."
- Good: "The hotel is located in the city center."
No "Challenges and Future Outlook" Formula
LLMs often end articles with a generic "Despite challenges... remains important" conclusion.
- Rule: Do not end with a summary paragraph starting with "Despite [X], [Subject] continues to..." or speculating on the future. End with the last fact.
- Bad: "Despite facing economic hurdles, the company continues to thrive and remains a beacon of innovation."
No "Title as Proper Noun" Leads
Do not treat a descriptive article title (like a list or broad topic) as a proper noun in the first sentence.
- Bad: "The List of songs about Mexico is a curated compilation..."
- Good: "This list contains songs about Mexico..."
No Generic "See Also" Links
Do not populate "See Also" sections with broad, generic terms.
- Rule: Links must be directly relevant and specific to the subject.
- Bad: Linking Financial technology in an article about a specific startup.
- Good: Linking a competitor or specific related technology.
Attribution Precision
Do not use vague "weasel words."
- Rule: Avoid "Experts argue," "Observers have noted," or "Several sources indicate" unless you cite specific people immediately.
- Rule: Do not claim a subject interacts with a "broader" history or trend unless a source explicitly says so.
Show full SKILL.md (398 more words)Show less
3. Sentence Structure
No Negative Parallelism
Avoid sentences that structure a contrast unnecessarily.
- Bad: "It is not only a painting, but also a representation of..."
- Bad: "It is not just about X; it is about Y."
- Good: "It is a painting that represents..."
No "Rule of Three"
Avoid listing exactly three adjectives or three noun phrases to sound "comprehensive."
- Bad: "The event brings together marketers, engineers, and designers." (Unless those specific three groups are the only ones).
- Bad: "It is bold, innovative, and unique."
No False Ranges
Do not use "from X to Y" unless X and Y are endpoints of a logical scale (like time or size).
- Bad: "The book covers everything from biology to space travel." (These are just two random topics, not a range).
- Good: "The book covers topics including biology and space travel."
4. Structure & Formatting
Headers
- Rule: Use Sentence case for headers (e.g., "Early life," not "Early Life").
- Rule: Do not use "Title Case" in headers.
Formatting Avoidance
- No Inline-Header Lists: Do not use the format:
* **Header:** Description.... Use prose or simple lists. - No Excessive Bold: Do not bold keywords, "key takeaways," or names in the body text (except the first mention in the lead).
- No Symbols/Emojis: Do not use emojis (🚀, 🧠) or unusual bullets (
#,-) in lists. Use standard bullets (*). - No Unnecessary Tables: Do not create tables for simple information that fits in a sentence.
- Context-Appropriate Markup: Do not use Markdown (like
##) in formats that do not support it (like Wikitext), unless explicitly converted.
Punctuation
- Quotes: Use straight quotes (
",') and straight apostrophes ('). Do not use curly/smart quotes (“,’). - Em Dashes: Use em dashes sparingly. LLMs overuse them for emphasis. Use commas or parentheses instead.
5. Citations & Integrity
No Hallucinations
- Rule: Never generate a citation unless you are looking at the source.
- Rule: Do not invent URLs or DOIs.
- Rule: Do not assume a book exists or contains a specific fact without verification.
6. Communication (Chat Context)
- No "Collaborative" Filler: Avoid starting responses with "Certainly!", "Here is the information," or "I hope this helps." Just provide the content.
- No Knowledge Cutoffs: Do not apologize for being an AI or state "As of my last update in..." unless relevant to a specific time-sensitive fact.
- No Subject Lines: Do not preface a response with
Subject: ... - Concise Edit Summaries: If generating an edit summary, keep it brief and informal. Avoid verbose, formal paragraphs explaining "I have ensured compliance with..."
© flutter, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/agents/reidbaker-agent/skills/natural-writing of flutter/flutter.
Open the folder on GitHubat commit fe75cab
Compare with similar skills
Natural Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Natural Writing this skillflutter/flutter | 179k | — | ~1.9k | Automated safety check: Pass | BSD-3-Clause | |
| Flutter Pub ReleaseMixinNetwork/flutter-plugins | 512 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Liquid Glass Widgetssdegenaar/liquid_glass_widgets | 720 | — | ~4.1k | Automated safety check: Pass | MIT | |
| Flutter Bloc and Cubitandrewyng/context-hub | 14k | — | ~998 | Automated safety check: Pass | MIT | |
| Solidnank1ro/solid | 165 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Code Guidelinesgetsentry/sentry-dart | 873 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Liquid Glass Widgets
sdegenaar/liquid_glass_widgets
Mastery guide and architectural rules for liquidglasswidgets.
Flutter Bloc and Cubit
andrewyng/context-hub
Helps choose between Bloc and Cubit in Flutter and sets defaults for packages, lifecycle, widget binding and tests.
Solid
nank1ro/solid
PRIORITY — read this skill FIRST before writing Dart code when pubspec.yaml declares solidannotations or solidgenerator.
- Official
Code Guidelines
getsentry/sentry-dart
Enforce Sentry Dart/Flutter SDK code guidelines for implementation, refactoring, and review.
Bump Version
VeryGoodOpenSource/very_good_analysis
Bumps the verygoodanalysis package to a new version. An agent skill from VeryGoodOpenSource/very_good_analysis.
More from flutter/flutter
All 14 skills in this repoEngine Whats New
flutter/flutter
Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44).
Flutter Cherry Pick
flutter/flutter
How to land a formal cherry-pick of a merged PR for the flutter/flutter repo stable or beta channel.
Upgrade Browser
flutter/flutter
Upgrade browser versions (Chrome or Firefox) in the Flutter Web Engine and/or Framework tests.
Code Review
flutter/flutter
Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.
Bump Dart
flutter/flutter
Do not trigger automatically; only run when a user runs /bump-dart.
Run Devicelab With Led
flutter/flutter
Run DeviceLab tests for Flutter PRs using LUCI's led CLI tool.
Related
Categories
Questions about Natural Writing
What does Natural Writing do?
Contains well-defined rules for creating natural, accurate, and readable writing. Natural Writing is an agent skill from flutter/flutter. Contains well-defined rules for creating natural, accurate, and readable writing.
When should I use Natural Writing?
Natural Writing fits situations like: authoring longer text; like analysis documents; CL descriptions.
How do I install Natural Writing in Claude Code?
Run `npx skills add flutter/flutter --skill natural-writing -a claude-code`. Or copy the skill folder (.agents/agents/reidbaker-agent/skills/natural-writing in flutter/flutter) into .claude/skills/natural-writing in your project. Claude Code loads it when a task matches its description.
How do I install Natural Writing in Codex?
Run `npx skills add flutter/flutter --skill natural-writing -a codex`. Or copy the skill folder (.agents/agents/reidbaker-agent/skills/natural-writing in flutter/flutter) into .agents/skills/natural-writing in your project. Codex loads it when a task matches its description.
Can I use Natural Writing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flutter/flutter --skill natural-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/natural-writing, .gemini/skills/natural-writing, .github/skills/natural-writing and .opencode/skills/natural-writing in your project.
What does Natural Writing need to run?
SKILL.md names no scripts, command-line tools or credentials: Natural Writing is instructions for the agent only.
Does Natural Writing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Natural Writing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Natural Writing use?
Natural Writing is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Natural Writing use?
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Natural Writing?
Skills that share tags, products or a category with Natural Writing: Flutter Pub Release (MixinNetwork/flutter-plugins, 512 stars), Liquid Glass Widgets (sdegenaar/liquid_glass_widgets, 720 stars), Flutter Bloc and Cubit (andrewyng/context-hub, 14k stars) and Solid (nank1ro/solid, 165 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Natural Writing?
flutter (a GitHub organization) maintains it in flutter/flutter, which has 179,184 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 2026.
Source: flutter/flutter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.