Review Component
Endava/BEEQ
Review a BEEQ StencilJS component against design system guidelines and project standards.
A skill your agent uses when responding to Editorial Committee and referee feedback on an Annual Review of Sociology (ARSoc) review — coverage gaps, balance/accuracy complaints, framework/structure…
Install Arsoc Revision
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arsoc-revision -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills arsoc-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/Annual-Review-of-Sociology-Skills/skills/arsoc-revision .claude/skills/arsoc-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 "arsoc-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-revision into .claude/skills/arsoc-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-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/Annual-Review-of-Sociology-Skills/skills/arsoc-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 arsoc-revision -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills arsoc-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/Annual-Review-of-Sociology-Skills/skills/arsoc-revision .agents/skills/arsoc-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 "arsoc-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-revision into .agents/skills/arsoc-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-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 arsoc-revision -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills arsoc-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/Annual-Review-of-Sociology-Skills/skills/arsoc-revision .cursor/skills/arsoc-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 "arsoc-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-revision into .cursor/skills/arsoc-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-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 Annual-Review-of-Sociology-Skills/skills/arsoc-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 arsoc-revision -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills arsoc-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/Annual-Review-of-Sociology-Skills/skills/arsoc-revision .gemini/skills/arsoc-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 "arsoc-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-revision into .gemini/skills/arsoc-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-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 arsoc-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 arsoc-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/Annual-Review-of-Sociology-Skills/skills/arsoc-revision .github/skills/arsoc-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 "arsoc-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-revision into .github/skills/arsoc-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-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 arsoc-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 arsoc-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/Annual-Review-of-Sociology-Skills/skills/arsoc-revision .opencode/skills/arsoc-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 "arsoc-revision" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-revision into .opencode/skills/arsoc-revision/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-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
arsoc-revision- GitHub stars
- 1.2k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 896 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 Editorial Committee and referee feedback on an Annual Review of Sociology (ARSoc) review — coverage gaps, balance/accuracy complaints, framework/structure…
- Responding to Editorial Committee and referee feedback on an Annual Review of Sociology (ARSoc) review — coverage gaps
- SKILL.md covers When to trigger, Categories of review feedback…, ARSoc-specific revision ledger and Writing the response letter, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Balance/accuracy complaints
What it does
Arsoc Revision is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when responding to Editorial Committee and referee feedback on an Annual Review of Sociology (ARSoc) review — coverage gaps, balance/accuracy complaints, framework/structure asks, and accessibility. Drafts the response and revision plan; it does not run the delivery preflight (arsoc-submission) or redesign the spine from scratch (arsoc-organizing-framework).
Its SKILL.md is about 2.1k 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 Editorial Committee and referee feedback on an Annual Review of Sociology (ARSoc) review — coverage gaps
- Balance/accuracy complaints
- Framework/structure asks
Example prompts
- “/arsoc-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
Arsoc Revision loads about 2.1k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 896 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). 896 words, ~2,063 tokens.
Download SKILL.mdSave it as
.claude/skills/arsoc-revision/SKILL.md (or your agent's skills folder).- name
- arsoc-revision
- description
- Use when responding to Editorial Committee and referee feedback on an Annual Review of Sociology (ARSoc) review — coverage gaps, balance/accuracy complaints, framework/structure asks, and accessibility. Drafts the response and revision plan; it does not run the delivery preflight (arsoc-submission) or redesign the spine from scratch (arsoc-organizing-framework).
Revision & Response for a Review (arsoc-revision)
When to trigger
- A Committee/referee letter on the invited review arrived
- Referees flagged missing literatures, imbalance, mischaracterization, method-siloing, or "reads like a list"
- The editor asked to expand, cut, or rebalance coverage, or to make the framework explicit
- You need a point-by-point response for a review article, not a primary paper
Categories of review feedback (and how to answer each)
ARSoc revision asks cluster differently from primary-research asks. Triage every point into one bucket:
| Feedback type | Typical phrasing | Response move |
|---|---|---|
| Coverage gap | "you omit the X literature / author Y / the qualitative work" | almost always concede and integrate — place the missing work in the right framework cell; re-run saturation (arsoc-literature-synthesis) and update the coverage account |
| Balance / fairness | "this slights school Z / over-cites the author / dismisses method M" | steelman the slighted side; re-audit self-citation and method balance (arsoc-comprehensiveness-and-balance) |
| Appraisal accuracy | "you mischaracterize study W" | correct precisely; reviewed authors often referee — fix exactly |
| Framework / structure | "this is an annotated bibliography" | strengthen or make explicit the spine (arsoc-organizing-framework); do not just reorder paragraphs |
| Accessibility | "a sociologist outside the subfield can't follow Section 4" | add intuition, define jargon (arsoc-writing-style) |
| Scope | "too broad / too narrow / overruns length" | negotiate with the editor (arsoc-editor-strategy); rescope deliberately, within the envelope |
| Transparency | "how did you decide what to include?" | document/expand the coverage account (arsoc-transparency-and-reproducibility) |
ARSoc-specific revision ledger
Annual Review of Sociology revisions should make the sociology of the review visible: which subfields, methods, theoretical traditions, and evidentiary communities are being asked to recognize the synthesis as fair. Keep a ledger that distinguishes "we added citations" from "we repaired the review's sociological coverage contract."
| Revision pressure | Evidence to add or rebalance | Where it should show up |
|---|---|---|
| Subfield omission | missing conversation, classic line, or contemporary debate | coverage account plus framework cell |
| Method-siloing | qualitative, quantitative, comparative-historical, computational, or mixed-method evidence | method-balance table and synthesis text |
| Theory lineage dispute | genealogy of concepts, schools, and critiques | theory map, not only parenthetical citations |
| Positionality / power concern | whose standpoint, institution, or case is centered | appraisal paragraphs and limitations |
| Cross-subfield accessibility | translation of terms across adjacent sociological audiences | section openings and bridge sentences |
| Inclusion-rule opacity | search terms, boundary decisions, and excluded literatures | transparent coverage account |
Use this ledger before drafting the letter; it keeps the reply from sounding like a generic Annual Review response and shows that the revised article can travel across sociology's internal audiences.
Writing the response letter
- Point-by-point, quote-then-respond. Reproduce each comment, then state the change and where it lives (section/page/table).
- Coverage asks: concede and integrate. A missing literature is a real defect in a review of record; adding it strengthens the article. Resist defensiveness — the omitting author may be the referee who named it.
- Balance asks: show the steelman. Demonstrate the revised text states the other side at its strongest; that is what a fairness complaint actually demands. If a method was slighted, show it is now weighed on its own terms.
- Accuracy asks: fix exactly. Mischaracterizing a reviewed author who is your referee is the fastest route to a hostile second round; correct the wording precisely and, where helpful, quote their own framing.
- Make method pluralism concrete. Acknowledge what each evidence mode can and cannot show instead of ranking methods implicitly by citation count or table space.
- Repair the coverage account when the draft changes. New literatures can alter the logic of inclusion, so update the account rather than treating transparency as a static appendix.
- Disagree rarely and respectfully. If an ask would break the spine or overrun the envelope, explain the trade-off and propose an alternative, ideally pre-cleared with the editor.
- Keep the editor central. On scope and conflicting referee asks, ask the Committee editor to adjudicate rather than satisfying mutually-incompatible referees.
- Track every addition's ripple. Adding a literature can shift the review's center of gravity; after each integration, re-check that the framework cells, the summary tables, the balance audit, and the coverage account still hold, and that the draft still fits the volume's length envelope.
- Mind the volume clock. Revisions run against a production deadline (
arsoc-editor-strategy); plan the rework so the article stays in its volume.
Show full SKILL.md (215 more words)Show less
Checklist
- Every comment triaged into a bucket (coverage / balance / appraisal / framework / accessibility / scope / transparency)
- Coverage gaps conceded and integrated into the right framework cell; saturation + coverage account re-run
- Balance complaints answered by demonstrable steelmanning + self-citation and method-balance re-audit
- Mischaracterizations corrected precisely (reviewed authors may be the referees)
- "Annotated bibliography" asks answered by a stronger/explicit spine, not reordering
- Subfield, method, theory-lineage, power/positionality, and inclusion-rule concerns logged separately
- Accessibility fixes add intuition / define jargon for the cross-subfield reader
- Scope conflicts routed to the editor; rework fits the envelope and the volume deadline
- Point-by-point letter: quote-then-respond, with section/page/table locations
- Comprehensiveness + balance + coverage account re-audited after all additions
Anti-patterns
- Defending an omission rather than adding the missing literature (a review gap is a real defect)
- Answering a balance complaint with assertions of fairness instead of revised, steelmanned text
- Dismissing or re-mischaracterizing a reviewed author who is likely your referee
- "Fixing" an annotated-bibliography critique by shuffling paragraphs without imposing a spine
- Letting method balance mean "one paragraph per method" rather than a real account of evidentiary limits
- Updating citations while leaving the inclusion rule or theory lineage unexplained
- Bloating scope to satisfy every "also cover…" until the review overruns its length and slips the volume
- Trying to satisfy two contradictory referees instead of asking the editor to decide
Output format
【Triage】each comment bucketed (coverage/balance/appraisal/framework/accessibility/scope/transparency)? Y/N
【Coverage gaps】conceded + integrated into framework cells; saturation + account re-run? Y/N
【Balance】steelman shown in revised text; self-citation + method balance re-audited? Y/N
【Appraisal fixes】mischaracterizations corrected precisely? Y/N
【Framework asks】spine strengthened/made explicit (not reordered)? Y/N
【Sociology ledger】subfield/method/theory/power/inclusion-rule concerns separated? Y/N
【Scope/length】fits envelope + volume deadline? Y/N
【Letter】point-by-point, quote-then-respond, with locations? Y/N
【Next step】→ arsoc-submission (re-deliver the revised 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 Annual-Review-of-Sociology-Skills/skills/arsoc-revision of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Arsoc 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 |
|---|---|---|---|---|---|---|
| Arsoc Revision this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~2.1k | 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 Arsoc Revision
What does Arsoc Revision do?
A skill your agent uses when responding to Editorial Committee and referee feedback on an Annual Review of Sociology (ARSoc) review — coverage gaps, balance/accuracy complaints, framework/structure…. Arsoc Revision is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when responding to Editorial Committee and referee feedback on an Annual Review of Sociology (ARSoc) review — coverage gaps, balance/accuracy complaints, framework/structure asks, and accessibility.
When should I use Arsoc Revision?
Arsoc Revision fits situations like: responding to Editorial Committee and referee feedback on an Annual Review of Sociology (ARSoc) review — coverage gaps; balance/accuracy complaints; framework/structure asks.
How do I install Arsoc Revision in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arsoc-revision -a claude-code`. Or copy the skill folder (Annual-Review-of-Sociology-Skills/skills/arsoc-revision in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/arsoc-revision in your project. Claude Code loads it when a task matches its description.
How do I install Arsoc Revision in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arsoc-revision -a codex`. Or copy the skill folder (Annual-Review-of-Sociology-Skills/skills/arsoc-revision in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/arsoc-revision in your project. Codex loads it when a task matches its description.
Can I use Arsoc 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 arsoc-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/arsoc-revision, .gemini/skills/arsoc-revision, .github/skills/arsoc-revision and .opencode/skills/arsoc-revision in your project.
What does Arsoc Revision need to run?
SKILL.md names no scripts, command-line tools or credentials: Arsoc Revision is instructions for the agent only.
Does Arsoc 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 Arsoc 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 Arsoc Revision use?
Arsoc 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 Arsoc Revision use?
About 2.1k tokens (SKILL.md is roughly 8.3k 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 Arsoc Revision?
Skills that share tags, products or a category with Arsoc 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 Arsoc 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.