Agent skill

Jpart Writing Style

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

Install Jpart Writing Style

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-writing-style -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpart-writing-style --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ 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-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style .claude/skills/jpart-writing-style && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "jpart-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style into .claude/skills/jpart-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-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

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style

Type 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-writing-style -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpart-writing-style --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style .agents/skills/jpart-writing-style && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "jpart-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style into .agents/skills/jpart-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-writing-style -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpart-writing-style --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style .cursor/skills/jpart-writing-style && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "jpart-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style into .cursor/skills/jpart-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-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

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-writing-style -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpart-writing-style --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style .gemini/skills/jpart-writing-style && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "jpart-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style into .gemini/skills/jpart-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-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.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpart-writing-style

Installs 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).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-writing-style -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ 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-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style .github/skills/jpart-writing-style && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "jpart-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style into .github/skills/jpart-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-writing-style -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpart-writing-style --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style .opencode/skills/jpart-writing-style && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "jpart-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style into .opencode/skills/jpart-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-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: jpart-writing-style
GitHub stars: 1.2k
Token cost: ~1.3k tokens
SKILL.md length: 575 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 4 steps: Front-load the theoretical contribution.… → Name the mechanism in plain language.… → Argument-first prose. Lead with claims… → …
Polishing a Journal of Public Administration Research and Theory (JPART) manuscript so it reads as theory-plus-rigor
SKILL.md covers When to trigger, Lead with theory, support with…, Format to JPART / OUP style and Abstract stress test, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Jpart Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or polishing a Journal of Public Administration Research and Theory (JPART) manuscript so it reads as theory-plus-rigor, follows OUP author-date style, and fits the ~12,000-word cap that includes the abstract, tables, and references. Tightens prose and format; it does not invent content.

Its SKILL.md is about 1.3k 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 Journal of Public Administration Research and Theory (JPART) manuscript so it reads as theory-plus-rigor
Follows OUP author-date style
000-word cap that includes the abstract

Example prompts

“/jpart-writing-style”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Front-load the theoretical contribution. By the end of the introduction the reader knows the PA
Name the mechanism in plain language. Don't make the reader infer why the relationship holds —
Argument-first prose. Lead with claims about the theory; use evidence to support them. Avoid "the
Signpost lightly. Clear structure, but no seven-section roadmap padding the word count.

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

Jpart Writing Style loads about 1.3k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 575 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~82
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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). 575 words, ~1,302 tokens.

Download SKILL.mdSave it as .claude/skills/jpart-writing-style/SKILL.md (or your agent's skills folder).

name: jpart-writing-style
description: Use when drafting or polishing a Journal of Public Administration Research and Theory (JPART) manuscript so it reads as theory-plus-rigor, follows OUP author-date style, and fits the ~12,000-word cap that includes the abstract, tables, and references. Tightens prose and format; it does not invent content.

Writing Style (jpart-writing-style)

A JPART paper must read as a public-management theory contribution carried by rigorous evidence, formatted to the journal's OUP author-date style, and disciplined to the word cap. JPART's own guidance asks the abstract to state the theoretical approach, method and data, results, and implications for theory — the paper should follow the same arc.

When to trigger

Drafting the introduction, framing the contribution, or final polish
Over the word cap and needing to cut without losing the argument
Writing the abstract (theory → method/data → results → implications for theory)
Aligning citations/headings/format to OUP author-date style before submission

Lead with theory, support with rigor

Front-load the theoretical contribution. By the end of the introduction the reader knows the PA theory at stake, the mechanism, the design, the headline result, and what it means for theory.
Name the mechanism in plain language. Don't make the reader infer why the relationship holds — state the public-management logic (incentives, motivation, identity, institutions).
Argument-first prose. Lead with claims about the theory; use evidence to support them. Avoid "the data show…" without saying what they show and why it matters for public management.
Signpost lightly. Clear structure, but no seven-section roadmap padding the word count.

Format to JPART / OUP style

Citations: author-date in text, alphabetical reference list with DOIs; keep one consistent style (manage with Zotero/BibTeX).
Keywords: 3–5; the first three should signal theory, research theme, and method (JPART convention).
Abstract: state theoretical approach → method and data → results → implications for theory.
Anonymize: JPART is double-blind — omit your name and funding from the manuscript, cite your own work in the third person, and keep acknowledgments/funding on the cover sheet only.

Abstract stress test

Draft the abstract as four disciplined sentences before polishing the manuscript:

Theory: What public-management theory or mechanism is at stake?
Method/data: What design, case, sample, and data identify or illuminate the mechanism?
Result: What is the directional, substantive finding in units a reader can understand?
Implication for theory: What should the field believe, qualify, or test differently?

If sentence 1 could describe any public-sector setting, the paper is not framed tightly enough. If sentence 4 says only "policy implications," route back to jpart-topic-selection or jpart-theory-building.

Show full SKILL.md (207 more words)Show less

Fit the word cap (~12,000 words including abstract, tables, references)

Move balance tables, full specs, and extended robustness to the online supplement.
Cut throat-clearing and literature dumps; engage the conversation, not every paper (see jpart-literature-positioning).
Because the cap counts references, prune citation padding; keep the works that constitute the debate.
Prefer one decisive marginal-effects figure to three redundant tables.

Cut in this order when over budget:

Generic PA throat-clearing that does not define the mechanism.
Literature paragraphs with no role in the contribution claim.
Redundant robustness prose already visible in tables or supplement.
Repeated method description across text, exhibit notes, and appendix.
Secondary mechanisms that cannot be adjudicated by the design.

Do not cut the theory contribution, scope conditions, or design limits; those are what make the paper reviewable at JPART.

Anti-patterns

An empirics-first intro that never states the theoretical contribution (reads atheoretical)
Burying the mechanism and the "implications for theory" in the conclusion
An abstract that reports results but never names the theoretical approach
Mixed citation styles; acknowledgments or self-references that break double-blind anonymity
Forgetting that the word cap counts the abstract, tables, and references

Output format

【Theory stated by end of intro?】[Y/N]
【Mechanism named in plain language?】[Y/N]
【Abstract】theory → method/data → results → implications for theory? [Y/N]
【Cut order used】generic setup / unused literature / redundant robustness / repeated methods / secondary mechanisms
【Word count】≤ ~12,000 incl. abstract/tables/references? [Y/N]
【OUP author-date + 3-5 keywords + anonymized】[Y/N]
【Next】jpart-transparency-and-data

Supplementary resources

../../resources/worked-examples/01-introduction.md — before→after JPART-style introduction
../../resources/official-source-map.md — word limit, abstract template, keyword convention, anonymity

Files

Just SKILL.md in Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Jpart 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.

Jpart Writing Style compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Jpart Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.3k	Automated safety check: Pass	MIT	14 days ago
Crim Writing Stylefranklee16/academic-research-skills	223	1 repos	~975	Automated safety check: Pass	None	23 days ago
Est Writing Stylefranklee16/academic-research-skills	223	1 repos	~798	Automated safety check: Pass	None	23 days ago
Jaar Writing Stylefranklee16/academic-research-skills	223	1 repos	~760	Automated safety check: Pass	None	23 days ago
Jcf Writing Stylefranklee16/academic-research-skills	223	1 repos	~669	Automated safety check: Pass	None	23 days ago
Joc Writing Stylefranklee16/academic-research-skills	223	1 repos	~873	Automated safety check: Pass	None	23 days ago

Similar skills

Crim Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing a Criminology (ASC / Wiley) manuscript so it reads for an interdisciplinary criminology audience, follows the journal's APA-based style, and uses…
223 GitHub starsUsed in 1 repo~975 tokens
Writing & ContentAuto-check passed
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…
223 GitHub starsUsed in 1 repo~798 tokens
Writing & ContentAuto-check passed
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…
223 GitHub starsUsed in 1 repo~760 tokens
Writing & ContentAuto-check passed
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…
223 GitHub starsUsed in 1 repo~669 tokens
Writing & ContentAuto-check passed
Joc Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing a Journal of Communication (JoC) manuscript so it reads for the whole field, follows APA 7th edition, and fits the limits (main document <= 35…
223 GitHub starsUsed in 1 repo~873 tokens
Writing & ContentAuto-check passed
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.
223 GitHub starsUsed in 1 repo~1.1k tokens
Writing & ContentAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag 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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.6k tokensUpdated 14 days ago
Auto-check passed

Questions about Jpart Writing Style

What does Jpart Writing Style do?

A skill your agent uses when drafting or polishing a Journal of Public Administration Research and Theory (JPART) manuscript so it reads as theory-plus-rigor, follows OUP author-date style, and fits…. Jpart Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or polishing a Journal of Public Administration Research and Theory (JPART) manuscript so it reads as theory-plus-rigor, follows OUP author-date style, and fits the ~12,000-word cap that includes the abstract, tables, and references.

When should I use Jpart Writing Style?

Jpart Writing Style fits situations like: polishing a Journal of Public Administration Research and Theory (JPART) manuscript so it reads as theory-plus-rigor; follows OUP author-date style; 000-word cap that includes the abstract.

How do I install Jpart Writing Style in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-writing-style -a claude-code`. Or copy the skill folder (Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jpart-writing-style in your project. Claude Code loads it when a task matches its description.

How do I install Jpart Writing Style in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-writing-style -a codex`. Or copy the skill folder (Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jpart-writing-style in your project. Codex loads it when a task matches its description.

Can I use Jpart 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 jpart-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/jpart-writing-style, .gemini/skills/jpart-writing-style, .github/skills/jpart-writing-style and .opencode/skills/jpart-writing-style in your project.

What does Jpart Writing Style need to run?

SKILL.md names no scripts, command-line tools or credentials: Jpart Writing Style is instructions for the agent only.

Does Jpart 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 Jpart 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 Jpart Writing Style use?

Jpart 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 Jpart Writing Style use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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 Jpart Writing Style?

Skills that share tags, products or a category with Jpart Writing Style: Crim Writing Style (franklee16/academic-research-skills, 223 stars), Est Writing Style (franklee16/academic-research-skills, 223 stars), Jaar Writing Style (franklee16/academic-research-skills, 223 stars) and Jcf 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 Jpart 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.

Install Jpart Writing Style

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Writing Style (jpart-writing-style)

When to trigger

Lead with theory, support with rigor

Format to JPART / OUP style

Abstract stress test

Fit the word cap (~12,000 words including abstract, tables, references)

Anti-patterns

Output format

Supplementary resources

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Related

Questions about Jpart Writing Style