Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
A skill your agent uses when planning a CSCW submission timeline end to end — the PACMHCI journal model, the retired fixed cycles versus the rolling 2027+ pathway, Revise-and-Resubmit rounds that…
MITAuto-check passed
Install Cscw Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-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/CSCW-Skills/skills/cscw-workflow .claude/skills/cscw-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 "cscw-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-workflow into .claude/skills/cscw-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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/CSCW-Skills/skills/cscw-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 cscw-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-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/CSCW-Skills/skills/cscw-workflow .agents/skills/cscw-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 "cscw-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-workflow into .agents/skills/cscw-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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 cscw-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-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/CSCW-Skills/skills/cscw-workflow .cursor/skills/cscw-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 "cscw-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-workflow into .cursor/skills/cscw-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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 CSCW-Skills/skills/cscw-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 cscw-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-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/CSCW-Skills/skills/cscw-workflow .gemini/skills/cscw-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 "cscw-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-workflow into .gemini/skills/cscw-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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 cscw-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 cscw-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/CSCW-Skills/skills/cscw-workflow .github/skills/cscw-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 "cscw-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-workflow into .github/skills/cscw-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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 cscw-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 cscw-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/CSCW-Skills/skills/cscw-workflow .opencode/skills/cscw-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 "cscw-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-workflow into .opencode/skills/cscw-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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
cscw-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 618 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a CSCW submission timeline end to end — the PACMHCI journal model, the retired fixed cycles versus the rolling 2027+ pathway, Revise-and-Resubmit rounds that…
- Planning a CSCW submission timeline end to end — the PACMHCI journal model
- SKILL.md covers The two regimes (as of…, Cycle-hopping, translated for…, Campaign plan skeleton and Risks specific to this venue's…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The retired fixed cycles versus the rolling 2027+ pathway
What it does
Cscw Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a CSCW submission timeline end to end — the PACMHCI journal model, the retired fixed cycles versus the rolling 2027+ pathway, Revise-and-Resubmit rounds that span months, and back-planning so an acceptance lands before the conference-year presentation cutoff.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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 a CSCW submission timeline end to end — the PACMHCI journal model
- The retired fixed cycles versus the rolling 2027+ pathway
- Revise-and-Resubmit rounds that span months
- Back-planning so an acceptance lands before the conference-year presentation cutoff
Example prompts
- “/cscw-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
Cscw Workflow loads about 1.4k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 618 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). 618 words, ~1,385 tokens.
Download SKILL.mdSave it as
.claude/skills/cscw-workflow/SKILL.md (or your agent's skills folder).- name
- cscw-workflow
- description
- Use when planning a CSCW submission timeline end to end — the PACMHCI journal model, the retired fixed cycles versus the rolling 2027+ pathway, Revise-and-Resubmit rounds that span months, and back-planning so an acceptance lands before the conference-year presentation cutoff.
CSCW Workflow
CSCW is not a deadline sprint. Since 2017 its papers have been journal articles in PACMHCI, and since early 2026 the venue has been rolling out a fully journal-style pipeline: submit whenever the paper is ready, expect a decision in roughly 3-4 months, revise on the editor's clock, and present at whichever conference your acceptance lands in front of. Planning a CSCW project therefore means planning a revision campaign, not a submission night.
The two regimes (as of 2026-07-08)
| Aspect | Fixed cycles (through the May 2025 cycle) | Rolling (CSCW 2027 and beyond) |
|---|---|---|
| Deadline | Hard cutoff (last: May 14, 2025, 12:00 EDT) | None — submit when ready |
| Platform | PCS | Manuscript Central (mc.manuscriptcentral.com/pacmhci) |
| Who handles the paper | Program committee (ACs) per cycle | Editorial board: EiC/AE by methodological track |
| First decision | Batched (first-round decisions ~6 months in) | Rolling, ~3-4 months from submission |
| Revision windows | Fixed dates (e.g., R&R due January 13, 2026) | Set per paper by the handling editor |
| Conference tie | Cycle mapped to a specific conference year | Accepted papers invited to the next CSCW, pending space |
The May 2025 cycle — the last of the old kind — is worth studying as a calibration anchor even though it will never recur: submissions May 14, 2025 → internal "Revise for External Review" resubmissions September 16, 2025 → first external decisions November 2025 (66.2% of papers got Revise and Resubmit; only a third got any final decision) → revised papers due January 13, 2026 → final decisions late March 2026 → presentation at CSCW 2026 (Salt Lake City, October 10-14, 2026). That is a 17-month arc from submission to podium, and two-thirds of surviving papers went through the full R&R loop.
Cycle-hopping, translated for the rolling era
Under fixed cycles, authors managed risk by "hopping": if an R&R could not be turned around by the resubmission date, the revision rolled into a later cycle and a later conference. Rolling keeps the underlying skill and removes the calendar: the hop is now a negotiation with time, not with a deadline table. Practical consequences:
- Submission date is a strategic variable. Count backward from the conference you want to attend: with ~3-4 months to first decision and a realistic multi-week revision round (PACMHCI revision periods are measured in weeks-to-months, not days), a paper submitted less than ~8-10 months before a conference is betting on a clean first decision. The exact cutoff by which a rolling acceptance is assigned to CSCW 2027 versus 2028 was 待核实 at check time — confirm it on cscw.acm.org/rolling.html before promising a travel year to anyone.
- Revision capacity is the bottleneck. An R&R that demands new data collection (a second interview wave, another deployment period) costs a season. Budget the team's field access before submitting, not when the decision arrives.
- Nothing forces you to submit early — or lets you cram. The rolling model rewards submitting a genuinely finished paper over hitting an arbitrary date with a rushed one; there is no deadline-night adrenaline to launder weak sections.
Show full SKILL.md (131 more words)Show less
Campaign plan skeleton
[T0] Internal full-draft review (simulate first-round: one skeptic per
method tradition in the paper)
[T0+2wk] Ethics/consent artifacts final; anonymization sweep #1
[T0+4wk] Submit via the current platform (verify regime first)
[T0+4mo] Expected decision window opens — pre-book revision capacity:
who re-codes, who re-runs analyses, who drafts the response letter
[R&R] Treat as a project phase with an owner, not a chore
(see cscw-author-response)
[Accept] Camera-ready + PACMHCI production (see cscw-camera-ready);
confirm which conference year the paper presents at
[Confab] Registration, travel, talk prep for the assigned CSCWRisks specific to this venue's shape
- Stale-regime planning. Advice, blog posts, and lab lore calibrated to PCS cycles is now wrong. Verify the live pathway before every new submission.
- Indefinite-polish drift. With no deadline, drafts can orbit forever. Set an internal submission date and treat it as real.
- Same-reviewers memory. R&R rounds return to the same reviewers; a revision that quietly ignores a request will be caught by the person who made it.
- Presentation-slot ambiguity. "Invited to present at the next conference, pending space" is a softer guarantee than a proceedings deadline; keep travel plans provisional until the assignment is explicit.
Status-report format
[Regime] rolling / residual fixed-cycle (verified <date> at cscw.acm.org)
[Stage] drafting / submitted / R&R round n / minor changes / production
[Clock] time since submission or since revision request
[Bottleneck] <the one resource gating the next stage>
[Conference target] CSCW <year> — assignment confirmed? yes / no / 待核实Dates and statistics above are the 2026-07-08 snapshot of a venue mid-transition; recheck cscw.acm.org and the rolling CFP before treating any of them as current.
© 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 CSCW-Skills/skills/cscw-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cscw 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 |
|---|---|---|---|---|---|---|
| Cscw Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Project Timeline Reportthedotmack/claude-mem | 99k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GSAP Timelinegreensock/gsap-skills | 16k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Building Incident Timeline With Timesketchmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.4k | Automated safety check: Notes | Apache-2.0 | |
| Generating Forensic Timelines With Hayabusamukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Performing Timeline Reconstruction With Plasomukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3k | Automated safety check: Notes | Apache-2.0 |
Similar skills
GSAP Timeline
greensock/gsap-skills
Teaches the GSAP timeline API for sequencing animations: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control.
Building Incident Timeline With Timesketch
mukul975/Anthropic-Cybersecurity-Skills
Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation…
Generating Forensic Timelines With Hayabusa
mukul975/Anthropic-Cybersecurity-Skills
Run Hayabusa against collected Windows EVTX files to apply Sigma detection rules and produce a prioritized, chronological CSV/JSON timeline with severity levels, MITRE ATT&CK mappings, and…
Performing Timeline Reconstruction With Plaso
mukul975/Anthropic-Cybersecurity-Skills
Builds comprehensive forensic super-timelines using Plaso (log2timeline and psort) to correlate events across file system metadata, event logs, browser history, and registry artifacts into a unified…
Building Super Timelines With Plaso
mukul975/Anthropic-Cybersecurity-Skills
Generate forensic super-timelines with Plaso's log2timeline.py, pinfo.py, psort.py, and psteal.py CLI tools (fusing file-system MACB, registry, EVTX, browser history, prefetch, LNK, and more), then…
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…
Questions about Cscw Workflow
What does Cscw Workflow do?
A skill your agent uses when planning a CSCW submission timeline end to end — the PACMHCI journal model, the retired fixed cycles versus the rolling 2027+ pathway, Revise-and-Resubmit rounds that…. Cscw Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a CSCW submission timeline end to end — the PACMHCI journal model, the retired fixed cycles versus the rolling 2027+ pathway, Revise-and-Resubmit rounds that span months, and back-planning so an acceptance lands before the conference-year presentation cutoff.
When should I use Cscw Workflow?
Cscw Workflow fits situations like: planning a CSCW submission timeline end to end — the PACMHCI journal model; the retired fixed cycles versus the rolling 2027+ pathway; revise-and-Resubmit rounds that span months; back-planning so an acceptance lands before the conference-year presentation cutoff.
How do I install Cscw Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-workflow -a claude-code`. Or copy the skill folder (CSCW-Skills/skills/cscw-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cscw-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Cscw Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-workflow -a codex`. Or copy the skill folder (CSCW-Skills/skills/cscw-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cscw-workflow in your project. Codex loads it when a task matches its description.
Can I use Cscw 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 cscw-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/cscw-workflow, .gemini/skills/cscw-workflow, .github/skills/cscw-workflow and .opencode/skills/cscw-workflow in your project.
What does Cscw Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Cscw Workflow is instructions for the agent only.
Does Cscw 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 Cscw 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 Cscw Workflow use?
Cscw 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 Cscw Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.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 Cscw Workflow?
Skills that share tags, products or a category with Cscw Workflow: Project Timeline Report (thedotmack/claude-mem, 99k stars), GSAP Timeline (greensock/gsap-skills, 16k stars), Building Incident Timeline With Timesketch (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Generating Forensic Timelines With Hayabusa (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cscw Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.