Review Component
Endava/BEEQ
Review a BEEQ StencilJS component against design system guidelines and project standards.
A skill your agent uses when responding to an Academy of Management Annals (Annals) proposal decision or full-review referee letter — framework/attitude asks, coverage gaps, balance complaints, and…
Install Amann Revision
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-revision --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-revision .claude/skills/amann-revision && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "amann-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-revision into .claude/skills/amann-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-revision", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-revisionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-revision --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-revision .agents/skills/amann-revision && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "amann-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-revision into .agents/skills/amann-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-revision", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-revision --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-revision .cursor/skills/amann-revision && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "amann-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-revision into .cursor/skills/amann-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-revision", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Academy-of-Management-Annals-Skills/skills/amann-revision--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-revision --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-revision .gemini/skills/amann-revision && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "amann-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-revision into .gemini/skills/amann-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-revision", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-revisionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-revision .github/skills/amann-revision && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "amann-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-revision into .github/skills/amann-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-revision", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills amann-revision --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Academy-of-Management-Annals-Skills/skills/amann-revision .opencode/skills/amann-revision && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "amann-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Academy-of-Management-Annals-Skills/skills/amann-revision into .opencode/skills/amann-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "amann-revision", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
amann-revision- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 635 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when responding to an Academy of Management Annals (Annals) proposal decision or full-review referee letter — framework/attitude asks, coverage gaps, balance complaints, and…
- Responding to an Academy of Management Annals (Annals) proposal decision
- SKILL.md covers When to trigger, First: which letter is this?, Categories of full-review… and Writing the response letter, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Full-review referee letter — framework/attitude asks
What it does
Amann Revision is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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).
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Test coverage and Accessibility. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Responding to an Academy of Management Annals (Annals) proposal decision
- Full-review referee letter — framework/attitude asks
- Balance complaints
Example prompts
- “/amann-revision”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Amann Revision loads about 1.5k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 635 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 635 words, ~1,522 tokens.
Download SKILL.mdSave it as
.claude/skills/amann-revision/SKILL.md (or your agent's skills folder).- 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.
Show full SKILL.md (169 more words)Show less
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)© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Academy-of-Management-Annals-Skills/skills/amann-revision of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Amann Revision next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Amann Revision this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Review ComponentEndava/BEEQ | 163 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Scenario MapOwl-Listener/inclusive-design-skills | 105 | — | ~568 | Automated safety check: Pass | MIT | |
| Libreqos Review Subagents WorkflowLibreQoE/LibreQoS | 721 | — | ~1.2k | Automated safety check: Pass | GPL-2.0 | |
| WCAG 2.2 Accessibility AuditAIPexStudio/AIPex | 1.3k | — | ~4.7k | Automated safety check: Pass | MIT | |
| Control UIcursor/plugins | 11k | 2 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Scenario Map
Owl-Listener/inclusive-design-skills
Map inclusive usage scenarios across ability spectrums for a product or feature.
Libreqos Review Subagents Workflow
LibreQoE/LibreQoS
Project workflow for invoking the local review sub-agents Thomas, Helen, Beck, Jonas, The Reaper, and Heckler during LibreQoS coding sessions.
WCAG 2.2 Accessibility Audit
AIPexStudio/AIPex
Audits a live webpage against eight core WCAG 2.2 success criteria, combining accessibility-tree inspection, visual screenshots and keyboard navigation tests, with evidence in the report.
- Official
Control UI
cursor/plugins
Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI.
Vrt
marigold-ui/marigold
DST — Trigger the Visual-Regression-Tests (Chromatic) GitHub Actions workflow on the current or a given branch.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Questions about Amann Revision
What does Amann Revision do?
A skill your agent uses when responding to an Academy of Management Annals (Annals) proposal decision or full-review referee letter — framework/attitude asks, coverage gaps, balance complaints, and…. Amann Revision is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Amann Revision?
Amann Revision fits situations like: responding to an Academy of Management Annals (Annals) proposal decision; full-review referee letter — framework/attitude asks; balance complaints.
How do I install Amann Revision in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision -a claude-code`. Or copy the skill folder (Academy-of-Management-Annals-Skills/skills/amann-revision in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/amann-revision in your project. Claude Code loads it when a task matches its description.
How do I install Amann Revision in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision -a codex`. Or copy the skill folder (Academy-of-Management-Annals-Skills/skills/amann-revision in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/amann-revision in your project. Codex loads it when a task matches its description.
Can I use Amann Revision in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill amann-revision -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/amann-revision, .gemini/skills/amann-revision, .github/skills/amann-revision and .opencode/skills/amann-revision in your project.
What does Amann Revision need to run?
SKILL.md names no scripts, command-line tools or credentials: Amann Revision is instructions for the agent only.
Does Amann Revision access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Amann Revision safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Amann Revision use?
Amann Revision is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Amann Revision use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Amann Revision?
Skills that share tags, products or a category with Amann Revision: Review Component (Endava/BEEQ, 163 stars), Scenario Map (Owl-Listener/inclusive-design-skills, 105 stars), Libreqos Review Subagents Workflow (LibreQoE/LibreQoS, 721 stars) and WCAG 2.2 Accessibility Audit (AIPexStudio/AIPex, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Amann Revision?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.