SkillAgentSearch skills...

amann-revision

Use when responding to an Academy of Management Annals (Annals) proposal decision or full-review referee letter — framework/attitude asks, coverage gaps, balance complaints, and accessibility.

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Supported Platforms

Cline

Our assessment of amann-revision

amann-revision scores 88/100 on our quality scale, 1962nd of 4,702 Development & Engineering skills we index (top 42%).

Its SKILL.md is 5.9 KB long, well organised into 8 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
17/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so amann-revision is actively maintained.
  • Our last check on 2026-11-01 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

amann-revision compared with similar skills

All 4 of these similar skills score higher than amann-revision; compare them before choosing.

SkillScoreStarsUpdatedFormat
amann-revision (this skill)by brycewang-stanford881.2k2mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.9k8d agoCLAUDE.md

Frequently asked questions

How do I install amann-revision?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision. The install tabs above show the steps for each supported agent.
Which AI agents does amann-revision work with?
It is written for Cline, as a SKILL.md file. Other agents that read the same format can often use it too.
Is amann-revision safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is amann-revision still maintained?
The repository was last updated about 2 months ago, so amann-revision is actively maintained.

name: amann-revision description: Use when responding to an Academy of Management Annals (Annals) proposal decision or full-review referee letter — framework/attitude asks, coverage gaps, balance complaints, and accessibility. Drafts the response letter and revision plan; it does not run the portal preflight (amann-submission) or redesign the framework from scratch (amann-organizing-framework).

Revision & Response for a Review (amann-revision)

When to trigger

  • A proposal decision letter arrived (invited / revise-and-resubmit / declined)
  • A full-review referee letter arrived (major revision is the norm for a long review)
  • Referees flagged "no real framework," missing streams, imbalance, or "reads like a list"
  • You need a point-by-point response letter for a review article, not a primary paper

First: which letter is this?

Annals' two-step process produces two kinds of feedback, and they call for different moves:

  • Proposal-stage feedback (double-blind, from the Associate Editors). The decision is mainly about fit and promise: is the literature Annals-scale, and is there a genuinely new framework under "New insights"? A revise-and-resubmit here usually means sharpen the contribution before the full review is invited — route back through amann-topic-selection / amann-organizing-framework / amann-proposal-framing.
  • Full-review feedback (editor-only: Associate Editor and Editor). The review is being developed; feedback is about execution — framework strength, coverage, balance, attitude, accessibility. This is the classic point-by-point revision below.

Categories of full-review feedback (and how to answer each)

Triage every point into one bucket:

| Feedback type | Typical phrasing | Response move | |---------------|------------------|---------------| | Framework / contribution | "this is an annotated bibliography" / "where is the integration?" | strengthen or make explicit the spine (amann-organizing-framework); do not just reorder — this is the acceptance bar | | Attitude / agenda | "this is descriptive; take a position" / "the agenda is generic" | add the critical position and a framework-tied agenda (amann-writing-style) | | Coverage gap | "you omit the X stream / author Y" | almost always concede and integrate; place the work in the right cell; re-run saturation (amann-literature-synthesis) | | Balance / fairness | "this slights school Z / over-cites the author" | steelman the slighted side; re-audit self-citation (amann-evidence-standards) | | Appraisal accuracy | "you mischaracterize study W" | correct it precisely — reviewed authors often referee | | Scope | "too broad / too narrow" | renegotiate with the editor (amann-editor-strategy); rescope deliberately, not by random cuts |

Writing the response letter

  • Point-by-point, quote-then-respond. Reproduce each comment, then state the change and where it lives (section/page/table/figure).
  • Framework asks are existential — answer them first. "No real framework" is a reject reason at Annals; a stronger or more explicit spine, not reordered paragraphs, is the required answer.
  • Coverage asks: concede gracefully and integrate. A missing stream is a real defect in a review-of-the-field; adding it strengthens the article. Resist defensiveness.
  • Balance asks: show the steelman. Demonstrate the revised text states the other side at its strongest.
  • Disagree rarely and respectfully. If an ask would break the framework or expand scope unfinishably, explain the trade-off and propose an alternative, ideally pre-cleared with the editor.
  • Keep the editor central. Because the full review is developed with the AE and Editor, route scope conflicts and incompatible asks to them rather than trying to satisfy everyone.
  • Track every addition's ripple. Adding a stream can shift the review's center of gravity; after each integration, re-check that the framework cells, the synthesis tables, and the balance audit still hold.

Checklist

  • [ ] Identified whether the letter is proposal-stage (fit/promise) or full-review (execution)
  • [ ] Every comment triaged (framework / attitude / coverage / balance / appraisal / scope)
  • [ ] "No framework" / "annotated bibliography" answered with a stronger explicit spine, not reordering
  • [ ] "Descriptive" answered by adding a critical position + framework-tied agenda
  • [ ] Coverage gaps conceded and integrated into the right cell; saturation re-run
  • [ ] Balance complaints answered by demonstrable steelmanning + self-citation re-audit
  • [ ] Mischaracterizations corrected precisely (reviewed authors may be the referees)
  • [ ] Scope conflicts routed to the editor for adjudication
  • [ ] Point-by-point letter: quote-then-respond, with section/page/table locations
  • [ ] Framework, coverage, and balance re-audited after all additions

Anti-patterns

  • "Fixing" a no-framework critique by shuffling paragraphs without strengthening the spine
  • Answering a "be more provocative" ask with the same neutral prose
  • Defending an omission rather than adding the missing stream (a review gap is a real defect)
  • Answering a balance complaint with assertions of fairness instead of revised, steelmanned text
  • Mischaracterizing or dismissing a reviewed author who is likely your referee
  • Bloating scope to satisfy every "also cover…" until the review no longer finishes

Output format

【Letter type】proposal-stage (fit/promise) / full-review (execution)
【Triage】each comment bucketed (framework/attitude/coverage/balance/appraisal/scope)? Y/N
【Framework asks】spine strengthened/made explicit (not reordered)? Y/N
【Attitude/agenda】critical position + framework-tied agenda added? Y/N
【Coverage gaps】conceded + integrated into cells; saturation re-run? Y/N
【Balance】steelman shown in revised text; self-citation re-audited? Y/N
【Scope conflicts】routed to editor? Y/N
【Letter】point-by-point, quote-then-respond, with locations? Y/N
【Next skill】→ amann-submission (re-preflight the revised proposal or review)

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryDevelopment
Updated2mo ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions