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 an ACM SoCC project timeline from venue fit through the two-round abstract+paper deadlines, the rebuttal, notification, camera-ready, and presentation, with…
MITAuto-check passed
Install Socc Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-workflow .claude/skills/socc-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 "socc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-workflow into .claude/skills/socc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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/SoCC-Skills/skills/socc-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 socc-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-workflow .agents/skills/socc-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 "socc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-workflow into .agents/skills/socc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-workflow .cursor/skills/socc-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 "socc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-workflow into .cursor/skills/socc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 SoCC-Skills/skills/socc-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 socc-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-workflow .gemini/skills/socc-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 "socc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-workflow into .gemini/skills/socc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-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 socc-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/SoCC-Skills/skills/socc-workflow .github/skills/socc-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 "socc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-workflow into .github/skills/socc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-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 socc-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/SoCC-Skills/skills/socc-workflow .opencode/skills/socc-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 "socc-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-workflow into .opencode/skills/socc-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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
socc-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 652 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 ACM SoCC project timeline from venue fit through the two-round abstract+paper deadlines, the rebuttal, notification, camera-ready, and presentation, with…
- Planning an ACM SoCC project timeline from venue fit through the two-round abstract+paper deadlines
- SKILL.md covers Milestones, Backward plan from a round's…, Two-rounds-per-year: the… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Socc Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM SoCC project timeline from venue fit through the two-round abstract+paper deadlines, the rebuttal, notification, camera-ready, and presentation, with backward-planning offsets for a cloud-systems measurement paper and honest handling of the two-rounds-per-year cadence and the no-cross-round-resubmission rule.
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.
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 ACM SoCC project timeline from venue fit through the two-round abstract+paper deadlines
Example prompts
- “/socc-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
Socc Workflow loads about 1.3k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 652 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). 652 words, ~1,333 tokens.
Download SKILL.mdSave it as
.claude/skills/socc-workflow/SKILL.md (or your agent's skills folder).- name
- socc-workflow
- description
- Use when planning an ACM SoCC project timeline from venue fit through the two-round abstract+paper deadlines, the rebuttal, notification, camera-ready, and presentation, with backward-planning offsets for a cloud-systems measurement paper and honest handling of the two-rounds-per-year cadence and the no-cross-round-resubmission rule.
SoCC Workflow
Use this as the project-management skill for a SoCC submission. Replace every date with the current official timetable and work backwards from the round's abstract-registration cutoff — which precedes the paper deadline by about a week. SoCC — the ACM Symposium on Cloud Computing, jointly sponsored by SIGMOD and SIGOPS — runs two review rounds per year, so the first planning decision is which round you are genuinely ready for.
SoCC is a conference with no standing editor-in-chief; its rotating leadership is the per-edition General Chair(s) and Program Committee Co-Chairs appointed under SIGMOD and SIGOPS (SoCC 2026 PC Co-Chairs reported as Eric Lo and Ivan Beschastnikh, verified 2026-07-09 via committee-page rendering; confirm on the live page). The cost model is conference registration; at least one author presents.
Milestones
- Venue fit: confirm SoCC over OSDI/NSDI/EuroSys/ATC and over SIGMOD/VLDB
(
socc-topic-selection), and confirm the contribution spans the systems-and-data intersection. - Evidence lock: freeze the system/mechanism, the testbed or trace, the workloads, the baselines, and the measurement pipeline.
- Round choice: pick Round 1 or Round 2 knowing a Round-1 reject cannot be resubmitted to Round 2 the same year.
- Abstract registration: submit real title, abstract, authors, subject tags, and conflicts by the round's abstract cutoff.
- Submission: upload the anonymized acmart PDF and (where possible) the artifact link by the round's paper deadline (AoE).
- Rebuttal: during the round's author-response window, answer reviewers on the axes they raised.
- Notification: accept / reject for that round; archive reviews, rebuttal, and every version.
- Acceptance: prepare the camera-ready, pursue ACM artifact badges if the edition offers evaluation, register, and present in Singapore (SoCC 2026).
Backward plan from a round's paper deadline
| Weeks out (heuristic) | Cloud-systems milestone |
|---|---|
| 10+ | System/mechanism feature-frozen; testbed or trace and baselines chosen |
| 8 | Experiments running; measurement harness logs throughput, latency, tail, and cost |
| 6 | Analysis done; cost-latency and tail results computed; baselines tuned with a documented budget |
| 4 | Full draft in acmart sigconf; artifact (trace-replay/testbed scripts) assembled and anonymized |
| 3 | Internal mock review by a systems reader and a data/measurement reader |
| 2 | Tail and cost results hardened; related-work delta sharpened; 12-page budget met |
| 1 | Dual-anonymous sweep on PDF and artifact (traces, cluster names, system names) |
| 0 | Abstract registered by its earlier cutoff, then paper + artifact link on HotCRP |
These offsets are planning heuristics only — anchor every one to the current Important Dates / HotCRP deadlines page, never to a previous cycle's calendar.
Show full SKILL.md (260 more words)Show less
Two-rounds-per-year: the honest calendar reality
SoCC's twin-round model is a genuine advantage and a trap:
- Advantage: there are two shots per calendar year at the same venue (a winter/February round and a summer/July round for SoCC 2026), so a paper that misses one round is only months from the next.
- Trap: a paper rejected in Round 1 may not be resubmitted to Round 2 the same year, so a rushed Round-1 submission does not buy a discounted retry — it costs you the year at SoCC. Submit to the round you can make strong, not merely the nearer one.
- As of 2026-07-09, the live target is SoCC 2026 Round 2 (paper 14 Jul 2026); Round 1 (13 Feb
- has passed.
Failure modes by stage
- Evidence still moving at week 4 forces last-minute measurement nobody has audited — the classic soundness reject for a systems paper.
- Simulation-only at submission invites the "does it hold on a real testbed?" reject from both sponsoring communities.
- Reporting only the mean — omitting tail latency and cost — reads as not understanding what a cloud paper is judged on.
- Leaving the anonymized trace/artifact to the final week is how a cluster name or provider hint leaks identity under dual-anonymous review.
- Treating Round 1 as a free draft and getting rejected forfeits the whole SoCC year.
Coordination notes
- Assign one owner for the measurement harness and reproducibility package and another for the dual-anonymous sweep; shared ownership is how both slip.
- Archive the exact submitted PDF and artifact — the rebuttal must quote the paper precisely and stay anonymous.
Output format
[Current stage] idea / evidence / round-choice / submitted / rebuttal / accepted
[Target round] round 1 / round 2, with the next official deadline and source
[Critical path] <three tasks that determine readiness>
[Risk register] <page budget / anonymity / simulation-vs-testbed / tail+cost evidence / artifact>
[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 SoCC-Skills/skills/socc-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Socc 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 |
|---|---|---|---|---|---|---|
| Socc Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | 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 | |
| VenueLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.4k | 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 |
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.
Venue
LeoYeAI/openclaw-master-skills
Music venue where AI agents stream concerts as mathematics. An agent skill from LeoYeAI/openclaw-master-skills.
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…
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 Socc Workflow
What does Socc Workflow do?
A skill your agent uses when planning an ACM SoCC project timeline from venue fit through the two-round abstract+paper deadlines, the rebuttal, notification, camera-ready, and presentation, with…. Socc Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM SoCC project timeline from venue fit through the two-round abstract+paper deadlines, the rebuttal, notification, camera-ready, and presentation, with backward-planning offsets for a cloud-systems measurement paper and honest handling of the two-rounds-per-year cadence and the no-cross-round-resubmission rule.
When should I use Socc Workflow?
Socc Workflow fits situations like: planning an ACM SoCC project timeline from venue fit through the two-round abstract+paper deadlines.
How do I install Socc Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-workflow -a claude-code`. Or copy the skill folder (SoCC-Skills/skills/socc-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/socc-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Socc Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-workflow -a codex`. Or copy the skill folder (SoCC-Skills/skills/socc-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/socc-workflow in your project. Codex loads it when a task matches its description.
Can I use Socc 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 socc-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/socc-workflow, .gemini/skills/socc-workflow, .github/skills/socc-workflow and .opencode/skills/socc-workflow in your project.
What does Socc Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Socc Workflow is instructions for the agent only.
Does Socc 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 Socc 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 Socc Workflow use?
Socc 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 Socc Workflow use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Socc Workflow?
Skills that share tags, products or a category with Socc Workflow: Project Timeline Report (thedotmack/claude-mem, 99k stars), GSAP Timeline (greensock/gsap-skills, 16k stars), Venue (LeoYeAI/openclaw-master-skills, 2.2k stars) and Building Incident Timeline With Timesketch (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 Socc 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.