Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
A skill your agent uses when planning an ESEC/FSE project timeline from venue fit through paper registration, submission, the journal-style Major Revision round, artifact evaluation, PACMSE…
Install Fse Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-workflow --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-workflow .claude/skills/fse-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-workflow into .claude/skills/fse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-workflow --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-workflow .agents/skills/fse-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-workflow into .agents/skills/fse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-workflow --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-workflow .cursor/skills/fse-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-workflow into .cursor/skills/fse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-workflow --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-workflow .gemini/skills/fse-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-workflow into .gemini/skills/fse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/fse-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-workflow into .github/skills/fse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/fse-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-workflow into .opencode/skills/fse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 598 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an ESEC/FSE project timeline from venue fit through paper registration, submission, the journal-style Major Revision round, artifact evaluation, PACMSE…
- Planning an ESEC/FSE project timeline from venue fit through paper registration
- SKILL.md covers Milestones, Backward plan from the…, Cycle-hopping: the honest… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The journal-style Major Revision round
What it does
Fse Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ESEC/FSE project timeline from venue fit through paper registration, submission, the journal-style Major Revision round, artifact evaluation, PACMSE camera-ready, and presentation, with backward-planning offsets for an empirical-SE paper and honest handling of the single-annual-deadline cycle and cycle-hopping.
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 Documents & Office. 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
- Planning an ESEC/FSE project timeline from venue fit through paper registration
- The journal-style Major Revision round
- Artifact evaluation
- PACMSE camera-ready
Example prompts
- “/fse-workflow”
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 Workflow loads about 1.2k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 598 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). 598 words, ~1,244 tokens.
Download SKILL.mdSave it as
.claude/skills/fse-workflow/SKILL.md (or your agent's skills folder).- name
- fse-workflow
- description
- Use when planning an ESEC/FSE project timeline from venue fit through paper registration, submission, the journal-style Major Revision round, artifact evaluation, PACMSE camera-ready, and presentation, with backward-planning offsets for an empirical-SE paper and honest handling of the single-annual-deadline cycle and cycle-hopping.
FSE Workflow
Use this as the project-management skill for an FSE submission. Replace every date with the current official timetable and work backwards from the HotCRP registration cutoff — which precedes the paper deadline. FSE publishes in PACMSE, so plan for a possible Major Revision round inside the review year, not just an accept/reject.
FSE is a conference whose papers are journal articles: it has no standing editor-in-chief and no article-processing charge. Rotating leadership is the per-edition General and Program/Review Co-Chairs (FSE 2026 General Chairs: Shin Hwei Tan and Foutse Khomh, verified 2026-07-09), and the cost model is registration, not APCs — PACMSE is open access. Chairs rotate yearly; re-check the organizing-committee page rather than carrying a name forward.
Milestones
- Venue fit: confirm FSE over ICSE/ASE/ISSTA and confirm the paper is ready this cycle
(
fse-topic-selection). - Evidence lock: freeze research questions, subject systems, baselines, statistics, threats, and the artifact contents.
- Registration: submit real title, abstract, authors, topics, and conflicts by the earlier registration deadline (FSE 2026: 4 Sep 2025).
- Submission: upload the anonymized PDF and Data Availability statement (FSE 2026: 11 Sep 2025; FSE 2027: 2 Oct 2026).
- Reviews: triage each comment by criterion (significance, soundness, evidence, threats, clarity, open-science).
- Major Revision (if issued): execute a tracked-change revision plus an anonymous, point-by- point response, re-read by the original reviewers.
- Decision: archive reviews, response, and every submitted version.
- Acceptance: prepare the PACMSE camera-ready, pursue ACM artifact badges on the artifact track's own deadline, register, and present.
Backward plan from the submission deadline
| Weeks out (heuristic) | Empirical-SE milestone |
|---|---|
| 10+ | Research questions fixed; subject systems and baselines chosen |
| 8 | Data collection / experiments complete; provenance and seeds logged |
| 6 | Analysis done; effect sizes and tests computed; threats drafted alongside results |
| 4 | Full draft in the ACM template; artifact assembled and anonymized |
| 3 | Internal mock review by an SE-empiricist reader |
| 2 | Threats hardened, related-work delta sharpened, page budget met |
| 1 | Anonymity sweep on PDF and artifact; Data Availability statement final |
| 0 | Registration by its earlier cutoff, then paper + artifact link on HotCRP |
These offsets are planning heuristics only — anchor every one to the current Important Dates page, never to a previous cycle's calendar.
Show full SKILL.md (243 more words)Show less
Cycle-hopping: the honest calendar reality
FSE runs (currently) a single annual research deadline. As of 2026-07-09, FSE 2026 is in progress in Montreal, so the live next target is FSE 2027 (Shenzhen; deadline 2 Oct 2026). Two planning consequences:
- A Major Revision that cannot be finished in the window may, depending on the year's rules, be resubmittable to the next FSE cycle rather than lost — but this is exactly the kind of policy that changes per edition, so verify it before relying on it.
- Missing the annual deadline costs roughly a year at FSE; a sibling flagship (ICSE/ASE/ISSTA) or an SE journal may have a nearer date — factor that into routing rather than idling.
Failure modes by stage
- Evidence still moving at week 4 forces last-minute analysis nobody has audited — the classic soundness reject in the making.
- Leaving the anonymized artifact to the final week is how a data-availability link or a lab-named tool leaks identity under heavy anonymity.
- Skipping the mock review forfeits the one chance to hear "your baseline is unfair" from a friend instead of a reviewer.
- Treating a Major Revision as a formality and under-budgeting the revision window turns a winnable R&R into a reject.
Coordination notes
- Assign one owner for the Data Availability / artifact and another for the anonymity sweep; shared ownership is how both slip.
- Archive the exact submitted PDF, artifact, and (later) response letter — the revision round must quote them precisely and stay anonymous.
Output format
[Current stage] idea / evidence / writing / registration / submitted / major revision / accepted
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <page budget / anonymity / evidence / threats / artifact / presentation>
[Owner map] <task -> person or role>© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Fse Workflow 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 Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Markdown Article FormatterJimLiu/baoyu-skills | 27k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Word Document Reader and WriterHKUDS/DeepTutor | 41k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Obsidian Markdown
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
Crossposting
wasp-lang/wasp
Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Fse Workflow
What does Fse Workflow do?
A skill your agent uses when planning an ESEC/FSE project timeline from venue fit through paper registration, submission, the journal-style Major Revision round, artifact evaluation, PACMSE…. Fse Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ESEC/FSE project timeline from venue fit through paper registration, submission, the journal-style Major Revision round, artifact evaluation, PACMSE camera-ready, and presentation, with backward-planning offsets for an empirical-SE paper and honest handling of the single-annual-deadline cycle and cycle-hopping.
When should I use Fse Workflow?
Fse Workflow fits situations like: planning an ESEC/FSE project timeline from venue fit through paper registration; the journal-style Major Revision round; artifact evaluation; PACMSE camera-ready.
How do I install Fse Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-workflow -a claude-code`. Or copy the skill folder (FSE-Skills/skills/fse-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/fse-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Fse Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-workflow -a codex`. Or copy the skill folder (FSE-Skills/skills/fse-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/fse-workflow in your project. Codex loads it when a task matches its description.
Can I use Fse Workflow 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-workflow -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-workflow, .gemini/skills/fse-workflow, .github/skills/fse-workflow and .opencode/skills/fse-workflow in your project.
What does Fse Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Fse Workflow is instructions for the agent only.
Does Fse Workflow 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 Workflow 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 Workflow use?
Fse Workflow 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 Workflow use?
About 1.2k tokens (SKILL.md is roughly 5k 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 Workflow?
Skills that share tags, products or a category with Fse Workflow: Markdown Article Formatter (JimLiu/baoyu-skills, 27k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fse Workflow?
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.