Marketing Campaign
affaan-m/ECC
End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.
A skill your agent uses when planning a SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines, running the summer response and July notification…
MITAuto-check passed
Install Sosp Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-workflow .claude/skills/sosp-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 "sosp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-workflow into .claude/skills/sosp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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/SOSP-Skills/skills/sosp-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 sosp-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-workflow .agents/skills/sosp-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 "sosp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-workflow into .agents/skills/sosp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-workflow .cursor/skills/sosp-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 "sosp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-workflow into .cursor/skills/sosp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 SOSP-Skills/skills/sosp-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 sosp-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-workflow .gemini/skills/sosp-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 "sosp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-workflow into .gemini/skills/sosp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-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 sosp-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/SOSP-Skills/skills/sosp-workflow .github/skills/sosp-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 "sosp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-workflow into .github/skills/sosp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-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 sosp-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/SOSP-Skills/skills/sosp-workflow .opencode/skills/sosp-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 "sosp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-workflow into .opencode/skills/sosp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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
sosp-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 520 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 SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines, running the summer response and July notification…
- Works in 3 steps: Shepherd thread — revision plan within… → Artifact thread — sysartifacts… → Logistics thread — ACM rights form,…
- Planning a SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines
- SKILL.md covers The 2026 cycle as the template, Accepted: three threads, two…, Rejected: the retargeting… and Back-scheduling the next…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sosp Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines, running the summer response and July notification, stacking the August camera-ready with artifact evaluation, and retargeting rejections across the SOSP/OSDI/EuroSys circuit.
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 a SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines
- Running the summer response and July notification
- Stacking the August camera-ready with artifact evaluation
- Retargeting rejections across the SOSP/OSDI/EuroSys circuit
Example prompts
- “/sosp-workflow”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Shepherd thread — revision plan within days, agreed scope, 13th/14th page
- Artifact thread — sysartifacts registration opens days after notification;
- Logistics thread — ACM rights form, registration, Czech-entry visas where
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
Sosp Workflow loads about 1.3k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 520 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). 520 words, ~1,257 tokens.
Download SKILL.mdSave it as
.claude/skills/sosp-workflow/SKILL.md (or your agent's skills folder).- name
- sosp-workflow
- description
- Use when planning a SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines, running the summer response and July notification, stacking the August camera-ready with artifact evaluation, and retargeting rejections across the SOSP/OSDI/EuroSys circuit.
SOSP Workflow
Use this to place a project on the SOSP calendar and to decide what to do in the
current phase. SOSP has been annual since 2024 (the SIGOPS announcement is at
sigops.org/2023/sosp-is-going-annual/), which changed campaign planning from a
two-year bet into a rolling circuit. All dates below were checked 2026-07-08.
The 2026 cycle as the template
| Milestone (2026 cycle) | Date | Phase it opens |
|---|---|---|
| Abstract registration | March 27, 2026 (Apr 1 AoE window rendered in EDT on HotCRP) | Freeze title/authors/conflicts |
| Full paper deadline | April 2, 2026, 7:59:59 AM EDT | Review |
| Author response window | Announced with reviews, pre-PC-meeting | sosp-author-response |
| Notification | July 3, 2026 | Camera-ready + AE (accepted) or retarget (rejected) |
| Camera-ready | August 28, 2026 | Shepherded final version |
| Conference | Sep 29 - Oct 2, 2026, Prague, Czech Republic | Talk, posters, workshops |
As of 2026-07-08 the notification has just landed: teams are either five days
into the acceptance track or five days into retargeting. SOSP 2027 dates are
unpublished (待核实 at sigops.org and sosp.org); the annual pattern implies a
spring 2027 deadline, but never back-schedule against an implied date — only
against a posted one.
Accepted: three threads, two months
July 3 to August 28 runs three deadline-bound conversations in parallel, and the standing failure is one person owning all three:
- Shepherd thread — revision plan within days, agreed scope, 13th/14th page
negotiation (see
sosp-camera-ready). Owner A. - Artifact thread — sysartifacts registration opens days after notification;
the evaluation window is interactive (see
sosp-artifact-evaluation). Owner B. - Logistics thread — ACM rights form, registration, Czech-entry visas where needed, talk preparation. Owner C, earliest start wins on visas.
Show full SKILL.md (260 more words)Show less
Rejected: the retargeting circuit
Annual SOSP plus annual OSDI plus the EuroSys/ATC/NSDI ring means a systems paper is rarely more than a few months from its next natural deadline. Retarget on a decision tree, not on grief:
- Reviews attack soundness (evaluation holes, unisolated mechanisms): fix the evidence first; the next deadline is whichever one the new experiments make.
- Reviews attack fit or significance but concede soundness: the paper may be right for a sibling with a different center of gravity — networked-systems framing to NSDI, storage framing to FAST, deployment/practitioner framing to ATC.
- Reviews are strong with one blocker: an OSDI resubmission in the next window with a surgical fix and a cover-your-delta introduction paragraph is the highest expected-value move. Exact sibling deadlines shift every cycle (待核实 against each venue's current CFP before promising a date to co-authors).
Back-scheduling the next submission
T-9 months problem locked; motivating measurement exists; skeleton design review
T-6 months system runs end-to-end on one workload; claim list drafted
T-4 months evaluation matrix frozen (sosp-experiments); baselines built and tuned
T-10 weeks full experimental sweep begins; env capture automated (sosp-reproducibility)
T-6 weeks complete draft; strict 15-minute read by an outside systems reader
T-3 weeks evaluation freeze; figures one-command from logs
T-10 days format compile, leak sweep, conflict list drafted (sosp-submission)
T-6 days abstract registration
T-0 upload; verify the HotCRP-held PDF, not the local oneThe two intervals teams misjudge: baselines (building and fairly tuning someone else's system routinely costs a month) and the draft-to-freeze gap (a SOSP draft that first exists three weeks before the deadline reads like it).
Cadence discipline for a group
- Track the circuit in one shared calendar: SOSP, OSDI, EuroSys, ATC, NSDI, FAST, plus HotOS in odd rhythm for early-stage ideas — each with abstract and paper gates, refreshed from official CFPs each fall and spring.
- One project, one primary venue bet, one named fallback — deciding the fallback before notification removes the week of post-rejection drift.
- Never submit the same work to overlapping review cycles; systems venues share PC members and treat dual submission as an integrity violation.
Output format
[Phase] where this project sits on the cycle today
[Owners] shepherd / artifact / logistics threads assigned?
[If rejected] soundness vs fit diagnosis -> named next venue + posted deadline
[Back-schedule] T-milestones with dates against the next posted deadline
[Calendar risk] the interval currently underestimated© 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 SOSP-Skills/skills/sosp-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sosp 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 |
|---|---|---|---|---|---|---|
| Sosp Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Marketing Campaignaffaan-m/ECC | 275k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Campaign Analyticsalirezarezvani/claude-skills | 28k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Campaign Cleaner AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~764 | Automated safety check: Pass | None | |
| Issue Campaignsamchon/typia | 5.9k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Ad Campaign Analyzersickn33/agentic-awesome-skills | 47k | 1 repos | ~4.3k | Automated safety check: Pass | MIT |
Similar skills
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Campaign Cleaner Automation
ComposioHQ/awesome-claude-skills
Automate Campaign Cleaner tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Issue Campaign
samchon/typia
Defines the default solo repository-wide issue campaign for typia: exhaustive discovery, lead-vetted issue publication, one unified CI-validated implementation pull request per cycle, solo…
Ad Campaign Analyzer
sickn33/agentic-awesome-skills
Analyze cross-channel campaign data, quantify uncertainty, and propose evidence-labeled budget tests without overstating causality.
Credit Cycle Analysis
sickn33/agentic-awesome-skills
Debtor and creditor credit-cycle analysis: weighted collection or payment days, ageing buckets, credit limit utilisation and gap against benchmark.
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 Sosp Workflow
What does Sosp Workflow do?
A skill your agent uses when planning a SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines, running the summer response and July notification…. Sosp Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines, running the summer response and July notification, stacking the August camera-ready with artifact evaluation, and retargeting rejections across the SOSP/OSDI/EuroSys circuit.
When should I use Sosp Workflow?
Sosp Workflow fits situations like: planning a SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines; running the summer response and July notification; stacking the August camera-ready with artifact evaluation; retargeting rejections across the SOSP/OSDI/EuroSys circuit.
How do I install Sosp Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-workflow -a claude-code`. Or copy the skill folder (SOSP-Skills/skills/sosp-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sosp-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Sosp Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-workflow -a codex`. Or copy the skill folder (SOSP-Skills/skills/sosp-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sosp-workflow in your project. Codex loads it when a task matches its description.
Can I use Sosp 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 sosp-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/sosp-workflow, .gemini/skills/sosp-workflow, .github/skills/sosp-workflow and .opencode/skills/sosp-workflow in your project.
What does Sosp Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Sosp Workflow is instructions for the agent only.
Does Sosp 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 Sosp 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 Sosp Workflow use?
Sosp 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 Sosp Workflow use?
About 1.3k 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 Sosp Workflow?
Skills that share tags, products or a category with Sosp Workflow: Marketing Campaign (affaan-m/ECC, 275k stars), Campaign Analytics (alirezarezvani/claude-skills, 28k stars), Campaign Cleaner Automation (ComposioHQ/awesome-claude-skills, 77k stars) and Issue Campaign (samchon/typia, 5.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sosp Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.