Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
A skill your agent uses when drafting or polishing a Field Crops Research (FCR) manuscript so it reads for a general agronomy/crop-science audience, follows FCR structure, and meets the format…
Install Fcr Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fcr-writing-style --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/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Field-Crops-Research-Skills/skills/fcr-writing-style .claude/skills/fcr-writing-style && 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 "fcr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-writing-style into .claude/skills/fcr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-writing-style", 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/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-writing-styleType 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 brycewang-stanford/Awesome-Journal-Skills --skill fcr-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fcr-writing-style --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Field-Crops-Research-Skills/skills/fcr-writing-style .agents/skills/fcr-writing-style && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fcr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-writing-style into .agents/skills/fcr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-writing-style", 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 brycewang-stanford/Awesome-Journal-Skills --skill fcr-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fcr-writing-style --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Field-Crops-Research-Skills/skills/fcr-writing-style .cursor/skills/fcr-writing-style && 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 "fcr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-writing-style into .cursor/skills/fcr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-writing-style", 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/brycewang-stanford/Awesome-Journal-Skills.git --path Field-Crops-Research-Skills/skills/fcr-writing-style--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 brycewang-stanford/Awesome-Journal-Skills --skill fcr-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fcr-writing-style --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Field-Crops-Research-Skills/skills/fcr-writing-style .gemini/skills/fcr-writing-style && 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 "fcr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-writing-style into .gemini/skills/fcr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-writing-style", 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 brycewang-stanford/Awesome-Journal-Skills fcr-writing-styleInstalls 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 brycewang-stanford/Awesome-Journal-Skills --skill fcr-writing-style -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Field-Crops-Research-Skills/skills/fcr-writing-style .github/skills/fcr-writing-style && 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 "fcr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-writing-style into .github/skills/fcr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-writing-style", 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 brycewang-stanford/Awesome-Journal-Skills --skill fcr-writing-style -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fcr-writing-style --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Field-Crops-Research-Skills/skills/fcr-writing-style .opencode/skills/fcr-writing-style && 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 "fcr-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Field-Crops-Research-Skills/skills/fcr-writing-style into .opencode/skills/fcr-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fcr-writing-style", 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
fcr-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 668 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting or polishing a Field Crops Research (FCR) manuscript so it reads for a general agronomy/crop-science audience, follows FCR structure, and meets the format…
- Works in 4 steps: Introduction. Brief, unbiased,… → Materials & Methods. Complete enough to… → Results. Concise; report what answers… → …
- Polishing a Field Crops Research (FCR) manuscript so it reads for a general agronomy/crop-science audience
- SKILL.md covers When to trigger, Structure & section discipline, Abstract & highlights and Reach a general agronomy…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Fcr Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or polishing a Field Crops Research (FCR) manuscript so it reads for a general agronomy/crop-science audience, follows FCR structure, and meets the format expectations (abstract <=400 words, 3-5 highlights of <=85 characters, grammatically sound English, concise results, a discussion that interprets rather than repeats). Tightens prose and format; it does not invent content.
Its SKILL.md is about 1.5k 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 Brand voice and tone. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Polishing a Field Crops Research (FCR) manuscript so it reads for a general agronomy/crop-science audience
- Follows FCR structure
- Meets the format expectations (abstract <=400 words
- 3-5 highlights of <=85 characters
Example prompts
- “/fcr-writing-style”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Introduction. Brief, unbiased, up-to-date review that flows to clear **objectives or
- Materials & Methods. Complete enough to reproduce: crop/cultivar, sites/seasons, soil, weather,
- Results. Concise; report what answers the objectives, with effect sizes and uncertainty.
- Discussion. Place findings in agronomic context and justify conclusions with the data — do
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. 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
Fcr Writing Style loads about 1.5k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 668 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 brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 668 words, ~1,524 tokens.
Download SKILL.mdSave it as
.claude/skills/fcr-writing-style/SKILL.md (or your agent's skills folder).- name
- fcr-writing-style
- description
- Use when drafting or polishing a Field Crops Research (FCR) manuscript so it reads for a general agronomy/crop-science audience, follows FCR structure, and meets the format expectations (abstract <=400 words, 3-5 highlights of <=85 characters, grammatically sound English, concise results, a discussion that interprets rather than repeats). Tightens prose and format; it does not invent content.
Writing Style (fcr-writing-style)
An FCR paper must be readable by an agronomist or crop scientist outside your exact crop and region, written in grammatically sound English, and disciplined to FCR's structure: a focused introduction, complete methods, concise results that address the objectives, and a discussion that interprets rather than restates results. This skill is about clarity and format — not about generating claims.
When to trigger
- Drafting the introduction, results, or discussion, or doing a final polish
- Writing the abstract (≤ 400 words) and the highlights (3–5 bullets)
- Tightening a verbose results or discussion section
- Aligning citations and units to the Elsevier/FCR style before submission
Structure & section discipline
- Introduction. Brief, unbiased, up-to-date review that flows to clear objectives or
hypotheses of general relevance (see
fcr-literature-positioning). - Materials & Methods. Complete enough to reproduce: crop/cultivar, sites/seasons, soil, weather,
management, design, and statistics (see
fcr-reporting-and-data-policy). - Results. Concise; report what answers the objectives, with effect sizes and uncertainty. Do not interpret here.
- Discussion. Place findings in agronomic context and justify conclusions with the data — do not repeat the results. State scope/limitations and generality across environments.
Abstract & highlights
- Abstract (≤ 400 words): purpose, key methods (crop, environments), principal quantitative results, and the major agronomic conclusion.
- Highlights: 3–5 bullet points, each ≤ 85 characters including spaces — concrete findings, not topic labels.
Reach a general agronomy audience
- Define crop- or region-specific terms on first use; spell out acronyms; use SI units throughout.
- Lead with the agronomic point; connect results to yield and biophysical processes.
- Quantify ("a 0.8 t ha⁻¹ increase," not "a large increase"); avoid vague significance language.
- Signpost clearly so a reader can follow the argument from objective to conclusion.
Vague-to-quantified rewrite table
FCR rewards the quantified, agronomic sentence over the qualitative one. Each row shows the upgrade an editor expects between draft and submission.
| Vague draft | Quantified, FCR-ready (illustrative) |
|---|---|
| "Yield increased substantially." | "Yield rose 0.9 t ha⁻¹ (12%) in high-N environments." |
| "The treatment was significant." | "The N×cultivar interaction was significant (SED = 0.15 t ha⁻¹, α = 0.05)." |
Worked discussion-rewrite vignette (illustrative)
Illustrative. A results-echoing discussion opens: "As shown in Table 3, the new cultivar yielded 0.9 t ha⁻¹ more than the check" — restating the result, the most common FCR reviewer complaint. The interpretive rewrite leads with the mechanism and its generality: "The advantage concentrated in high-N environments, consistent with greater post-anthesis N remobilisation in the stay-green line; in the two dry site-years it vanished, marking water — not N — as limiting." Now the paragraph explains why and bounds where it travels — the move from local report to general contribution.
Show full SKILL.md (247 more words)Show less
Anti-patterns
- A discussion that repeats the results instead of interpreting them
- A region-insider framing that never states general relevance
- An abstract that hides the quantitative finding or runs far over length
- Highlights that are topics ("Effects of nitrogen on wheat") rather than findings
- Non-SI units, undefined acronyms, or inconsistent citation style
- Conclusions not justified by the data
Style execution pass for Field Crops Research
Treat this skill as an executable review pass, not a prose hint. First lock the crop system, environment structure, GxE logic, and yield or physiology endpoint; then judge whether the current manuscript answers the venue's real reader: agronomy reviewers who expect field-based, multi-environment evidence and crop-level general significance.
- Do the pass: Rewrite the first two pages so each paragraph starts from the venue-level claim, not from chronology or method inventory; preserve exact source-map limits and move technical overflow to appendix or supplement.
- Return a ledger: give
claim / evidence / risk / manuscript locationrows, so the next agent can edit rather than rediscover the issue. - Sibling guard: compare against Agricultural Systems for whole-system modeling, European Journal of Agronomy for agronomic breadth, Crop Science for cultivar or breeding emphasis; if a sibling owns the contribution, recommend re-routing before polishing format.
- Submission-ready gate: do not give final advice until the pack's
resources/official-source-map.mdhas been checked for upload-week rules and the manuscript has one concrete fix for the largest venue-specific risk.
Output format
【Structure】intro → methods → concise results → interpretive discussion? [Y/N]
【Discussion interprets, not repeats?】[Y/N]
【Abstract】word count (≤400) + states quantitative finding? [Y/N]
【Highlights】3-5 bullets, each ≤85 chars, findings not topics? [Y/N]
【General reach】SI units + acronyms defined + quantified? [Y/N]
【Next】fcr-cover-letterSupplementary resources
../../resources/external_tools.md— reference managers and Elsevier typesetting tools../../resources/official-source-map.md— abstract/highlights specs and structure expectations
© brycewang-stanford, MIT. 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 Field-Crops-Research-Skills/skills/fcr-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Fcr Writing Style 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 |
|---|---|---|---|---|---|---|
| Fcr Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| BrandOhh-889/skyroc | 795 | 13 repos | ~733 | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Writing Guidelinesvercel-labs/agent-skills | 32k | 7 repos | ~309 | Automated safety check: Pass | None | |
| Unslop AI Writing Cleanuptheclaymethod/unslop | 518 | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Brand
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
- Official
Writing Guidelines
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Unslop AI Writing Cleanup
theclaymethod/unslop
Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Fcr Writing Style
What does Fcr Writing Style do?
A skill your agent uses when drafting or polishing a Field Crops Research (FCR) manuscript so it reads for a general agronomy/crop-science audience, follows FCR structure, and meets the format…. Fcr Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or polishing a Field Crops Research (FCR) manuscript so it reads for a general agronomy/crop-science audience, follows FCR structure, and meets the format expectations (abstract <=400 words, 3-5 highlights of <=85 characters, grammatically sound English, concise results, a discussion that interprets rather than repeats).
When should I use Fcr Writing Style?
Fcr Writing Style fits situations like: polishing a Field Crops Research (FCR) manuscript so it reads for a general agronomy/crop-science audience; follows FCR structure; meets the format expectations (abstract <=400 words; 3-5 highlights of <=85 characters.
How do I install Fcr Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-writing-style -a claude-code`. Or copy the skill folder (Field-Crops-Research-Skills/skills/fcr-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/fcr-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Fcr Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-writing-style -a codex`. Or copy the skill folder (Field-Crops-Research-Skills/skills/fcr-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/fcr-writing-style in your project. Codex loads it when a task matches its description.
Can I use Fcr Writing Style 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 brycewang-stanford/Awesome-Journal-Skills --skill fcr-writing-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fcr-writing-style, .gemini/skills/fcr-writing-style, .github/skills/fcr-writing-style and .opencode/skills/fcr-writing-style in your project.
What does Fcr Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Fcr Writing Style is instructions for the agent only.
Does Fcr Writing Style 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 Fcr Writing Style 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 Fcr Writing Style use?
Fcr Writing Style is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fcr Writing Style use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Fcr Writing Style?
Skills that share tags, products or a category with Fcr Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fcr Writing Style?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.