en-humanities-journal-workflow
Use when deciding which English humanities journal skill to invoke next, comparing fit across the 36-journal humanities roadmap, or routing a manuscript before venue-specific re-framing. Routes by sub-field (history / philosophy / literary studies / classics / art history / religion / linguistics / musicology), contribution type (argument, interpretation, theory, edition), and the venue's house style and review norms.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-humanities-journal-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Humanities journal workflow (en-humanities-journal-workflow) ## Purpose This is the routing skill for the humanities bundle. It does not replace a single-journal profile; it first classifies the manuscript by **sub-field, contribution type, and method/approach**, then routes into the matching per-journal skill for fit and re-framing. It is a sibling to `en-natsci-journal-workflow`, `en-engtech-journal-workflow`, and `en-journal-workflow`. ## Ask four things first 1. **Sub-field:** history, philosophy, literary studies, classics, art/architectural history, religious studies, linguistics, or musicology/aesthetics? 2. **Contribution type:** an original argument or interpretation, a theoretical or conceptual intervention, a recovery of new primary sources/evidence, a critical edition or attribution, or a methodological/historiographical reframing? 3. **Approach:** archival/empirical, close reading/textual, analytic/formal, theoretical/critical, or object-/image-based? 4. **Audience:** the whole field (a generalist flagship), a period/area specialty, or a method/theory community? ## Quick routing | Manuscript signature | Prefer skill | |---|---| | Broad, field-defining historical argu
- Purpose
- Ask four things first
- Quick routing
- Sibling-journal disambiguation
- Decision rules
- Output format
What does the en-humanities-journal-workflow skill do?
Use when deciding which English humanities journal skill to invoke next, comparing fit across the 36-journal humanities roadmap, or routing a manuscript before venue-specific re-framing. Routes by sub-field (history / philosophy / literary studies / classics / art history / religion / linguistics / musicology), contribution type (argument, interpretation, theory, edition), and the venue's house style and review norms.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-humanities-journal-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.