A skill your agent uses when targeting History and Theory or deciding whether a philosophy-of-history, historiography, or historical-method manuscript fits this venue.

MITAuto-check passed

Install History And Theory

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill history-and-theory -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills history-and-theory --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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/history-and-theory .claude/skills/history-and-theory && rm -rf skills-src

Use ~/.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/

Facts

Skill name
history-and-theory
GitHub stars
1.2k
Token cost
~1.9k tokens
SKILL.md length
810 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when targeting History and Theory or deciding whether a philosophy-of-history, historiography, or historical-method manuscript fits this venue.

  • Targeting History and Theory
  • 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 philosophy-of-history

What it does

History And Theory is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting History and Theory or deciding whether a philosophy-of-history, historiography, or historical-method manuscript fits this venue. Encodes the journal's meta-level theoretical bar, its historiographical and conceptual expectations, house style and double-blind norms, official-submission re-check, and desk-reject heuristics.

Its SKILL.md is about 1.9k 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 History and Theory
  • Deciding whether a philosophy-of-history
  • Historical-method manuscript fits this venue

Example prompts

  • “/history-and-theory”

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

History And Theory loads about 1.9k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 810 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

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). 810 words, ~1,860 tokens.

Download SKILL.mdSave it as .claude/skills/history-and-theory/SKILL.md (or your agent's skills folder).
name
history-and-theory
description
Use when targeting History and Theory or deciding whether a philosophy-of-history, historiography, or historical-method manuscript fits this venue. Encodes the journal's meta-level theoretical bar, its historiographical and conceptual expectations, house style and double-blind norms, official-submission re-check, and desk-reject heuristics.

History and Theory (history-and-theory)

Journal positioning

History and Theory, published for Wesleyan University (Wiley), is the leading venue for the philosophy of history, historical theory, historiography, and the epistemology and method of history. It is a meta-level journal: its object is not the past itself but historical thinking — how historians explain, narrate, periodize, represent, and justify claims about the past, and what concepts and methods underwrite that practice. Its defining expectation is an original theoretical or methodological argument that advances debate about historical knowledge, engaging the relevant theoretical literature with philosophical care. A straightforward archival case study with no theoretical or methodological stake is a misfit here, however accomplished as empirical history. 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 History and Theory author instructions and style guide.

When to trigger

  • The author names History and Theory for a work on philosophy of history, historiography, or historical method and wants a fit/framing check.
  • An empirical project contains a genuine theoretical or methodological argument that could be extracted and developed for a meta-level venue.
  • The author is choosing between History and Theory and an empirical history journal or a philosophy journal.
  • The author needs the journal's theory-level bar and desk-reject heuristics.

Scope & topic fit

  • Philosophy of history: historical explanation, causation, contingency, counterfactuals, and the logic of historical inference.
  • Theory of historiography: narrative, representation, the rhetoric of historical writing, and the status of historical truth and objectivity.
  • Epistemology and method: evidence, testimony, the archive, periodization, scale, and comparison as conceptual problems.
  • Critical and reflexive historiography: memory, temporality, the politics of the past, and debates over the discipline's foundations and futures.
  • Conceptual histories of the field's key terms and the theoretical commitments embedded in historical practice.
  • Engagement with theory from philosophy, social theory, and adjacent fields when it illuminates how history is done and justified.

Method & evidence bar

  • The contribution is an original theoretical or methodological argument about historical knowledge; state the thesis and its stake for historical practice clearly.
  • The argument is conceptually rigorous: distinctions are drawn precisely, key terms defined, the reasoning followed through, and the meta-level thesis earned by argument rather than merely asserted.
  • Historiographical positioning is explicit: which theoretical debate the piece enters and how it advances or revises it.
  • Where historical examples appear, they do genuine argumentative work — illustrating or testing the theoretical claim, not standing in for it.
  • Engagement with the relevant theoretical literature (in philosophy of history and adjacent theory) is current, fair, and non-padding.

Structure & house style

  • Long-form scholarly article sustaining a theoretical argument; defer exact word limits and article types (articles, review essays where offered) to the live guide.
  • Chicago notes-and-bibliography style with full footnotes; footnotes carry qualification and secondary dialectic.
  • Double-blind review: anonymize the manuscript — self-identifying citations and acknowledgements — per current policy.
  • Prose is precise and economical; technical or philosophical apparatus is used only where it earns its keep, and non-English theory is quoted and translated per policy.
  • Any historical illustrations or figures, where used, follow the journal's permissions and specification requirements.
Show full SKILL.md (297 more words)Show less

Official-submission checklist

  • Before giving submission-ready advice, read ../../resources/source-basis.md and ../../resources/official-source-map.md; start from the Wesleyan / Wiley anchors, then cite the current History and Theory page you checked.
  • Search the live site for "History and Theory submission guidelines" and follow the current version.
  • Re-check article types (articles, review essays), word limits, the Chicago footnote form, and the abstract requirement.
  • Confirm anonymization requirements for double-blind review.
  • Re-check the translation policy for non-English theoretical sources and any image permissions.
  • Re-check competing-interest, funding (if applicable), prior-presentation/preprint, and AI-use disclosure, and any open-access terms.
  • If the live official instructions conflict with this skill, the official instructions win.

Pre-submission self-check

  • There is a clearly stated, original theoretical or methodological thesis about historical knowledge.
  • The argument is conceptually rigorous — distinctions drawn, key terms defined, reasoning followed through.
  • The theoretical debate the piece enters and how it advances it are named explicitly.
  • Any historical examples do argumentative work and do not substitute for the argument.
  • Engagement with the theoretical literature is current, fair, and non-padding.
  • The manuscript is anonymized and follows Chicago footnotes and any abstract requirement.

Common desk-reject triggers

  • A straightforward archival case study with no theoretical or methodological argument.
  • A theoretical claim asserted but not argued, terms left undefined and distinctions blurred, or no explicit positioning in the philosophy-of-history / historiography debate addressed.
  • Historical illustration that carries the piece in place of a conceptual argument.
  • Engagement with theory that is dated, unfair, or padded rather than load-bearing.
  • Wrong venue: empirical history better suited to a substantive history journal, or pure philosophy better suited to a philosophy journal.

Re-routing decision

  • Empirical study with discipline-wide significance → the-american-historical-review.
  • Problem-driven social/economic/cultural history → past-and-present.
  • Modern European archival study with broad significance → the-journal-of-modern-history.
  • British or wide-ranging empirical study → the-english-historical-review.
  • Representation, memory, or cultural-theory emphasis with a literary axis → representations.

Output format

text
[Fit] High / Medium / Low (one-line reason)
[Target] History and Theory
[Field/period/region] <theoretical area — e.g. explanation, narrative, method>
[Argument] <the theoretical/methodological thesis in one line>
[Sources/historiography] <does the conceptual rigor + positioning clear the meta-level bar?>
[Top risk] <the single most likely reason for rejection>
[Official items to re-check] <word limit / Chicago style / anonymization / translation / preprint policy>
[Re-route suggestion] <if not a fit, 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/history-and-theory of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

History And Theory 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.

History And Theory compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
History And Theory this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.9kAutomated safety check: PassMIT
Design Philosophysickn33/agentic-awesome-skills47k1 repos~699Automated safety check: PassMIT
Historyalsk1992/CloddsBot3k—~1.6kAutomated safety check: PassMIT
Touch Targetsthedaviddias/Front-End-Checklist74k—~938Automated safety check: PassMIT
Integration Theoryparcadei/Continuous-Claude-v33.9k1 repos~929Automated safety check: NotesMIT
Extracting Browser History Artifactsmukul975/Anthropic-Cybersecurity-Skills34k—~2.9kAutomated safety check: WarnApache-2.0

Similar skills

  • Design Philosophy

    sickn33/agentic-awesome-skills

    Visual philosophy and art-direction for frontend. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 1 repo~699 tokens
    Frontend & DesignAuto-check passed
  • History

    alsk1992/CloddsBot

    Trade history tracking, sync, and performance analytics. An agent skill from alsk1992/CloddsBot.

    3k GitHub stars~1.6k tokensUpdated 8 days ago
    Auto-check passed
  • Touch Targets

    thedaviddias/Front-End-Checklist

    A skill your agent uses when applies to all interactive elements on touchscreen interfaces: buttons, links, checkboxes, radio buttons, form inputs, icon buttons, and menu items.

    74k GitHub stars~938 tokensUpdated 5 days ago
    MobileAuto-check passed
  • Integration Theory

    parcadei/Continuous-Claude-v3

    Problem-solving strategies for integration theory in measure theory

    3.9k GitHub starsUsed in 1 repo~929 tokens
    Research & ScienceAuto-check: notes
  • Extracting Browser History Artifacts

    mukul975/Anthropic-Cybersecurity-Skills

    Extracts and analyzes browser history, cookies, cache, downloads, and bookmarks from Chrome, Firefox, and Edge using sqlite3, DB Browser for SQLite, Hindsight, and NirSoft tools…

    34k GitHub stars~2.9k tokensUpdated 1 mo ago
    SecurityAuto-check: warnings
  • System History

    BuilderIO/agent-native

    Blobless-safe git and PR history for this repo. An agent skill from BuilderIO/agent-native.

    7.1k GitHub stars~727 tokensUpdated today
    DevelopmentAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo
  • Aaag 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed

Questions about History And Theory

What does History And Theory do?

A skill your agent uses when targeting History and Theory or deciding whether a philosophy-of-history, historiography, or historical-method manuscript fits this venue. History And Theory is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting History and Theory or deciding whether a philosophy-of-history, historiography, or historical-method manuscript fits this venue.

When should I use History And Theory?

History And Theory fits situations like: targeting History and Theory; deciding whether a philosophy-of-history; historical-method manuscript fits this venue.

How do I install History And Theory in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill history-and-theory -a claude-code`. Or copy the skill folder (English-Humanities-Journal-Skills/skills/history-and-theory in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/history-and-theory in your project. Claude Code loads it when a task matches its description.

How do I install History And Theory in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill history-and-theory -a codex`. Or copy the skill folder (English-Humanities-Journal-Skills/skills/history-and-theory in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/history-and-theory in your project. Codex loads it when a task matches its description.

Can I use History And Theory 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 history-and-theory -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/history-and-theory, .gemini/skills/history-and-theory, .github/skills/history-and-theory and .opencode/skills/history-and-theory in your project.

What does History And Theory need to run?

SKILL.md names no scripts, command-line tools or credentials: History And Theory is instructions for the agent only.

Does History And Theory 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 History And Theory 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 History And Theory use?

History And Theory 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 History And Theory use?

About 1.9k tokens (SKILL.md is roughly 7.4k 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 History And Theory?

Skills that share tags, products or a category with History And Theory: Design Philosophy (sickn33/agentic-awesome-skills, 47k stars), History (alsk1992/CloddsBot, 3k stars), Touch Targets (thedaviddias/Front-End-Checklist, 74k stars) and Integration Theory (parcadei/Continuous-Claude-v3, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains History And Theory?

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.