Right To Erasure
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing account settings pages, privacy dashboards, or API routes to verify that a complete data deletion path exists for users.
A skill your agent uses when deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management or economics-of-IS problem, not a…
MITAuto-check passed
Install Jmis Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-topic-selection --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/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection .claude/skills/jmis-topic-selection && 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 "jmis-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection into .claude/skills/jmis-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-topic-selection", 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/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selectionType 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 jmis-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-topic-selection --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/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection .agents/skills/jmis-topic-selection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jmis-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection into .agents/skills/jmis-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-topic-selection", 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 jmis-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-topic-selection --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/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection .cursor/skills/jmis-topic-selection && 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 "jmis-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection into .cursor/skills/jmis-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-topic-selection", 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 Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection--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 jmis-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-topic-selection --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/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection .gemini/skills/jmis-topic-selection && 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 "jmis-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection into .gemini/skills/jmis-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-topic-selection", 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 jmis-topic-selectionInstalls 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 jmis-topic-selection -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/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection .github/skills/jmis-topic-selection && 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 "jmis-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection into .github/skills/jmis-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-topic-selection", 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 jmis-topic-selection -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 jmis-topic-selection --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/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection .opencode/skills/jmis-topic-selection && 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 "jmis-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection into .opencode/skills/jmis-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-topic-selection", 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
jmis-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~2.2k tokens
- SKILL.md length
- 1,173 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management or economics-of-IS problem, not a…
- Works in 3 steps: The IS-management hinge. Does the answer… → The economics-of-IS angle. JMIS (Zwass's… → Generalizable beyond one system. The…
- Deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management
- SKILL.md covers When to trigger, What makes a question…, Decision table: route by what… and JMIS vs. its neighbors at the…, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Jmis Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management or economics-of-IS problem, not a generic tech study or a pure CS contribution. Pressure-tests fit and outlet choice before theory work begins; it does not build the mechanism (jmis-theory-development).
Its SKILL.md is about 2.2k 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
- Deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management
- Economics-of-IS problem
- Not a generic tech study
- A pure CS contribution
Example prompts
- “/jmis-topic-selection”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- The IS-management hinge. Does the answer change how a manager, firm, platform, or policymaker should act on technology? "We predict churn…
- The economics-of-IS angle. JMIS (Zwass's IJEC lineage) is unusually receptive to IT economics, e-commerce, digital platforms, network…
- Generalizable beyond one system. The insight should travel past the specific artifact or firm to a class of IS phenomena.
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
Jmis Topic Selection loads about 2.2k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 1,173 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). 1,173 words, ~2,247 tokens.
Download SKILL.mdSave it as
.claude/skills/jmis-topic-selection/SKILL.md (or your agent's skills folder).- name
- jmis-topic-selection
- description
- Use when deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management or economics-of-IS problem, not a generic tech study or a pure CS contribution. Pressure-tests fit and outlet choice before theory work begins; it does not build the mechanism (jmis-theory-development).
Topic Selection (jmis-topic-selection)
When to trigger
- You have an IS/technology phenomenon but cannot say what managerial or economic question it answers
- The work might be a better fit for MISQ, ISR, JAIS, Management Science, or a CS venue and you need to decide before investing in theory
- A reviewer or colleague says "this is a technical exercise" or "where is the management contribution?"
- The dataset (platform logs, firm IT spend, e-commerce transactions, security incidents) is rich but the question is not yet sharp
What makes a question JMIS-shaped
JMIS rewards questions at the technology–organization–economics nexus: how information systems and technology are managed, valued, and governed, and how they reshape firms, markets, and platforms. The strongest JMIS topics make the technology load-bearing in an economic or managerial mechanism — not a backdrop. Use these tests:
- The IS-management hinge. Does the answer change how a manager, firm, platform, or policymaker should act on technology? "We predict churn with a new model" is CS; "we show how a recommender's design shifts platform-side seller competition and revenue" is JMIS.
- The economics-of-IS angle. JMIS (Zwass's IJEC lineage) is unusually receptive to IT economics, e-commerce, digital platforms, network effects, IT business value, and the economics of security/privacy. If your question has incentives, information, matching, or value at its core, it fits.
- Generalizable beyond one system. The insight should travel past the specific artifact or firm to a class of IS phenomena.
Decision table: route by what the question is really about
| Your question is really about… | Strong JMIS fit if… | Reroute / risk |
|---|---|---|
| IT investment and firm performance | identification of IT's causal value, not just correlation with spend | pure finance → a finance journal |
| a digital platform / marketplace | network effects, two-sidedness, governance, or pricing are theorized | descriptive platform stats → weak fit |
| IS adoption / use / behavior | a technology-specific behavioral mechanism, validated | generic TAM replication → desk-reject risk |
| a built artifact / ML system | managerial utility evaluated vs. real baselines, design knowledge generalized | algorithm-only novelty → a CS venue |
| security / privacy | the economics or management of risk, disclosure, breaches | a crypto/protocol result → a security venue |
| a policy / governance change | the IT-mediated effect on firms or markets is the point | a pure econ result with IS as setting → econ journal |
JMIS vs. its neighbors at the topic stage
- vs. MISQ — MISQ leans into design-science and theory-method pluralism; JMIS leans into management/economics of IS. If the contribution is a design theory, MISQ may fit better.
- vs. ISR — ISR prizes sociotechnical, intradisciplinary, silo-bridging work and analytical models as co-equal. If your edge is bridging behavioral and economic paradigms, weigh ISR.
- vs. Management Science (IS dept.) — broader OR/management generality; JMIS wants the IS audience and an IS-specific takeaway.
- vs. a CS / data-mining venue — if removing the management/economics framing loses nothing, the paper is not JMIS-shaped.
Worked vignette: from a dataset to a JMIS question (illustrative)
A team has clickstream and seller data from a marketplace and a draft titled "Predicting which sellers churn." As written it is a churn-prediction paper — a CS/data-mining contribution. The JMIS-shaped version asks an economic-of-platforms question: does the platform's algorithmic ranking redesign cause marginal sellers to exit, and does that shrink buyer-side variety and platform revenue? Now the technology (the ranking algorithm) is load-bearing, there is an identifying event (the redesign), and the takeaway is managerial (how aggressively to personalize ranking trades off short-run match quality against long-run seller supply). Same data, JMIS-grade question.
Pre-commit the fit decision before theory work
Topic selection is also an outlet decision, and it is cheaper to make now than after a desk return. Write the single sentence, then ask three coauthor-style questions: Who on the JMIS board would champion this? Which reviewer would say "wrong journal"? If a reviewer says "this is really a MISQ/ISR/econ paper," can I answer in one sentence? If you cannot, the fit is borderline and you should resolve it — by sharpening the management/economics angle or by rerouting — before investing in jmis-theory-development.
Checklist
- The one-sentence question names the technology and the managerial/economic stake
- Removing the IT artifact would break the contribution (technology is load-bearing)
- The economics-of-IS or IT-value angle is explicit where the phenomenon supports it
- You can name the JMIS audience segment that cares and the one that would desk-reject
- Fit vs. MISQ/ISR/JAIS/Management Science is argued, not assumed
- The insight generalizes beyond the single system, firm, or dataset
- The question passes the deletion, audience, and decision tests
- The phenomenon maps onto a JMIS-rewarded area (IT value, platforms, e-commerce, security/privacy economics, analytics)
Show full SKILL.md (431 more words)Show less
Topics JMIS has historically rewarded
JMIS's identity — shaped by Vladimir Zwass's long editorship and his parallel work on electronic commerce — leans toward the management and economics of IS. Questions that sit squarely in its wheelhouse: the business value and complementarities of IT and emerging tech (now including AI/analytics); the design, governance, and competition of digital platforms and marketplaces; e-commerce and digital channels; the economics of information security and privacy; decision support and business analytics in real managerial settings; and the organizational and market impacts of new technology. A topic that maps cleanly onto one of these — with the technology load-bearing — starts with the wind at its back; one that only borrows an IS setting to make a reference-discipline point starts behind.
Anti-patterns
- A technically strong model with no managerial or economic question — reads as a CS paper in IS clothing
- A generic technology-adoption replication with no IS-specific mechanism
- Treating the IT artifact as an interchangeable "treatment" or setting
- Picking JMIS only because it is T&F and easy to email, when MISQ/ISR is the natural home
- Inventing an exemplar JMIS paper to justify fit instead of verifying it in the archive
- Choosing the topic for data availability alone, with no managerial or economic question attached
- A purely descriptive "we characterize X" framing with no decision it would change
Stress-test the scope before you commit
Three quick tests separate a JMIS topic from a near-miss. The deletion test: remove the IT artifact from the question — if it still makes sense, the technology was a setting, not the subject, and the paper is probably not IS. The audience test: picture the JMIS readership (IS scholars who study the management and economics of technology) — can you name the subset who would cite this and the subset who would shrug? If you cannot name either, the topic is too diffuse. The decision test: does answering the question change a real technology decision (invest, govern, price, design, disclose)? JMIS's management identity rewards a question whose answer a manager or platform could act on; a purely descriptive "we characterize X" topic, however novel, sits closer to the journal's margin.
Hand off only when fit is settled
Do not route to jmis-theory-development while the fit verdict is still "borderline." A topic that is unsure of its home wastes theory and analysis effort, because a reframe at the contribution stage often forces the mechanism to be rebuilt. Resolve the fit first — sharpen the management/economics angle until the deletion, audience, and decision tests all pass, or reroute honestly to the sibling that fits — and only then commit downstream work.
Output format
【Journal】Journal of Management Information Systems (JMIS)
【One-sentence question】technology + managerial/economic stake
【IS-management hinge】who acts differently and how
【Economics-of-IS angle】incentives / value / platform / security economics (or n/a)
【Fit verdict】strong / borderline / reroute → which sibling
【Next skill】jmis-theory-development© 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 Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jmis Topic Selection 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 |
|---|---|---|---|---|---|---|
| Jmis Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Right To Erasurethedaviddias/Front-End-Checklist | 74k | — | ~512 | Automated safety check: Pass | MIT | |
| TopicsZimoLiao/scholaraio | 577 | — | ~294 | Automated safety check: Pass | MIT | |
| Topic Modelingbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Add Shape Inferenceonnx/onnx | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Five Questionsbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~1.7k | Automated safety check: Notes | Custom licence |
Similar skills
Topics
ZimoLiao/scholaraio
A skill your agent uses when the user asks about research themes, topic distribution, BERTopic clustering, topic overview, topic papers, topic merges, or HTML topic visualizations.
Topic Modeling
brycewang-stanford/Auto-Empirical-Research-Skills
Structural topic modeling: STM spec, topic count, coherence-exclusivity.
Add Shape Inference
onnx/onnx
Add or update type and shape inference for an ONNX operator.
Five Questions
brycewang-stanford/Auto-Empirical-Research-Skills
Deeply analyze any empirical economics PDF using the five-question framework (五问框架): research question, identification strategy, core estimand, robustness logic, and scholarly contribution.
Bestblogs Topic
ginobefun/BestBlogs
A skill your agent uses when the user asks about a specific topic, subject area, or wants to explore curated topic pages on BestBlogs.
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 Jmis Topic Selection
What does Jmis Topic Selection do?
A skill your agent uses when deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management or economics-of-IS problem, not a…. Jmis Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management or economics-of-IS problem, not a generic tech study or a pure CS contribution.
When should I use Jmis Topic Selection?
Jmis Topic Selection fits situations like: deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management; economics-of-IS problem; not a generic tech study; A pure CS contribution.
How do I install Jmis Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-topic-selection -a claude-code`. Or copy the skill folder (Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jmis-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Jmis Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-topic-selection -a codex`. Or copy the skill folder (Journal-of-Management-Information-Systems-Skills/skills/jmis-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jmis-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Jmis Topic Selection 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 jmis-topic-selection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jmis-topic-selection, .gemini/skills/jmis-topic-selection, .github/skills/jmis-topic-selection and .opencode/skills/jmis-topic-selection in your project.
What does Jmis Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Jmis Topic Selection is instructions for the agent only.
Does Jmis Topic Selection 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 Jmis Topic Selection 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 Jmis Topic Selection use?
Jmis Topic Selection 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 Jmis Topic Selection use?
About 2.2k tokens (SKILL.md is roughly 9k 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 Jmis Topic Selection?
Skills that share tags, products or a category with Jmis Topic Selection: Right To Erasure (thedaviddias/Front-End-Checklist, 74k stars), Topics (ZimoLiao/scholaraio, 577 stars), Topic Modeling (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars) and Add Shape Inference (onnx/onnx, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jmis Topic Selection?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.