Install
$ agentstack add skill-brycewang-stanford-awesome-journal-skills-aaai-supplementary ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
AAAI Supplementary
Use this when deciding what belongs in the main paper, technical appendix, multimedia appendix, or code/data ZIP. AAAI supplementary material is due with the paper and should be treated as immutable once submitted unless current instructions say otherwise.
Supplement structure
- Keep the central contribution, method, core results, and checklist-relevant evidence in the main
paper.
- Put proofs, extra ablations, extended qualitative examples, implementation details, and additional
error analysis in the technical appendix.
- Put videos, audio, interactive demos, or visualizations in a multimedia appendix only when they are
technically necessary.
- Put scripts, datasets, logs, model configs, and checkpoints in code/data ZIPs.
- Add a compact appendix map so reviewers can find support for each disputed claim.
Anonymity and immutability
- Remove identity from file names, metadata, paths, Git history, author comments, and license
headers.
- Do not use web pointers for extra material if current AAAI rules disallow them.
- Submit final, uncorrupted files. Do not rely on rebuttal to repair missing content.
- Keep the supplement consistent with the reproducibility checklist.
Where each item belongs
A broad-AI reviewer will skim the appendix, not study it, so placement decides whether evidence is actually seen. Anything a claim depends on belongs in the main paper; the appendix only deepens it.
| Material | Main paper | Technical appendix | Multimedia | Code/data ZIP | | --- | --- | --- | --- | --- | | Core result | yes | no | no | no | | Full proof | sketch | full | no | no | | Extra ablation | summary | detail | no | no | | Demo of behavior | no | no | yes | no | | Scripts and configs | no | no | no | yes |
Reviewer-pushback patterns
- "The key result is only in the appendix." Fix: promote it to the main paper; AAAI reviewers are not
obligated to find a load-bearing claim buried in supplement.
- "Supplement contradicts the checklist." Fix: reconcile every appendix number with the checklist
before submission, since neither can be edited later.
- "Multimedia is huge but adds nothing." Fix: drop spectacle clips; include video only when it is the
evidence, not decoration.
Worked vignette
A vision paper hides its ablation table in the ZIP and leaves only a teaser figure in the paper. The navigation map exposes the gap: a disputed claim points to a file a skimming reviewer will miss. The fix moves the ablation summary into the main paper, keeps full per-class numbers in the technical appendix, and scrubs the ZIP's metadata so nothing deanonymizes the immutable supplement.
Output format
[Supplement plan] technical appendix / multimedia appendix / code-data ZIP / none
[Main-paper dependencies]
[Navigation map] supplement file/section>
[Anonymity risks]
[Submission risk]
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: brycewang-stanford
- Source: brycewang-stanford/Awesome-Journal-Skills
- License: MIT
- Homepage: https://www.copaper.ai
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.