Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use to build NEJM clinical display items correctly — Table 1 baseline characteristics by group (with standardized differences, not P values), Kaplan-Meier curves with numbers-at-risk, forest plots for subgroups and meta-analyses, and the CONSORT participant flow diagram.
Use when preparing accepted NeurIPS papers for camera-ready upload, de-anonymization, final checklist, code/data release, OpenReview metadata, and post-acceptance obligations.
Use when auditing a NeurIPS main-track submission for current-cycle CFP, OpenReview, formatting, anonymity, track, contribution-type, checklist, code/data, dual-submission, and LLM/agent policy compliance.
Use when deciding what NeurIPS material belongs in the main PDF body, the references, text appendices, the mandatory Paper Checklist, the separate code/data ZIP, or an external public artifact, and how to keep every supplemental component anonymous under double-blind review.
Use for the final preflight before submitting a New Media & Society (NM&S) manuscript via Sage Track — word target, abstract, keywords, masking, SAGE Harvard referencing, ethics statement, and ORCID. Runs the checklist; it does not draft content.
Use when building exhibits for a New Media & Society (NM&S) manuscript — quote/excerpt tables, coding-scheme tables, network and computational figures, and screenshots of platform interfaces. Makes exhibits clear and self-contained; it does not run the analysis.
Use when converting an NSDI acceptance into a published, presented paper — de-anonymizing within the same 12-page cap, meeting the final-papers deadline that also gates Community Award eligibility, designating the presenter, and landing in USENIX's open-access proceedings for the May symposium.
Use when splitting NSDI material across the 12-page body, the appendix pages the CFP allows beyond references, HotCRP auxiliary-material uploads for critical online content, and the one-shot-revision packet — deciding what reviewers must see in-body versus what merely supports it.
Use when packaging an artifact for an accepted OOPSLA paper under the SPLASH artifact-evaluation track — surviving the kick-the-tires phase, earning the Functional and Reusable badges, depositing a Zenodo snapshot with a DOI for Available, and aligning artifact claims with the paper's Data-Availability Statement.
Use when converting an accepted OOPSLA paper into its PACMPL journal article — final acmsmall formatting within the 25-page revision cap, de-anonymization and Data-Availability Statement updates, ACM open-access and rights steps, hitting the OOPSLA1 (April) or OOPSLA2 (October) issue, and planning the SPLASH talk.