Editorial Policy
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing a blog, news site, or YMYL content site for trust signals, drafting editorial policy page content, or evaluating whether a site meets Google's quality rater…
A skill your agent uses when working with the Annual Review of Sociology (ARSoc) Editorial Committee and Annual Reviews production team — negotiating the commissioned scope, anticipating what review…
MITAuto-check passed
Install Arsoc Editor Strategy
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arsoc-editor-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills arsoc-editor-strategy --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-editor-strategy .claude/skills/arsoc-editor-strategy && 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-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-editor-strategy into .claude/skills/arsoc-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-editor-strategy", 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-editor-strategyType 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-editor-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills arsoc-editor-strategy --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-editor-strategy .agents/skills/arsoc-editor-strategy && 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-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-editor-strategy into .agents/skills/arsoc-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-editor-strategy", 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-editor-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills arsoc-editor-strategy --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-editor-strategy .cursor/skills/arsoc-editor-strategy && 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-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-editor-strategy into .cursor/skills/arsoc-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-editor-strategy", 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-editor-strategy--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-editor-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills arsoc-editor-strategy --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-editor-strategy .gemini/skills/arsoc-editor-strategy && 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-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-editor-strategy into .gemini/skills/arsoc-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-editor-strategy", 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-editor-strategyInstalls 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-editor-strategy -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-editor-strategy .github/skills/arsoc-editor-strategy && 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-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-editor-strategy into .github/skills/arsoc-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-editor-strategy", 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-editor-strategy -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-editor-strategy --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-editor-strategy .opencode/skills/arsoc-editor-strategy && 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-editor-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Annual-Review-of-Sociology-Skills/skills/arsoc-editor-strategy into .opencode/skills/arsoc-editor-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arsoc-editor-strategy", 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-editor-strategy- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 767 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when working with the Annual Review of Sociology (ARSoc) Editorial Committee and Annual Reviews production team — negotiating the commissioned scope, anticipating what review…
- Anticipating what review referees evaluate
- SKILL.md covers When to trigger, Who you are working with at…, How review differs for a… and Sociology-specific editorial…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The annual-volume timeline
What it does
Arsoc Editor Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when working with the Annual Review of Sociology (ARSoc) Editorial Committee and Annual Reviews production team — negotiating the commissioned scope, anticipating what review referees evaluate, and the annual-volume timeline. Plans the interaction; it does not run the delivery preflight (arsoc-submission) or draft the response letter (arsoc-revision).
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Anticipating what review referees evaluate
- The annual-volume timeline
Example prompts
- “/arsoc-editor-strategy”
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 Editor Strategy loads about 1.7k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 767 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). 767 words, ~1,657 tokens.
Download SKILL.mdSave it as
.claude/skills/arsoc-editor-strategy/SKILL.md (or your agent's skills folder).- name
- arsoc-editor-strategy
- description
- Use when working with the Annual Review of Sociology (ARSoc) Editorial Committee and Annual Reviews production team — negotiating the commissioned scope, anticipating what review referees evaluate, and the annual-volume timeline. Plans the interaction; it does not run the delivery preflight (arsoc-submission) or draft the response letter (arsoc-revision).
Editor & Committee Strategy (arsoc-editor-strategy)
When to trigger
- The Editorial Committee invited the topic and you are negotiating the review's scope
- You want to anticipate what ARSoc reviewers of a review will push on (different from a paper)
- The editor has asked you to expand, cut, or rebalance coverage
- You are calibrating how the Committee review cycle and the Annual Reviews production timeline work
Who you are working with at ARSoc
ARSoc is run by an Editorial Committee — an editor (检索于 2026-06：co-editors Douglas Massey & Mary C. Waters；以官网为准), associate editors, regular members serving multi-year terms, and occasional one-year guest members — plus the journal's production team at Annual Reviews. Your primary partners differ by phase: the commissioning editor / Committee owns scope and acceptance; the production editor owns format, figures, copyediting, and the volume schedule. Because the article is commissioned, the relationship is more collaborative than adversarial — the Committee wants the review to succeed — but acceptance is not automatic: an invited manuscript is still assessed for accuracy, rigor, and balance (检索于 2026-06；以官网为准).
How review differs for a review article
ARSoc reviewers do not check an identification strategy or replicate results — there are none of the author's own. They evaluate the review as a review:
| Reviewer question | What they are really checking |
|---|---|
| Is the coverage complete? | the saturation/coverage account from arsoc-literature-synthesis / arsoc-transparency-and-reproducibility — can they name an omitted literature? |
| Is it balanced and accurate? | even-handedness across schools and methods; no self-promotion (arsoc-comprehensiveness-and-balance) |
| Is there a real framework? | the spine vs. an annotated bibliography (arsoc-organizing-framework) |
| Is it accessible? | can a sociologist from another subfield follow it (arsoc-writing-style) |
| Are the appraisals fair and correct? | does the author characterize each study's contribution and limits accurately |
| Is it the right scope? | not too narrow (specialist review) nor unfinishably broad (handbook) |
Reviewers of an ARSoc review are often the reviewed authors themselves — the people whose work is being weighed will read how you weighed it. This makes balance and accurate attribution strategic, not just ethical.
Sociology-specific editorial posture
- Treat the editor conversation as a scope contract about traditions, methods, and levels of analysis: theory, ethnography, historical/comparative work, surveys, experiments, networks, demography, and computational sociology do not ask identical evidence questions.
- When an editor asks for broader coverage, answer by naming which sociological debate the added work changes: mechanism, institution, inequality axis, cultural process, population pattern, organizational field, or methodological boundary.
- Push back on additions that flatten traditions into a bibliography; ARSoc value comes from mapping a debate and its tensions, not from treating every subfield as interchangeable coverage.
Show full SKILL.md (350 more words)Show less
Scope negotiation with the Committee
- Lock scope early, in writing. The invitation/acceptance stage is where scope is cheapest to change. Confirm the boundaries — including which traditions and methods are in — before months of reading.
- Negotiate, don't capitulate, on coverage asks. If a referee or editor wants an added literature, assess whether it fits the spine; propose where it goes or explain why it is out of scope — a review cannot grow without bound and must stay in the word/page envelope (检索于 2026-06；以官网为准).
- Surface conflicts of interest. If a likely reviewer is a central author you must critique, tell the editor — Annual Reviews requires disclosure of potential bias, and it protects both the process and you.
- Respect the volume schedule. ARSoc publishes one volume per year; production has fixed deadlines. A late draft can slip a whole volume. Confirm the timeline with the production editor and plan backward from it.
- Keep a coverage ledger. Maintain a short, sharable record of what is in scope and why (and what was deliberately excluded), so when the editor or a referee asks "why not X?", you answer with a decision already made.
Checklist
- Scope agreed with the commissioning editor in writing at the invitation stage (traditions + methods specified)
- Anticipated the six review-referee questions (coverage, balance/accuracy, framework, accessibility, appraisal, scope)
- Coverage-expansion asks evaluated against the spine and the word/page envelope before agreeing
- Conflicts of interest (reviewers who are reviewed authors) flagged to the editor
- Attribution and appraisals double-checked, knowing reviewed authors may referee
- Volume/production timeline calibrated with the production editor (volatile — confirm)
- A plan for which asks you accept vs. push back on, with reasons
Anti-patterns
- Treating an invitation as guaranteed acceptance — invited reviews are still assessed for rigor and balance
- Accepting every "please also cover…" until the review loses its spine and overruns the envelope
- Mischaracterizing a reviewed author's work when that author may be your reviewer
- Hiding a conflict of interest instead of disclosing it (Annual Reviews requires disclosure)
- Missing the production deadline and slipping the volume
- Asserting current editors / timeline / process from memory rather than the live Annual Reviews pages
Output format
【Scope agreement】boundaries (traditions + methods) locked with editor in writing? Y/N
【Referee anticipation】coverage / balance / framework / accessibility / appraisal / scope — prepared each? Y/N
【Coverage asks】evaluated against spine + envelope; accept/push-back plan? Y/N
【COI】reviewed-author referees flagged to editor? Y/N
【Timeline】volume/production schedule calibrated? Y/N · 待核实
【Source status】current editors/process re-confirmed on Annual Reviews pages? Y/N
【Next step】→ arsoc-submission (delivery preflight)© 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-editor-strategy of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Arsoc Editor Strategy 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 Editor Strategy this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Editorial Policythedaviddias/Front-End-Checklist | 74k | — | ~763 | Automated safety check: Pass | MIT | |
| Editorial Designsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| After Hours Editorial Templatenexu-io/open-design | 100k | — | ~607 | Automated safety check: Pass | Apache-2.0 | |
| Editorialbergside/awesome-design-skills | 3.1k | 1 repos | ~915 | Automated safety check: Pass | MIT | |
| Editorial Burgundy Principles Templatenexu-io/open-design | 100k | — | ~461 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Editorial Design
sickn33/agentic-awesome-skills
Web and App implementation guide for Editorial Design. An agent skill from sickn33/agentic-awesome-skills.
After Hours Editorial Template
nexu-io/open-design
Luxury dark-editorial HyperFrames template for three-page cinematic storyboards, inspired by haute couture title cards and magazine chapter spreads.
Editorial
bergside/awesome-design-skills
Magazine-inspired editorial layout with refined serif typography, structured grids, and elegant reading experiences.
Editorial Burgundy Principles Template
nexu-io/open-design
Editorial studio deck template in burgundy / blush / muted-gold palette.
Paseo Committee
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
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…
Questions about Arsoc Editor Strategy
What does Arsoc Editor Strategy do?
A skill your agent uses when working with the Annual Review of Sociology (ARSoc) Editorial Committee and Annual Reviews production team — negotiating the commissioned scope, anticipating what review…. Arsoc Editor Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when working with the Annual Review of Sociology (ARSoc) Editorial Committee and Annual Reviews production team — negotiating the commissioned scope, anticipating what review referees evaluate, and the annual-volume timeline.
When should I use Arsoc Editor Strategy?
Arsoc Editor Strategy fits situations like: anticipating what review referees evaluate; the annual-volume timeline.
How do I install Arsoc Editor Strategy in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arsoc-editor-strategy -a claude-code`. Or copy the skill folder (Annual-Review-of-Sociology-Skills/skills/arsoc-editor-strategy in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/arsoc-editor-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Arsoc Editor Strategy in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arsoc-editor-strategy -a codex`. Or copy the skill folder (Annual-Review-of-Sociology-Skills/skills/arsoc-editor-strategy in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/arsoc-editor-strategy in your project. Codex loads it when a task matches its description.
Can I use Arsoc Editor Strategy 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-editor-strategy -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-editor-strategy, .gemini/skills/arsoc-editor-strategy, .github/skills/arsoc-editor-strategy and .opencode/skills/arsoc-editor-strategy in your project.
What does Arsoc Editor Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Arsoc Editor Strategy is instructions for the agent only.
Does Arsoc Editor Strategy 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 Editor Strategy 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 Editor Strategy use?
Arsoc Editor Strategy 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 Editor Strategy use?
About 1.7k tokens (SKILL.md is roughly 6.6k 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 Editor Strategy?
Skills that share tags, products or a category with Arsoc Editor Strategy: Editorial Policy (thedaviddias/Front-End-Checklist, 74k stars), Editorial Design (sickn33/agentic-awesome-skills, 47k stars), After Hours Editorial Template (nexu-io/open-design, 100k stars) and Editorial (bergside/awesome-design-skills, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Arsoc Editor Strategy?
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.