Est Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing the prose of an Environmental Science & Technology (ES&T) manuscript so it reads for a multidisciplinary audience in ACS style and fits the…
A skill your agent uses when the prose, intro, and abstract are the bottleneck for a Journal of Financial Markets (JFM) manuscript — making the trading mechanism land for microstructure insiders.
Install Jfm Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-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/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style .claude/skills/jfm-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 "jfm-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style into .claude/skills/jfm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-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/Journal-of-Financial-Markets-Skills/skills/jfm-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 jfm-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-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/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style .agents/skills/jfm-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 "jfm-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style into .agents/skills/jfm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-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 jfm-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-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/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style .cursor/skills/jfm-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 "jfm-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style into .cursor/skills/jfm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-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 Journal-of-Financial-Markets-Skills/skills/jfm-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 jfm-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-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/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style .gemini/skills/jfm-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 "jfm-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style into .gemini/skills/jfm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-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 jfm-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 jfm-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/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style .github/skills/jfm-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 "jfm-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style into .github/skills/jfm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-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 jfm-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 jfm-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/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style .opencode/skills/jfm-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 "jfm-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-writing-style into .opencode/skills/jfm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-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
jfm-writing-style- GitHub stars
- 1.2k
- Token cost
- ~2.2k tokens
- SKILL.md length
- 1,167 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the prose, intro, and abstract are the bottleneck for a Journal of Financial Markets (JFM) manuscript — making the trading mechanism land for microstructure insiders.
- Works in 3 steps: Lead with the trading-process mechanism,… → Get the institutions exactly right. Name… → Claim only what the design supports.…
- Tasks that involve Brand voice and tone
- SKILL.md covers When to trigger, The JFM voice, Writing the intro and abstract and Before / after (illustrative), plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Jfm Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when the prose, intro, and abstract are the bottleneck for a Journal of Financial Markets (JFM) manuscript — making the trading mechanism land for microstructure insiders. Late-stage polish; it does not invent evidence or citations.
Its SKILL.md is about 2.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, Trading and backtesting and Citation management. 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
- Tasks that involve Brand voice and tone
- Tasks that involve Trading and backtesting
- Tasks that involve Citation management
Example prompts
- “/jfm-writing-style”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Lead with the trading-process mechanism, fast. The first paragraph should name the market object (spread, depth, order flow, price…
- Get the institutions exactly right. Name the venue, the matching/priority rule, the order types, the tick size, the relevant regulation…
- Claim only what the design supports. Prefer "spreads narrow by X bps for treated stocks" to "liquidity improves." State economic magnitude…
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
Jfm Writing Style loads about 2.2k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 1,167 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). 1,167 words, ~2,202 tokens.
Download SKILL.mdSave it as
.claude/skills/jfm-writing-style/SKILL.md (or your agent's skills folder).- name
- jfm-writing-style
- description
- Use when the prose, intro, and abstract are the bottleneck for a Journal of Financial Markets (JFM) manuscript — making the trading mechanism land for microstructure insiders. Late-stage polish; it does not invent evidence or citations.
Writing Style (jfm-writing-style)
When to trigger
- The mechanism, design, and exhibits are stable and it is time to write the intro and abstract (not before)
- The abstract describes data and methods but never states the microstructure result
- The intro reads like a broad-finance paper and does not signal "this is microstructure" in the first paragraph
- Institutional detail (market rules, order types, venue mechanics) is vague where precision is the JFM currency
- A coauthor's draft over-claims generality JFM referees will not grant
The JFM voice
JFM prose is precise about market mechanics and disciplined about claims. The reader is a microstructure specialist who wants the institutional detail right and the mechanism stated plainly. Three habits define the house style:
- Lead with the trading-process mechanism, fast. The first paragraph should name the market object (spread, depth, order flow, price discovery) and the economic force. A JFM intro that buries the mechanism behind two paragraphs of general-finance throat-clearing reads as mis-targeted.
- Get the institutions exactly right. Name the venue, the matching/priority rule, the order types, the tick size, the relevant regulation. Microstructure referees notice when "the exchange" is used where the actual mechanism matters. This precision is the contribution's credibility.
- Claim only what the design supports. Prefer "spreads narrow by X bps for treated stocks" to "liquidity improves." State economic magnitude in market terms (bps, depth, impact), not just statistical significance.
Writing the intro and abstract
Abstract: in ~4-6 sentences — (1) the market question, (2) the data/setting in microstructure terms, (3) the identifying variation, (4) the result with a magnitude in market units, (5) the mechanism it implies, (6) one sentence of contribution. Confirm the exact abstract word limit on the guide for authors (检索于 2026-06；以官网为准 — 待核实).
Intro (the funnel): (1) the market phenomenon and why how-it-trades matters; (2) what we do and find, in one tight paragraph with the headline magnitude; (3) the identifying variation / measurement advance; (4) placement vs. the microstructure lineage (one paragraph, not a survey); (5) why JFM and not a broad-finance frame — the specialist depth. Keep the contribution sentence verbatim-consistent with the abstract and the title.
Throughout: define each liquidity measure on first use; keep units consistent with the exhibits; resist the passive "it is found that."
Before / after (illustrative)
Before (broad-finance framing): "We examine the relationship between trading activity and asset prices using a large dataset of intraday transactions and find economically and statistically significant effects." This could be any finance paper; it states no mechanism and no magnitude.
After (JFM voice): "When a stock joins the pilot's wider-tick group, effective spreads widen by 12 bps and quoted depth at the touch nearly doubles, while the permanent (adverse-selection) component is unchanged — implying the wider tick raises liquidity-supply rents without altering information asymmetry." It names the shock, the market objects, the magnitudes in market units, and the mechanism it identifies. That is the sentence a microstructure editor wants in paragraph one.
The mechanism sentence
Every JFM paper should have one sentence a reader could quote as "what this paper shows about how markets work." It names the cause, the market object, the magnitude, and the channel: "A wider tick raises liquidity-supplier rents — depth doubles while the adverse-selection component is flat — so the cost falls on uninformed traders." Draft this sentence early and let it discipline the whole paper; if you cannot write it cleanly, the contribution is not yet sharp. It should appear (in some form) in the abstract, the intro, and the conclusion, keeping the paper anchored to a single mechanism rather than a list of correlations.
House-style details that signal fluency
- Use the field's terms precisely: effective vs. quoted spread, permanent vs. temporary impact, adverse selection vs. inventory cost, lit vs. dark, maker-taker. Loose usage reads as an outsider.
- Report magnitudes in the unit a trader thinks in (bps, cents, shares, microseconds), and benchmark against the average (a 2-bps effect on a 5-bps spread is large; on a 200-bps spread it is noise).
- Name dates and rules ("after Reg NMS, effective October 2007") rather than vague time references.
- Keep the active voice and a single, consistent label for each measure throughout.
Show full SKILL.md (479 more words)Show less
Pruning the broad-finance throat-clearing
A common drag on microstructure intros is two opening paragraphs of general motivation ("financial markets are central to the economy…") before the specific question appears. A microstructure editor wants the trading-process question and the headline in the first half-page. Cut generic scene-setting to one or two sentences and move quickly to the market mechanism, the setting, and what you find. The same discipline applies to the literature review: place the paper in its sub-field in a tight paragraph rather than surveying. Density and specificity read as expertise; broad preamble reads as a paper hedging about whether it really belongs at JFM.
Checklist
- First paragraph names the trading-process object and the economic force
- Abstract states the result with a magnitude in market units, not just significance
- Institutional detail (venue, rules, order types, tick size, regulation) is exact, not generic
- Claims are sized in bps/depth/impact and bounded by the design
- The microstructure lineage is placed in the intro without a full literature survey
- One sentence says why JFM, not a broad-finance journal
- Contribution sentence is consistent across title, abstract, and intro
Calibrating claims to a skeptical specialist
Microstructure referees are unusually quick to flag over-claiming because they know how many ways a liquidity result can be an artifact. Match the verb to the evidence: a clean randomized shock supports "causes"; a panel regression supports "is associated with"; a heterogeneity pattern supports "consistent with [mechanism]," not "proves." Name the channel only when the design isolates it — "spreads narrow because adverse selection falls" requires showing the adverse-selection component moved, not just the total spread. State scope honestly: a result on large-cap U.S. equities is not a claim about all markets. This disciplined register reads as competence to a specialist, whereas sweeping language reads as naivety and invites a harsher review.
Anti-patterns
- An abstract that lists data and methods but never states the microstructure finding
- Generic institutional descriptions ("trades happen on the exchange") where the mechanism matters
- Over-claiming "liquidity improves" without magnitude or sign of the channel
- A broad-finance intro framing that hides the microstructure cut
- Significance-driven prose ("highly significant") instead of economic magnitude
- Polishing prose before the mechanism, measurement, and identification are settled
Sequencing the write so the mechanism survives editing
Write in the order that protects the contribution. First lock the results section prose around the stable exhibits, stating each magnitude in market units. Then write the mechanism / interpretation paragraphs that connect the numbers to the trading-process force, since that is what a microstructure editor evaluates. Only then write the intro, reverse-engineered from the results so the headline magnitude in paragraph two matches the tables exactly. Write the abstract last, distilled from the finished intro. This order prevents the common failure where a beautifully written intro promises a sharper or broader result than the exhibits deliver — a gap microstructure referees notice immediately and read as over-claiming.
Output format
【Journal】Journal of Financial Markets (JFM)
【Skill】jfm-writing-style
【Mechanism in para 1】trading-process object named early? [Y/N]
【Abstract】result + market-unit magnitude stated? [Y/N]
【Institutions】venue/rules/order-types/tick exact? [Y/N]
【Claim discipline】sized in bps/depth/impact, design-bounded? [Y/N]
【Why JFM line】present in intro? [Y/N]
【Source status】abstract limit / style verified or 待核实
【Next skill】jfm-submission© 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 Journal-of-Financial-Markets-Skills/skills/jfm-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jfm 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 |
|---|---|---|---|---|---|---|
| Jfm Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Est Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~798 | Automated safety check: Pass | None | |
| Jaar Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~760 | Automated safety check: Pass | None | |
| Jcf Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~669 | Automated safety check: Pass | None | |
| Jpe Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Mgsci Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~875 | Automated safety check: Pass | None |
Similar skills
Jaar Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing the prose of a Journal of the American Academy of Religion (JAAR) article so it is clear, analytic, gender-neutral, and readable across the study…
Jcf Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing prose for a Journal of Corporate Finance (JCF) manuscript — the ≤250-word abstract, 1–7 keywords, author-date (Harvard) in-text citations, and the…
Jpe Writing Style
franklee16/academic-research-skills
A skill your agent uses when polishing the prose of a Journal of Political Economy (JPE) manuscript into its spare, analytical, economics-first register.
Mgsci Writing Style
franklee16/academic-research-skills
A skill your agent uses when polishing the prose of a Management Science (INFORMS) manuscript — front-loading the result, keeping notation lean, writing for a cross-department reader, and conforming…
Pmla Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing the prose of a PMLA (Publications of the Modern Language Association) essay so it reads clearly for a broad membership of language and literature…
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 Jfm Writing Style
What does Jfm Writing Style do?
A skill your agent uses when the prose, intro, and abstract are the bottleneck for a Journal of Financial Markets (JFM) manuscript — making the trading mechanism land for microstructure insiders. Jfm Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when the prose, intro, and abstract are the bottleneck for a Journal of Financial Markets (JFM) manuscript — making the trading mechanism land for microstructure insiders.
When should I use Jfm Writing Style?
Jfm Writing Style fits situations like: tasks that involve Brand voice and tone; tasks that involve Trading and backtesting; tasks that involve Citation management.
How do I install Jfm Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-writing-style -a claude-code`. Or copy the skill folder (Journal-of-Financial-Markets-Skills/skills/jfm-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jfm-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Jfm Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-writing-style -a codex`. Or copy the skill folder (Journal-of-Financial-Markets-Skills/skills/jfm-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jfm-writing-style in your project. Codex loads it when a task matches its description.
Can I use Jfm 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 jfm-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/jfm-writing-style, .gemini/skills/jfm-writing-style, .github/skills/jfm-writing-style and .opencode/skills/jfm-writing-style in your project.
What does Jfm Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Jfm Writing Style is instructions for the agent only.
Does Jfm 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 Jfm 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 Jfm Writing Style use?
Jfm 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 Jfm Writing Style use?
About 2.2k tokens (SKILL.md is roughly 8.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 Jfm Writing Style?
Skills that share tags, products or a category with Jfm Writing Style: Est Writing Style (franklee16/academic-research-skills, 223 stars), Jaar Writing Style (franklee16/academic-research-skills, 223 stars), Jcf Writing Style (franklee16/academic-research-skills, 223 stars) and Jpe Writing Style (franklee16/academic-research-skills, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jfm 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.