Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
A skill your agent uses when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section…
Install Fse Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-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/FSE-Skills/skills/fse-writing-style .claude/skills/fse-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 "fse-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-writing-style into .claude/skills/fse-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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/FSE-Skills/skills/fse-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 fse-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-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/FSE-Skills/skills/fse-writing-style .agents/skills/fse-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 "fse-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-writing-style into .agents/skills/fse-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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 fse-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-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/FSE-Skills/skills/fse-writing-style .cursor/skills/fse-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 "fse-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-writing-style into .cursor/skills/fse-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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 FSE-Skills/skills/fse-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 fse-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-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/FSE-Skills/skills/fse-writing-style .gemini/skills/fse-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 "fse-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-writing-style into .gemini/skills/fse-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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 fse-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 fse-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/FSE-Skills/skills/fse-writing-style .github/skills/fse-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 "fse-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-writing-style into .github/skills/fse-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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 fse-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 fse-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/FSE-Skills/skills/fse-writing-style .opencode/skills/fse-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 "fse-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-writing-style into .opencode/skills/fse-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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
fse-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 519 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section…
- Revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page
- SKILL.md covers Revision rules, Empirical-SE paper skeleton, Sentence-level rewrites and Threats-to-validity discipline, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Research-question contracts
What it does
Fse Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section that argues rather than recites, evidence proportional to the claim, double-anonymous wording, and disciplined use of the ACM-template page budget.
Its SKILL.md is about 1.2k 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, Hypothesis generation and Programmatic SEO. 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
- Revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page
- Research-question contracts
- A threats-to-validity section that argues rather than recites
- Evidence proportional to the claim
Example prompts
- “/fse-writing-style”
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
Fse Writing Style loads about 1.2k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 519 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). 519 words, ~1,204 tokens.
Download SKILL.mdSave it as
.claude/skills/fse-writing-style/SKILL.md (or your agent's skills folder).- name
- fse-writing-style
- description
- Use when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section that argues rather than recites, evidence proportional to the claim, double-anonymous wording, and disciplined use of the ACM-template page budget.
FSE Writing Style
Use this when revising the main paper. FSE papers are PACMSE journal articles read by SE empiricists, so they need a software-engineering contribution stated in the first page and evidence a reviewer trusts. The failure this skill prevents is a technically fine paper that reads like a systems demo or an ML result with an SE title glued on.
Revision rules
- Lead with the SE contribution: the problem a practitioner recognizes, why the current state is inadequate, the contribution (technique and/or finding), the evidence, and what changes for software engineering.
- State research questions as contracts. Each RQ should name what is measured and how it will be judged; every RQ must be answered explicitly in the results, and no result should exist without an RQ it serves.
- Pair every claim with proportional evidence — real subjects, a fair baseline, a statistic with an effect size, or a qualitative code with agreement — not adjectives.
- Argue threats to validity; do not recite them. Name the construct, internal, external, and conclusion threats that actually bite this study, and say what you did to bound each. A boilerplate threats paragraph is a tell that the author has not stressed their own claims.
- Respect the page budget as a design constraint, not a formatting afterthought — the ACM template is generous but finite, and a study that only fits by shrinking threats or method is over-scoped.
- Maintain heavy double-anonymity in self-citations, tool names, acknowledgements, funding, and the data-availability wording.
Empirical-SE paper skeleton
| Section | Job it must do | Common failure |
|---|---|---|
| Intro | Problem, inadequacy, contribution, evidence preview, SE payoff — first page | Leads with a technology trend, not a problem |
| Background/Motivation | Why a practitioner or the field needs this now | Motivation by assertion, no grounding |
| Approach / Study design | The technique or the RQs + protocol, reproducibly | Method described too thinly to re-run |
| Evaluation | Each RQ answered with proportional evidence | Metrics that proxy for the claim rather than test it |
| Threats to validity | The threats that bite, each bounded | Generic list untethered from this study |
| Related work | Delta-first positioning against SE literature | Catalog of citations with no contrast |
Show full SKILL.md (170 more words)Show less
Sentence-level rewrites
| Draft pattern | FSE-safe rewrite |
|---|---|
| "Our tool significantly improves..." | "detects X% more defects (95% CI ...) than <baseline> on <N real projects>" |
| "We evaluate on a large dataset." | "We evaluate on <N> projects sampled by <criterion>, listed in the artifact" |
| "Results show our approach works well." | "RQ2: developers acted on <fraction> of comments (effect size ...); threats in §5.2" |
| "State-of-the-art performance." | Claim scoped to the subjects, metrics, and regime actually tested |
| "The LLM understands the code." | "the model's output matched <criterion> in <fraction> of cases" |
Threats-to-validity discipline
[Construct] does the metric measure the SE outcome you claim? (e.g. proxy for causation)
[Internal] could something other than your technique explain the effect? (confounds, tuning)
[External] to which projects/languages/teams does the finding generalize?
[Conclusion] are the statistics appropriate; multiple comparisons corrected; variance reported?
-> for each that bites: state it, then state the mitigation, next to the affected resultVignette: compressing a three-RQ study
A draft with three RQs, nine figures, and a sprawling background: keep all three RQ answers, the two figures that carry the headline findings, and a threats subsection per RQ; move secondary plots and full protocol tables to the artifact with explicit forward references; cut background to what the argument needs. The test of a good cut: a reviewer should be able to answer "what did each RQ find, and what threatens it?" from the body alone.
Output format
[Writing diagnosis] clear / under-motivated / over-claimed / evidence-mismatched / over-scoped
[First-page fix] <new framing leading with the SE contribution>
[RQ audit] <RQ -> metric -> where answered -> proportional? yes/no>
[Threats fix] <threat that bites -> mitigation to add, placed by the result>
[Anonymity edits] <tool names / self-citations / links to rewrite>© 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 FSE-Skills/skills/fse-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Fse 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 |
|---|---|---|---|---|---|---|
| Fse Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Brand Voice Content Creatordavila7/claude-code-templates | 33k | 3 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Humanities Writing Companiontizzy916/humanities-writing-companion | 436 | — | ~3.4k | Automated safety check: Pass | CC-BY-NC-4.0 | |
| Caption Writerstevenflanagan1/social-ai-team | 244 | — | ~2.9k | Automated safety check: Pass | None | |
| Content Creatorsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Brand Voice Guidelhfer/claude-howto-zh-cn | 2.3k | — | ~178 | Automated safety check: Pass | MIT |
Similar skills
Humanities Writing Companion
tizzy916/humanities-writing-companion
Help with humanities scholarly writing: sharpen research questions, map supplied readings, plan and draft arguments, review chapters, preserve authorial voice, and respond to reviewers.
Caption Writer
stevenflanagan1/social-ai-team
Writes on-brand social media captions for SMBs. An agent skill from stevenflanagan1/social-ai-team.
Content Creator
sickn33/agentic-awesome-skills
Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.
Brand Voice Guide
lhfer/claude-howto-zh-cn
Keeps marketing copy and customer messages in one consistent brand voice, using a defined mission, tone, writing rules and lists of preferred and avoided terms.
Brand Voice Guidelines in Ukrainian
luongnv89/claude-howto
Keeps marketing copy, customer messages and public content in one brand voice, with tone rules, preferred and banned wording and sample sentences; written in Ukrainian.
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
Questions about Fse Writing Style
What does Fse Writing Style do?
A skill your agent uses when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section…. Fse Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section that argues rather than recites, evidence proportional to the claim, double-anonymous wording, and disciplined use of the ACM-template page budget.
When should I use Fse Writing Style?
Fse Writing Style fits situations like: revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page; research-question contracts; A threats-to-validity section that argues rather than recites; evidence proportional to the claim.
How do I install Fse Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-writing-style -a claude-code`. Or copy the skill folder (FSE-Skills/skills/fse-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/fse-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Fse Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-writing-style -a codex`. Or copy the skill folder (FSE-Skills/skills/fse-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/fse-writing-style in your project. Codex loads it when a task matches its description.
Can I use Fse 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 fse-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/fse-writing-style, .gemini/skills/fse-writing-style, .github/skills/fse-writing-style and .opencode/skills/fse-writing-style in your project.
What does Fse Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Fse Writing Style is instructions for the agent only.
Does Fse 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 Fse 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 Fse Writing Style use?
Fse 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 Fse Writing Style use?
About 1.2k tokens (SKILL.md is roughly 4.8k 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 Fse Writing Style?
Skills that share tags, products or a category with Fse Writing Style: Brand Voice Content Creator (davila7/claude-code-templates, 33k stars), Humanities Writing Companion (tizzy916/humanities-writing-companion, 436 stars), Caption Writer (stevenflanagan1/social-ai-team, 244 stars) and Content Creator (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fse 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.