History
alsk1992/CloddsBot
Trade history tracking, sync, and performance analytics. An agent skill from alsk1992/CloddsBot.
A skill your agent uses when targeting New Literary History or deciding whether an essay on the theory, history, and method of literary study fits this venue.
MITAuto-check passed
Install New Literary History
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill new-literary-history -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills new-literary-history --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/new-literary-history .claude/skills/new-literary-history && 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 "new-literary-history" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/new-literary-history into .claude/skills/new-literary-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-literary-history", 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/new-literary-historyType 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 new-literary-history -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills new-literary-history --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/new-literary-history .agents/skills/new-literary-history && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "new-literary-history" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/new-literary-history into .agents/skills/new-literary-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-literary-history", 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 new-literary-history -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills new-literary-history --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/new-literary-history .cursor/skills/new-literary-history && 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 "new-literary-history" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/new-literary-history into .cursor/skills/new-literary-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-literary-history", 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/new-literary-history--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 new-literary-history -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills new-literary-history --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/new-literary-history .gemini/skills/new-literary-history && 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 "new-literary-history" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/new-literary-history into .gemini/skills/new-literary-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-literary-history", 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 new-literary-historyInstalls 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 new-literary-history -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/new-literary-history .github/skills/new-literary-history && 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 "new-literary-history" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/new-literary-history into .github/skills/new-literary-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-literary-history", 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 new-literary-history -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 new-literary-history --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/new-literary-history .opencode/skills/new-literary-history && 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 "new-literary-history" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/English-Humanities-Journal-Skills/skills/new-literary-history into .opencode/skills/new-literary-history/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "new-literary-history", 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
new-literary-history- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 769 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when targeting New Literary History or deciding whether an essay on the theory, history, and method of literary study fits this venue.
- Targeting New Literary History
- 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 an essay on the theory
What it does
New Literary History is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting New Literary History or deciding whether an essay on the theory, history, and method of literary study fits this venue. Encodes the journal's theory-of-literature fit, the conceptual-question bar, methodological-reflexivity expectations, 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 New Literary History
- Deciding whether an essay on the theory
- Method of literary study fits this venue
Example prompts
- “/new-literary-history”
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
New Literary History loads about 1.7k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 769 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). 769 words, ~1,702 tokens.
Download SKILL.mdSave it as
.claude/skills/new-literary-history/SKILL.md (or your agent's skills folder).- name
- new-literary-history
- description
- Use when targeting New Literary History or deciding whether an essay on the theory, history, and method of literary study fits this venue. Encodes the journal's theory-of-literature fit, the conceptual-question bar, methodological-reflexivity expectations, house style and double-blind norms, official-submission re-check, and desk-reject heuristics.
New Literary History (new-literary-history)
Journal positioning
New Literary History, published by Johns Hopkins University Press, is devoted to theory and interpretation — to questions about the nature, method, and history of literary study rather than to readings for their own sake. Its defining expectation is an essay that asks a genuine theoretical or methodological question: what literature is, how it means, why we read it as we do, how categories like period, genre, value, or interpretation are constituted and might be rethought. A close reading without a conceptual question behind it, or a survey of a critical school, is a poor fit; the journal wants reflection that reorients how the discipline thinks. 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 New Literary History author instructions.
When to trigger
- The author names New Literary History for an essay on literary theory, method, or history and wants a fit/framing check.
- A reading-driven piece must be re-framed around the theoretical or methodological question it implicitly raises.
- The author is choosing between New Literary History and a high-theory or close-reading venue.
- The author needs the journal's theory-of-literature bar and desk-reject heuristics.
Scope & topic fit
- Theory of literature and interpretation: meaning, reading, value, genre, periodization, canon, and the concept of "literature" itself.
- Reflection on critical methods and their histories — how schools, paradigms, and protocols of reading arise and change.
- Conceptual essays drawing on philosophy, history of ideas, cognitive science, or the social sciences to rethink literary categories.
- Histories of criticism and theory that bear on present method, not antiquarian for its own sake.
- Cross-traditional and comparative reflection when the payoff is a rethought general category.
- Essays that propose a new way of posing a literary-theoretical problem.
Method & evidence bar
- The contribution is an original conceptual or methodological argument; the essay is driven by a question about literary study, not by a single text's reading.
- Theoretical and historicist resources are marshaled rigorously to reframe a category or method.
- Where texts are read, the reading exemplifies or tests the conceptual claim rather than standing as the end in itself.
- The essay engages the relevant theoretical and critical literature precisely, situating its question in an ongoing conversation.
- Argumentation is conceptually careful: distinctions are drawn, terms clarified, consequences traced.
- Claims about "what literary study does" are supported, not merely proclaimed.
Structure & house style
- Reflective scholarly essay organized around a theoretical question; re-check current length expectations and essay types on the live guide.
- The governing question and its stakes are posed early; the essay develops a sustained line of conceptual argument.
- Citation follows the journal's current humanities style; notes carry qualification and secondary debate.
- Double-blind review: anonymize the manuscript (self-citations and acknowledgements) per current policy.
- Non-English quotations are given with translations per policy; any reproduced material requires permissions.
- Prose is conceptually precise and addressed to readers across literary fields, not to one specialty.
Show full SKILL.md (283 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 JHU Press anchors, then cite the current New Literary History page you checked. - Search the live site for "New Literary History submission guidelines" and follow the current version.
- Re-check essay types, length expectations, and the abstract requirement.
- Confirm the citation/style format and anonymization for double-blind review.
- Re-check the translation policy for non-English quotation and any permissions.
- Re-check prior-presentation/preprint, simultaneous-submission, and AI-use disclosure policies.
- If the live official instructions conflict with this skill, the official instructions win.
Pre-submission self-check
- The essay is driven by a genuine theoretical or methodological question about literary study.
- The conceptual argument reframes a category or method rather than just reading a text.
- Any close reading exemplifies or tests the concept rather than standing as the goal.
- The question is situated precisely in the relevant theoretical and critical literature.
- Distinctions are drawn, terms clarified, and consequences for the discipline traced.
- The manuscript is anonymized, follows current style, and has translations/permissions in hand.
Common desk-reject triggers
- A close reading with no conceptual or methodological question behind it.
- A descriptive survey of a critical school with no original theoretical claim.
- Theory invoked as label rather than argued to reframe a category or method.
- A "rethinking" announced but with no distinctions drawn or consequences traced.
- No engagement with the relevant theoretical conversation the essay claims to enter.
- Wrong venue: a reading or interpretation better suited to a broad or specialist literary journal.
Re-routing decision
- Broad-readership interpretive essay →
pmla. - Agenda-setting theory across the arts and humanities generally →
critical-inquiry. - New-historicist, archive-grounded analysis →
representations. - Historically grounded account of literary change rather than theory of method →
modern-language-quarterly. - Cross-linguistic or world-literature framing →
comparative-literature.
Output format
[Fit] High / Medium / Low (one-line reason)
[Target] New Literary History
[Question] <the theoretical/methodological question in one line>
[Category at stake] <which literary concept or method is being rethought>
[Theoretical idiom] <does the conceptual argument reframe the category and clear the theory-of-literature bar?>
[Top risk] <the single most likely reason for rejection>
[Official items to re-check] <length / citation style / anonymization / translations / permissions>
[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/new-literary-history of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
New Literary History 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 |
|---|---|---|---|---|---|---|
| New Literary History this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Historyalsk1992/CloddsBot | 3k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Touch Targetsthedaviddias/Front-End-Checklist | 74k | — | ~938 | Automated safety check: Pass | MIT | |
| Extracting Browser History Artifactsmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.9k | Automated safety check: Warn | Apache-2.0 | |
| System HistoryBuilderIO/agent-native | 7.1k | — | ~727 | Automated safety check: Pass | None | |
| Git History Analyzerudecode/plate | 17k | — | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
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.
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…
System History
BuilderIO/agent-native
Blobless-safe git and PR history for this repo. An agent skill from BuilderIO/agent-native.
Git History Analyzer
udecode/plate
Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist.
Implementing Mimecast Targeted Attack Protection
mukul975/Anthropic-Cybersecurity-Skills
Deploys and configures Mimecast Targeted Threat Protection (TTP) modules -- URL Protect (click-time URL rewriting/analysis), Attachment Protect (sandbox detonation), Impersonation Protect…
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 New Literary History
What does New Literary History do?
A skill your agent uses when targeting New Literary History or deciding whether an essay on the theory, history, and method of literary study fits this venue. New Literary History is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting New Literary History or deciding whether an essay on the theory, history, and method of literary study fits this venue.
When should I use New Literary History?
New Literary History fits situations like: targeting New Literary History; deciding whether an essay on the theory; method of literary study fits this venue.
How do I install New Literary History in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill new-literary-history -a claude-code`. Or copy the skill folder (English-Humanities-Journal-Skills/skills/new-literary-history in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/new-literary-history in your project. Claude Code loads it when a task matches its description.
How do I install New Literary History in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill new-literary-history -a codex`. Or copy the skill folder (English-Humanities-Journal-Skills/skills/new-literary-history in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/new-literary-history in your project. Codex loads it when a task matches its description.
Can I use New Literary History 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 new-literary-history -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/new-literary-history, .gemini/skills/new-literary-history, .github/skills/new-literary-history and .opencode/skills/new-literary-history in your project.
What does New Literary History need to run?
SKILL.md names no scripts, command-line tools or credentials: New Literary History is instructions for the agent only.
Does New Literary History 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 New Literary History 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 New Literary History use?
New Literary History 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 New Literary History use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 New Literary History?
Skills that share tags, products or a category with New Literary History: History (alsk1992/CloddsBot, 3k stars), Touch Targets (thedaviddias/Front-End-Checklist, 74k stars), Extracting Browser History Artifacts (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and System History (BuilderIO/agent-native, 7.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains New Literary History?
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.