Agent skill

Jpart Submission

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

MITAuto-check passed

Install Jpart Submission

skills CLI

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

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

GitHub CLI

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

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-submission -a codex

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

GitHub CLI

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

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

GitHub CLI

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

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

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

At a glance

Double-blind anonymization
SKILL.md covers When to trigger, Process facts (verify volatile…, Preflight checklist and Anti-patterns, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
OUP author-date style

What it does

Jpart Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-submission preflight for the Journal of Public Administration Research and Theory (JPART) via Editorial Express — word/format limits, double-blind anonymization, OUP author-date style, keywords, Data Availability Statement, and declarations. Final checks; it does not draft content.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `templates/checklist.md`).

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

Double-blind anonymization
OUP author-date style
Data Availability Statement

Example prompts

“/jpart-submission”

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 Submission loads about 1.2k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 471 words of instructions outside code blocks.

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

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). 471 words, ~1,219 tokens.

Download SKILL.mdSave it as .claude/skills/jpart-submission/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: jpart-submission
description: Use when running the final pre-submission preflight for the Journal of Public Administration Research and Theory (JPART) via Editorial Express — word/format limits, double-blind anonymization, OUP author-date style, keywords, Data Availability Statement, and declarations. Final checks; it does not draft content.

Submission Preflight (jpart-submission)

The last check before pressing submit on Editorial Express. JPART is double-blind, so the most common avoidable failure is an under-anonymized manuscript; the second is forgetting that the word cap includes the abstract, tables, and references. Verify volatile specifics on the official page first.

When to trigger

"Submitting tomorrow" — last pass before upload
Unsure which files/metadata Editorial Express expects
Confirming the word cap is met and the manuscript is properly anonymized

Process facts (verify volatile items on the official page)

Owner / publisher: Public Management Research Association (PMRA) / Oxford University Press (OUP).
Editors (re-verified 2026-06-22): Editor-in-Chief Ole Helby Petersen and Co-Editor Kim Sass Mikkelsen (both Roskilde University), serving a four-year term; re-verify the masthead on the live Editorial Board page before relying on it.
Portal: Editorial Express (editorialexpress.com/jpart). Submit one PDF containing title, abstract, text, references, all tables/figures, plus any appendices.
Review model: double-blind — anonymize the manuscript; identifying info (name, funding, acknowledgments) goes on the cover sheet only.
Length: no longer than ~12,000 words, including abstract, tables, and references (检索于 2026-06-22；以官网为准).
Abstract: state theoretical approach, method and data, results, and implications for theory (no fixed word limit stated — 待核实).
Keywords: 3–5; the first three should indicate theory, research theme, and method.
Style: OUP author-date; alphabetical reference list with DOIs.
Data policy: authors must, where ethically possible, publicly release data and code as a condition of publication, with a mandatory Data Availability Statement (see jpart-transparency-and-data).
Fee: no submission fee (re-verified 2026-06-22); open-access publication requires an OUP-handled APC after acceptance (current figure 待核实 — confirm on the OUP page if choosing open access).
ORCID: not confirmed as required on the guidelines page (待核实).

Preflight checklist

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

Length & format

Manuscript ≤ ~12,000 words including abstract, tables, and references
Abstract states theory → method/data → results → implications for theory
3–5 keywords; first three signal theory / research theme / method
OUP author-date citations; reference list alphabetical with DOIs

No author names, affiliations, funding, or acknowledgments in the manuscript
Self-citations phrased in the third person; no "as we showed in…"
Identifying file metadata stripped (document properties, comments)
Separate cover sheet prepared with name/funding/acknowledgments
Pre-registration report blinded (hyperlinks anonymized) or placed on the cover sheet

Transparency & compliance

Data Availability Statement drafted; data + code staged for public release
Ethics / IRB / human-subjects compliance addressed
Original work; not under review elsewhere
Online supplement/appendix uploaded if used

Anti-patterns

Leaving author identifiers in the text, funding lines, or file metadata (breaks double-blind)
Forgetting the word cap counts the abstract, tables, and references (a common overrun)
An abstract that omits the theoretical approach or implications for theory
Submitting without a Data Availability Statement / public data-and-code plan
Budgeting a submission fee that is not charged (verify; the APC applies only to open access)

Output format

【Length】≤ ~12,000 words incl. abstract/tables/references? [Y/N]
【Anonymized】text + self-refs + file metadata clean; cover sheet separate? [Y/N]
【Abstract】theory → method/data → results → implications for theory? [Y/N]
【Keywords】3-5, theory/theme/method first? [Y/N]
【OUP author-date + DOIs】[Y/N]
【Data Availability Statement + public package】[Y/N]
【Next】await decision → jpart-rebuttal on R&R

Supplementary resources

./templates/checklist.md — full pre-submission self-check
../../resources/external_tools.md — reference managers, anonymization, repro tooling
../../resources/official-source-map.md — official JPART URLs behind every fact in this pack

Files

SKILL.md and 1 other file in Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-submission of brycewang-stanford/Awesome-Journal-Skills.

SKILL.md
templates/checklist.md

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Jpart Submission 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 Submission compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Jpart Submission this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.2k	Automated safety check: Pass	MIT	14 days ago
Running CI PreflightPostHog/posthog	40k	—	~1.5k	Automated safety check: Pass	Custom licence	yesterday
Finalize Agent Promptgithub/awesome-copilot	40k	1 repos	~224	Automated safety check: Pass	MIT	2 days ago
Azure Deployment Preflightgithub/awesome-copilot	40k	1 repos	~1.9k	Automated safety check: Pass	MIT	2 days ago
Implementation Final Reviewopenai/openai-agents-python	30k	—	~2k	Automated safety check: Pass	MIT	2 days ago
Preflightopenwpm/OpenWPM	1.4k	—	~670	Automated safety check: Pass	Custom licence	6 days ago

Similar skills

Running CI Preflight
PostHog/posthog
Official
Catch the deterministic CI failures reachable from your diff before pushing, with hogli ci:preflight.
40k GitHub stars~1.5k tokensUpdated yesterday
Backend & APIsAuto-check passed
Finalize Agent Prompt
github/awesome-copilot
Official
Finalize prompt file using the role of an AI agent to polish the prompt for the end user.
40k GitHub starsUsed in 1 repo~224 tokens
Auto-check passed
Azure Deployment Preflight
github/awesome-copilot
Official
Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks.
40k GitHub starsUsed in 1 repo~1.9k tokens
DevOps & CloudAuto-check passed
Implementation Final Review
openai/openai-agents-python
Official
Review completed implementation changes before final verification.
30k GitHub stars~2k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Preflight
openwpm/OpenWPM
Use BEFORE implementing code in a crosslink-tracked project — loads .crosslink/rules/global.md, the language rules for detected manifests, the project rules, and the active tracking-<mode.md.
1.4k GitHub stars~670 tokensUpdated 6 days ago
Auto-check passed
Preflight
openfootmanager/openfootmanager
Verify a pull request with the frontend scripts, default and MCP backend tests and clippy, formatting, architecture checks and review evidence.
1.1k GitHub stars~1.3k tokensUpdated yesterday
DevelopmentAuto-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 Submission

What does Jpart Submission do?

A skill your agent uses when running the final pre-submission preflight for the Journal of Public Administration Research and Theory (JPART) via Editorial Express — word/format limits, double-blind…. Jpart Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-submission preflight for the Journal of Public Administration Research and Theory (JPART) via Editorial Express — word/format limits, double-blind anonymization, OUP author-date style, keywords, Data Availability Statement, and declarations.

When should I use Jpart Submission?

Jpart Submission fits situations like: double-blind anonymization; OUP author-date style; data Availability Statement.

How do I install Jpart Submission in Claude Code?

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

How do I install Jpart Submission in Codex?

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

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

What does Jpart Submission need to run?

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

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

Jpart Submission 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 Submission use?

About 1.2k tokens (SKILL.md is roughly 4.9k 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 Submission?

Skills that share tags, products or a category with Jpart Submission: Running CI Preflight (PostHog/posthog, 40k stars), Finalize Agent Prompt (github/awesome-copilot, 40k stars), Azure Deployment Preflight (github/awesome-copilot, 40k stars) and Implementation Final Review (openai/openai-agents-python, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jpart Submission?

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 Submission

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Submission Preflight (jpart-submission)

When to trigger

Process facts (verify volatile items on the official page)

Preflight checklist

Length & format

Anonymity (double-blind)

Transparency & compliance

Anti-patterns

Output format

Supplementary resources

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Questions about Jpart Submission