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 an ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21…
MITAuto-check passed
Install Asplos Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-workflow .claude/skills/asplos-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 "asplos-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-workflow into .claude/skills/asplos-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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/ASPLOS-Skills/skills/asplos-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 asplos-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-workflow .agents/skills/asplos-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 "asplos-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-workflow into .agents/skills/asplos-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 asplos-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-workflow .cursor/skills/asplos-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 "asplos-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-workflow into .cursor/skills/asplos-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 ASPLOS-Skills/skills/asplos-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 asplos-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-workflow .gemini/skills/asplos-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 "asplos-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-workflow into .gemini/skills/asplos-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 asplos-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 asplos-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/ASPLOS-Skills/skills/asplos-workflow .github/skills/asplos-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 "asplos-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-workflow into .github/skills/asplos-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 asplos-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 asplos-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/ASPLOS-Skills/skills/asplos-workflow .opencode/skills/asplos-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 "asplos-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-workflow into .opencode/skills/asplos-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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
asplos-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 737 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 ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21…
- Works in 4 steps: Accept → switch to asplos-camera-ready… → Major Revision → treat as a funded… → Reject at rapid review → the diagnosis… → …
- Planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building
- SKILL.md covers The 2027 cycle as a calendar, Working backward from…, Role assignments that prevent… and Branch planning at…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Asplos Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21 notification, Major Revision resubmission six weeks later, artifact evaluation, and the April 2027 conference in Crete, with owners per risk.
Its SKILL.md is about 1.7k 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 ASPLOS campaign across the two-deadline cycle — sequencing evidence building
- The September 9
- 2026 submission gate
- Author-response windows
Example prompts
- “/asplos-workflow”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Accept → switch to asplos-camera-ready immediately; camera-ready lands
- Major Revision → treat as a funded contract, not a consolation: the revision
- Reject at rapid review → the diagnosis is almost always positioning: the
- Reject after full review → mine the reviews for the evidence matrix, then
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
Asplos Workflow loads about 1.7k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 737 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). 737 words, ~1,729 tokens.
Download SKILL.mdSave it as
.claude/skills/asplos-workflow/SKILL.md (or your agent's skills folder).- name
- asplos-workflow
- description
- Use when planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21 notification, Major Revision resubmission six weeks later, artifact evaluation, and the April 2027 conference in Crete, with owners per risk.
ASPLOS Workflow
An ASPLOS campaign is a pipeline with two entry gates per edition and a revision side-channel, not a single deadline sprint. All dates below are the verified 2027 cycle (CFP and conference site, checked 2026-07-08); reopen the official pages before committing a team to any of them.
The 2027 cycle as a calendar
| Gate | April cycle | September cycle |
|---|---|---|
| Full-paper deadline (11:59 PM AoE) | April 15, 2026 — passed | September 9, 2026 — the live gate |
| Author response | July 6-9, 2026 — open this week (as of 2026-07-08) | December 1-4, 2026 |
| Notification | July 27, 2026 | December 21, 2026 |
| Major Revision due | camera-ready deadline, 6 weeks after notification | camera-ready deadline, 6 weeks after notification |
| Conference | April 11-15, 2027, Heraklion, Crete, Greece | same |
There is no separate abstract deadline in 2027, and no mid-year third round — the edition moved from three deadlines to two. Missing September means waiting for the next edition's first gate.
Working backward from September 9, 2026
A credible countdown for a systems paper with hardware-dependent evidence:
T-10 weeks (by ~Jul 1) Freeze the claim list; run asplos-topic-selection;
choose evidence instruments (silicon / FPGA / simulator).
T-8 weeks Evaluation infrastructure done: baselines building,
workloads chosen, simulator configs pinned.
T-6 weeks First full results sweep; kill or descope claims the
data will not carry. Start the two-page draft NOW —
it is the part rapid review actually reads.
T-4 weeks Full draft; internal red-team against the rapid-review
question set; ablations running.
T-2 weeks Freeze experiments. Citation-format pass (full names,
no "et al.", DOIs). Anonymity sweep.
T-1 week HotCRP entry created; PDF uploaded; co-author sign-off.
T-0 Sep 9, 11:59 PM AoE HotCRP status shows *complete*, not draft.Role assignments that prevent known failures
- Two-page owner — one author owns pages 1-2 as a standalone artifact and
rehearses them against
asplos-writing-style; rapid review reads nothing else. - Evidence-integrity owner — keeps the experiment matrix (claims × platforms × baselines) current so the rebuttal window never requires new runs under pressure.
- Compliance owner — template, 11-page geometry, citation full-name rule, GenAI disclosure, HotCRP fields; format violations risk rejection without review.
- Response owner — reserves the response window dates (Dec 1-4 for the September cycle) on every author's calendar at submission time, not after reviews arrive.
Branch planning at notification (December 21, 2026)
- Accept → switch to
asplos-camera-readyimmediately; camera-ready lands ~6 weeks out, and artifact evaluation (asplos-artifact-evaluation) runs in parallel with its own appendix and deadlines (2027 AE calendar 待核实). - Major Revision → treat as a funded contract, not a consolation: the revision is due at the camera-ready deadline and counts as a submission; scope revision work to exactly what the decision letter requires, tracked in a change log that will become the resubmission note.
- Reject at rapid review → the diagnosis is almost always positioning: the first two pages did not establish the intersection or the evidence. Fix framing before considering a new venue.
- Reject after full review → mine the reviews for the evidence matrix, then
re-run
asplos-topic-selection; some full-review rejects are strong ISCA, SOSP, or PLDI papers mis-aimed at the intersection.
Cross-edition cautions
- The two-deadline structure is itself new for 2027; do not assume it for 2028.
- ASPLOS logistics genuinely change year to year — the 2025 edition (30th, Rotterdam) ran jointly with EuroSys; 2026 (31st) was standalone in Pittsburgh; 2027 is in Crete. Travel, visa, and registration planning must restart per edition (fees and attendance rules for 2027: 待核实).
- Program leadership rotates every edition; there is no standing editorial memory to appeal to. A policy answer from a previous year's chairs is expired.
Show full SKILL.md (261 more words)Show less
Hardware lead times are schedule items
Systems evidence has procurement physics that a paper calendar must absorb:
- Cluster or testbed reservations for the T-8 to T-2 sweep window book out weeks ahead; reserve at claim-freeze time, not first-results time.
- FPGA synthesis iterations and simulator calibration runs are days-long serial steps — one redesign late in the countdown costs a week, not an evening.
- Access to pre-production parts (new memory devices, engineering samples) often comes with NDA review of the paper text; start that review before T-4 or it becomes the critical path.
Between notification and Crete
An accepted September-cycle paper has a compressed post-decision runway: camera-ready and any Major Revision work land ~6 weeks after December 21 — squarely across the holiday break, which the six-week plan must acknowledge — followed by artifact evaluation, then travel logistics for an April conference in Greece (visa timelines for some team members exceed the gap; start at notification). Presentation format, registration requirements, and speaker obligations for 2027 were 待核实 at pack-check time: read the acceptance email before assigning the talk.
Pipelining across gates
Teams running multiple projects should treat the two gates as a pipeline: a paper that misses the September evidence bar can target the next edition's first gate with its evaluation matrix already built, while the response and revision windows of a September submission land in December-February — plan author bandwidth so a Major Revision does not collide with the next project's deadline sprint. One person cannot own the revision of paper A and pages 1-2 of paper B in the same six weeks.
Output format
[Cycle chosen] September 2026 / next edition (reason)
[Countdown health] on-track items · at-risk items with dates
[Owners] two-page / evidence / compliance / response — names attached?
[Branch plans] accept · major-revision · rapid-reject · full-reject, one line each
[Calendar holds] Dec 1-4 response window + 6-week revision block reserved? Y/N
[Facts to re-verify] <official pages to reopen before relying on this plan>© 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 ASPLOS-Skills/skills/asplos-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Asplos 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 |
|---|---|---|---|---|---|---|
| Asplos Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Marketing Campaignaffaan-m/ECC | 276k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Deadlinesanthropics/claude-for-legal | 9.6k | 3 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| 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 | |
| Deadline Funnel AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~760 | Automated safety check: Pass | None |
Similar skills
- Official
Deadlines
anthropics/claude-for-legal
Track case deadlines — add, cross-case rollup report, update, complete, close.
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.
Deadline Funnel Automation
ComposioHQ/awesome-claude-skills
Automate Deadline Funnel 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…
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 Asplos Workflow
What does Asplos Workflow do?
A skill your agent uses when planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21…. Asplos Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21 notification, Major Revision resubmission six weeks later, artifact evaluation, and the April 2027 conference in Crete, with owners per risk.
When should I use Asplos Workflow?
Asplos Workflow fits situations like: planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building; the September 9; 2026 submission gate; author-response windows.
How do I install Asplos Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-workflow -a claude-code`. Or copy the skill folder (ASPLOS-Skills/skills/asplos-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/asplos-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Asplos Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-workflow -a codex`. Or copy the skill folder (ASPLOS-Skills/skills/asplos-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/asplos-workflow in your project. Codex loads it when a task matches its description.
Can I use Asplos 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 asplos-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/asplos-workflow, .gemini/skills/asplos-workflow, .github/skills/asplos-workflow and .opencode/skills/asplos-workflow in your project.
What does Asplos Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Asplos Workflow is instructions for the agent only.
Does Asplos 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 Asplos 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 Asplos Workflow use?
Asplos 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 Asplos Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Asplos Workflow?
Skills that share tags, products or a category with Asplos Workflow: Marketing Campaign (affaan-m/ECC, 276k stars), Deadlines (anthropics/claude-for-legal, 9.6k stars), Campaign Analytics (alirezarezvani/claude-skills, 28k stars) and Campaign Cleaner Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Asplos 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.