ã审计ç 究ãæ稿ï¼auditing-researchï¼
openbooklet.com/s/-auditing-researchopenbooklet.com/s/-auditing-research@1.0.0GET /api/v1/skills/-auditing-researché å¥ä»£ç ï¼`resources/code/stata/03_did_modern.do`ï¼DIDï¼ã`04_iv.do`ï¼IVï¼ã`05_rdd.do`ï¼RDDï¼ã`06_dml.do`ï¼DMLï¼ã
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
Use when drafting AAAI rebuttals under the single short author-response limit, no-URL rule, no-new-results guidance, AI-review handling, and two-phase review process.
Use when targeting AAAI Conference on Human Computation and Crowdsourcing (HCOMP) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for human computation.
Use when strengthening an AAAI paper's reproducibility checklist, experimental traceability, seed reporting, compute disclosure, dataset access, code/data readiness, and evidence map.
Use when explaining or planning around AAAI's two-phase review process, Phase 1 rejection risk, Phase 2 additional reviews, AI-assisted review pilot, author feedback, SPC/AC discussion, and final decisions.
Use when deciding whether a project is a strong AAAI submission, should be reframed for AAAI, or should be routed to IJCAI, NeurIPS, ICML, ICLR, AISTATS, UAI, ACL, CVPR, KDD, CHI, or another venue.
Use when planning an AAAI project timeline from topic selection through abstract, OpenReview submission, two-phase review, rebuttal, decision, camera-ready, registration, presentation, and public artifact release.
Use when revising an AAAI manuscript for broad AI audience fit, concise contribution claims, two-column readability, reproducibility-checklist alignment, and policy-aware AI-system claims.
Auto-indexed from brycewang-stanford/Awesome-Journal-Skills
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.