Short
sickn33/agentic-awesome-skills
Rewrite the previous response more briefly while preserving the substance.
A skill your agent uses when targeting Analysis or deciding whether a short, focused philosophy manuscript fits this venue.
MITAuto-check passed
Install Analysis
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills analysis --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/English-Humanities-Journal-Skills/skills/analysis .claude/skills/analysis && 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 "analysis" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/analysis into .claude/skills/analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysis", 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/English-Humanities-Journal-Skills/skills/analysisType 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 analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills analysis --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/English-Humanities-Journal-Skills/skills/analysis .agents/skills/analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analysis" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/analysis into .agents/skills/analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysis", 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 analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills analysis --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/English-Humanities-Journal-Skills/skills/analysis .cursor/skills/analysis && 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 "analysis" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/analysis into .cursor/skills/analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysis", 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 English-Humanities-Journal-Skills/skills/analysis--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 analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills analysis --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/English-Humanities-Journal-Skills/skills/analysis .gemini/skills/analysis && 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 "analysis" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/analysis into .gemini/skills/analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysis", 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 analysisInstalls 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 analysis -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/English-Humanities-Journal-Skills/skills/analysis .github/skills/analysis && 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 "analysis" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/analysis into .github/skills/analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysis", 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 analysis -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 analysis --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/English-Humanities-Journal-Skills/skills/analysis .opencode/skills/analysis && 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 "analysis" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/analysis into .opencode/skills/analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysis", 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
analysis- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 768 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when targeting Analysis or deciding whether a short, focused philosophy manuscript fits this venue.
- Targeting Analysis
- SKILL.md covers Journal positioning, When to trigger, Scope & topic fit and Method & evidence bar, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Deciding whether a short
What it does
Analysis is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting Analysis or deciding whether a short, focused philosophy manuscript fits this venue. Encodes the journal's identity as a home for crisp, single-point articles, counterexamples, and replies; the argument-rigor bar; the brevity-and-focus house style and double-blind norms; official-submission re-check; and desk-reject heuristics.
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
- Targeting Analysis
- Deciding whether a short
- Focused philosophy manuscript fits this venue
Example prompts
- “/analysis”
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
Analysis loads about 1.7k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 768 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). 768 words, ~1,687 tokens.
Download SKILL.mdSave it as
.claude/skills/analysis/SKILL.md (or your agent's skills folder).- name
- analysis
- description
- Use when targeting Analysis or deciding whether a short, focused philosophy manuscript fits this venue. Encodes the journal's identity as a home for crisp, single-point articles, counterexamples, and replies; the argument-rigor bar; the brevity-and-focus house style and double-blind norms; official-submission re-check; and desk-reject heuristics.
Analysis (analysis)
Journal positioning
Analysis, published by Oxford University Press for the Analysis Trust, is the home of short, focused philosophical articles and notes — its identity is brevity and a single sharp point. A canonical Analysis piece makes one crisp argument, presents a decisive counterexample, or mounts a tight reply to a recent paper, and it does so in a few pages rather than a sustained treatise. Its defining expectation is a clear, valid, original argument compressed to its essentials: state the point, make it, dispatch the obvious objection, and stop. A long, multi-part article that develops many threads is a misfit here no matter how good — Analysis rewards the one-idea paper that earns its space. This skill is a fit / venue-selection / re-framing aid. It does not replace the journal's current submission guidelines. Before submitting, re-check the live Analysis author instructions.
When to trigger
- The author names Analysis for a short philosophy note or article and wants a fit/framing check.
- A paper has one sharp idea, counterexample, or reply that should be compressed to Analysis's brevity-and-focus form.
- The author is deciding whether a contribution belongs as a short Analysis note or a full-length article elsewhere.
- The author needs Analysis's brevity/single-point bar and desk-reject heuristics.
Scope & topic fit
- Crisp original arguments across core analytic philosophy — metaphysics, epistemology, mind, language, logic, and value theory — where one point can stand alone.
- Decisive counterexamples that refute or seriously pressure a published claim.
- Tight replies, rejoinders, and discussion notes engaging a specific recent paper or position.
- Sharp distinctions or puzzles introduced and motivated in a few pages.
- Short formal results or observations where the formalism delivers a single clear payoff.
- Any sub-area, provided the contribution is genuinely self-contained and concise.
Method & evidence bar
- The contribution is one original point defended by a valid, tightly compressed argument; the claim is stated immediately and the stakes are obvious.
- The argument is complete on its own terms — a counterexample actually bites, a reply actually answers — without requiring a treatise to land.
- The single most pressing objection is anticipated and dispatched; exhaustive objection-handling is neither expected nor space-permitting.
- Distinctions and key terms are defined with precision; the logical form is transparent.
- Engagement is targeted: cite the specific paper or position being advanced or refuted, not a broad survey.
- Brevity is load-bearing: every paragraph earns its place; nothing is padding.
Structure & house style
- Short note or short article built around a single point; re-check the current length limit and note/article types on the live guide — brevity is enforced.
- The point appears in the opening lines; the piece moves directly to the argument with no long literature review.
- Objections-and-replies, where present, are minimal and integral — the one objection worth raising, answered.
- Citation follows the journal's current style; footnotes are sparing.
- Double-blind review: anonymize the manuscript (self-citations and acknowledgements) per current policy.
- Prose is maximally economical; for a reply, identify the target paper precisely up front.
Show full SKILL.md (284 more words)Show less
Official-submission checklist
- Before giving submission-ready advice, read
../../resources/source-basis.mdand../../resources/official-source-map.md; start from the press/society anchors, then cite the current Analysis page you checked. - Search the live site for "Analysis journal submission guidelines" (Oxford University Press / Analysis Trust) and follow the current version.
- Re-check the strict word/length limit and note/article types, and any abstract requirement.
- Confirm the citation/style format and anonymization for double-blind review.
- Re-check the journal's policy on prior presentation/preprints, simultaneous submission, and AI-use disclosure.
- If the live official instructions conflict with this skill, the official instructions win.
Pre-submission self-check
- The paper makes exactly one sharp, original point, stated in the opening lines.
- The argument (or counterexample/reply) is valid and complete on its own without a treatise.
- The single most pressing objection is anticipated and dispatched.
- The piece is within the strict length limit, with no padding or long literature review.
- The manuscript is anonymized and follows the current citation style.
- For a reply, the target paper/position is identified precisely up front.
Common desk-reject triggers
- A long, multi-part treatise developing several threads — the classic Analysis misfit.
- More than one point, or a single point buried under survey-style scene-setting.
- A counterexample that does not actually bite, or a reply that does not actually answer.
- Padding, lengthy literature review, or apparatus disproportionate to one short point.
- Imprecise theses or undefined key terms in a piece with no room to recover.
- A contribution that genuinely needs full-article length to succeed (route to a generalist venue).
Re-routing decision
- The idea genuinely needs full-length development →
the-philosophical-review/nous/the-journal-of-philosophy. - A sustained argument in the UK/analytic tradition →
mind. - Moral, political, or normative-ethics focus needing room →
ethics/philosophy-and-public-affairs. - Aesthetics / philosophy of art →
the-journal-of-aesthetics-and-art-criticism. - Argument about historical or inquiry-level method →
history-and-theory.
Output format
[Fit] High / Medium / Low (one-line reason)
[Target] Analysis
[Type] short article / counterexample / reply / discussion note
[Thesis] <the single point in one line>
[Argument/engagement] <is it one crisp, valid, self-contained point that fits the brevity bar?>
[Top risk] <the single most likely reason for rejection — usually: too long / more than one point>
[Official items to re-check] <strict length limit / note type / citation style / anonymization / preprint policy>
[Re-route suggestion] <if it needs full-article length, a better-matched venue>© 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 English-Humanities-Journal-Skills/skills/analysis of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Analysis 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 |
|---|---|---|---|---|---|---|
| Analysis this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Shortsickn33/agentic-awesome-skills | 47k | 1 repos | ~281 | Automated safety check: Pass | MIT | |
| Daily Focus Boardgithub/awesome-copilot | 40k | — | ~3k | Automated safety check: Pass | MIT | |
| Focus Stylesthedaviddias/Front-End-Checklist | 74k | — | ~639 | Automated safety check: Pass | MIT | |
| Focus Orderthedaviddias/Front-End-Checklist | 74k | — | ~519 | Automated safety check: Pass | MIT | |
| Focus Managementthedaviddias/Front-End-Checklist | 74k | — | ~465 | Automated safety check: Pass | MIT |
Similar skills
- Official
Daily Focus Board
github/awesome-copilot
Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.
Focus Styles
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Provide visible custom focus indicators.
Focus Order
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure logical focus order.
Focus Management
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Manage focus during dynamic interactions.
Recipe Block Focus Time
googleworkspace/cli
Create recurring focus time blocks on Google Calendar to protect deep work hours.
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 Analysis
What does Analysis do?
A skill your agent uses when targeting Analysis or deciding whether a short, focused philosophy manuscript fits this venue. Analysis is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting Analysis or deciding whether a short, focused philosophy manuscript fits this venue.
When should I use Analysis?
Analysis fits situations like: targeting Analysis; deciding whether a short; focused philosophy manuscript fits this venue.
How do I install Analysis in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill analysis -a claude-code`. Or copy the skill folder (English-Humanities-Journal-Skills/skills/analysis in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/analysis in your project. Claude Code loads it when a task matches its description.
How do I install Analysis in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill analysis -a codex`. Or copy the skill folder (English-Humanities-Journal-Skills/skills/analysis in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/analysis in your project. Codex loads it when a task matches its description.
Can I use Analysis 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 analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analysis, .gemini/skills/analysis, .github/skills/analysis and .opencode/skills/analysis in your project.
What does Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Analysis is instructions for the agent only.
Does Analysis 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 Analysis 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 Analysis use?
Analysis 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 Analysis use?
About 1.7k tokens (SKILL.md is roughly 6.7k 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 Analysis?
Skills that share tags, products or a category with Analysis: Short (sickn33/agentic-awesome-skills, 47k stars), Daily Focus Board (github/awesome-copilot, 40k stars), Focus Styles (thedaviddias/Front-End-Checklist, 74k stars) and Focus Order (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analysis?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,216 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.