跳到正文
cccskills
免费在 GitHub 公开

amann-editor-strategy

Use when working with the Associate Editor and Editor of an Academy of Management Annals (Annals) review — scope alignment after a proposal is invited, what review-article referees evaluate, and revision expectations. Plans the interaction; it does not run the portal preflight (amann-submission) or draft the response letter (amann-revision).

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md5.6 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Editor & Referee Strategy for a Review (amann-editor-strategy)

When to trigger

  • A proposal was invited and you are aligning the full review's scope with the editor
  • You want to anticipate what Annals referees of a review push on (different from a paper)
  • The editor has asked you to expand, cut, sharpen the framework, or rebalance coverage
  • You are calibrating revision depth and the twice-yearly cadence

The editor relationship at Annals is unusually direct

Annals' process makes the editor your central partner — more than at most journals. The proposal is reviewed double-blind by the Associate Editors, but once invited, the full review forgoes double-blind and is developed primarily with the Associate Editor and Editor (检索于 2026-06;以官网为准). You are effectively co-developing the review with an expert editor who already endorsed the idea. Use that:

  • The proposal is the scope contract. The four headings you committed to (Focus / Related reviews / Review scope and process / New insights) define what was invited. Departing from them silently is the fastest way to lose editor confidence — renegotiate explicitly if the literature pushes you elsewhere.
  • Lead with the framework in every editor exchange. The editor invited a new way of seeing the field. Decisions about coverage, length, and balance should be argued from whether they strengthen the framework and agenda.
  • Surface conflicts of interest early. If a likely referee is a central author you must critique, tell the editor; it protects the process and you.
  • Calibrate the cadence. Annals runs on a twice-yearly proposal cycle and publishes two issues a year; full-review development and revision can be substantial and multi-round. Plan for real revision effort, not cosmetic edits.

How review differs for a review article

Annals referees do not check an identification strategy or replicate results — there are none. They evaluate the review as a review:

Referee questionWhat they are really checking
Is there a genuine integrative framework?the spine vs. an annotated bibliography (amann-organizing-framework) — the acceptance bar
Does it have "attitude"?a critical, agenda-setting position grounded in evidence, not a neutral tour (amann-writing-style)
Is the coverage complete and systematic?saturation + transparent search; can they name an omitted stream? (amann-literature-synthesis)
Is it balanced and fair?even-handedness across schools; no self-promotion (amann-evidence-standards)
Are the appraisals accurate?does the author characterize each study and its limits correctly
Is it the right scope?broad enough for general interest, but coverable in one ~50-page article

Referees of a review are often the reviewed authors themselves — the people whose work you weigh will read how you weighed it. Balance and accurate attribution are therefore strategic, not just ethical.

A useful frame: the editor recruits referees partly to test the framework, coverage, and fairness, not to re-run statistics. A referee who finds "no real framework," who can name an omitted stream, or who feels their school was caricatured is the single most common cause of a major-revision verdict — all preventable upstream by amann-organizing-framework, amann-literature-synthesis, and amann-evidence-standards.

Checklist

  • Full-review scope reconciled with the invited proposal's four headings; departures renegotiated explicitly
  • Every editor exchange argued from whether it strengthens the framework and agenda
  • Anticipated the six review-referee questions (framework, attitude, coverage, balance, appraisal, scope)
  • Coverage-expansion asks evaluated against the framework before agreeing
  • Conflicts of interest (referees who are reviewed authors) flagged to the editor
  • Attribution and appraisals double-checked, knowing reviewed authors may referee
  • Revision depth and the twice-yearly cadence calibrated from official pages (volatile)

Anti-patterns

  • Treating the editor as a gatekeeper rather than a co-developer of an invited review
  • Drifting from the invited proposal's scope without telling the editor
  • Accepting every "please also cover…" until the review loses its framework and finish-ability
  • Mischaracterizing a reviewed author's work when that author may be your referee
  • Hiding a conflict of interest instead of disclosing it
  • Assuming an invited review gets a light revise; budgeting for cosmetic edits when substantial rework is normal

Output format

【Scope vs. proposal】full review reconciled with invited four headings? Y/N
【Framework-first】editor exchanges argued from framework/agenda strength? Y/N
【Referee anticipation】framework / attitude / coverage / balance / appraisal / scope — prepared each? Y/N
【Coverage asks】evaluated against the framework; accept/push-back plan? Y/N
【COI】reviewed-author referees flagged to editor? Y/N
【Cadence】revision depth + twice-yearly timing calibrated from official pages? Y/N
【Next skill】→ amann-submission (preflight) → amann-revision (after the letter)

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.

中文简介正在准备中。当前显示原文说明。

brycewang-stanford/Awesome-Journal-Skills12972026年9月27日 更新

Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round before SPC/AC discussion.

中文简介正在准备中。当前显示原文说明。

brycewang-stanford/Awesome-Journal-Skills12972026年9月27日 更新

Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.

中文简介正在准备中。当前显示原文说明。

brycewang-stanford/Awesome-Journal-Skills12972026年9月27日 更新

Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.

中文简介正在准备中。当前显示原文说明。

brycewang-stanford/Awesome-Journal-Skills12972026年9月27日 更新

Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.

中文简介正在准备中。当前显示原文说明。

brycewang-stanford/Awesome-Journal-Skills12972026年9月27日 更新

Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.

中文简介正在准备中。当前显示原文说明。

brycewang-stanford/Awesome-Journal-Skills12972026年9月27日 更新

查看 brycewang-stanford 的全部技能

报告此技能的问题