ase-supplementary
Use when deciding what belongs in the 10-page ASE (IEEE/ACM Automated Software Engineering) paper body versus the artifact and supplementary material, splitting content by decision-criticality so nothing that decides acceptance lives outside the reviewed pages under the 10+2 budget.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-supplementary --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ASE Supplementary Split content by **decision-criticality**. ASE gives you **10 pages** of body (plus 2 for references), and reviewers judge the paper on those pages. The artifact and any supplementary material *support* reproduction and reuse — they do not carry the argument. The failure mode is exiling a decision-critical result to the artifact and assuming reviewers will dig for it; they judge what is in the body. ## The decision-criticality rule - **In the body (must be within 10 pages):** anything a reviewer needs to accept the paper — the automated task, the technique, the headline results on real subjects, the closest baseline comparison, the key ablation, and the central threats argument. - **In the artifact / supplement:** everything needed to *reproduce or reuse* — full configurations, complete result tables, extra subjects, proofs, additional plots, raw logs, and cached model outputs. If a result decides acceptance, it lives in the body even if space is tight; cut elsewhere. ## What each container is for | Content | Where | Why | |---|---|---| | Task, technique, headline evaluation, closest-baseline comparison, key ablation | Body (≤10 pp) | Decision-critical; reviewer
- The decision-criticality rule
- What each container is for
- The reviewer-behavior reality
- Anonymity across containers
- Space-recovery moves (before cutting content)
- Output format
What does the ase-supplementary skill do?
Use when deciding what belongs in the 10-page ASE (IEEE/ACM Automated Software Engineering) paper body versus the artifact and supplementary material, splitting content by decision-criticality so nothing that decides acceptance lives outside the reviewed pages under the 10+2 budget.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-supplementary --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.