Marketing Os
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
Agent skill
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when staking a Journal of Management Information Systems (JMIS) manuscript's contribution against the IS literature and the basket siblings — showing it advances an…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-literature-positioning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-literature-positioning --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-literature-positioning .claude/skills/jmis-literature-positioning && 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-literature-positioning" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-literature-positioning into .claude/skills/jmis-literature-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-literature-positioning", 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-literature-positioningType 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-literature-positioning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-literature-positioning --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-literature-positioning .agents/skills/jmis-literature-positioning && 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-literature-positioning" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-literature-positioning into .agents/skills/jmis-literature-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-literature-positioning", 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-literature-positioning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-literature-positioning --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-literature-positioning .cursor/skills/jmis-literature-positioning && 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-literature-positioning" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-literature-positioning into .cursor/skills/jmis-literature-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-literature-positioning", 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-literature-positioning--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-literature-positioning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-literature-positioning --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-literature-positioning .gemini/skills/jmis-literature-positioning && 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-literature-positioning" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-literature-positioning into .gemini/skills/jmis-literature-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-literature-positioning", 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-literature-positioningInstalls 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-literature-positioning -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-literature-positioning .github/skills/jmis-literature-positioning && 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-literature-positioning" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-literature-positioning into .github/skills/jmis-literature-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-literature-positioning", 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-literature-positioning -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-literature-positioning --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-literature-positioning .opencode/skills/jmis-literature-positioning && 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-literature-positioning" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-literature-positioning into .opencode/skills/jmis-literature-positioning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-literature-positioning", 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.
jmis-literature-positioningA skill your agent uses when staking a Journal of Management Information Systems (JMIS) manuscript's contribution against the IS literature and the basket siblings — showing it advances an…
Jmis Literature Positioning is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when staking a Journal of Management Information Systems (JMIS) manuscript's contribution against the IS literature and the basket siblings — showing it advances an IS-management/economics conversation rather than only a reference discipline. Positions the work; it does not build the mechanism (jmis-theory-development) or write the contribution statement (jmis-contribution-framing).
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Positioning and messaging. 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.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Jmis Literature Positioning loads about 2.1k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 1,142 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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 1,142 words, ~2,141 tokens.
.claude/skills/jmis-literature-positioning/SKILL.md (or your agent's skills folder).JMIS is an IS journal, so the literature you must engage first is the IS literature — IT business value, digital platforms, e-commerce, IS economics, security/privacy, decision support/analytics — even when your toolkit comes from economics or computer science. The test a JMIS reviewer applies: what did the IS field believe, and how does this paper move that belief? Borrowing a reference-discipline method is fine; positioning the contribution only in the reference discipline is a desk-reject signal because the IS audience cannot see the advance.
JMIS reviewers expect you to know the IS basket. Engage prior JMIS, MISQ, ISR, and JAIS work on your phenomenon — not just econ/CS papers. Failing to cite the closest IS predecessors (especially prior JMIS papers on the same platform/value/security question) reads as not knowing the field. Where your evidence comes from a reference discipline, cite that frontier too, but subordinate it to the IS contribution.
| If a reviewer says… | Reposition by… |
|---|---|
| "This belongs in MISQ as a design-science paper" | Foregrounding the managerial/economic value question, not the artifact build |
| "This is an economics paper with an IS label" | Showing the IT artifact is essential to the mechanism and the takeaway is for IS practice |
| "This is single-paradigm; try ISR" | Either embracing JMIS's clean management/economics framing or, if the edge is silo-bridging, considering ISR honestly |
| "This is just a better algorithm" | Reframing around managerial utility and IS decision-making, or rerouting to a CS venue |
A privacy paper opens: "Little is known about how breach disclosure laws affect firms." That is an absence, and a JMIS reviewer will read it as under-positioned. Reframed as a tension: the security-economics literature argues mandatory disclosure disciplines firms into investing more in protection [signaling/deterrence], yet the disclosure literature implies it can trigger reputational over-reaction and under-reporting; we identify which force dominates and for whom. Now the gap is a live debate the IS field can place, the contribution is a resolution rather than a first look, and the closest IS predecessors (prior JMIS/MISQ security-economics papers) become the conversation you advance rather than a citation pile.
JMIS reviewers notice when a paper engages the IS basket generically but skips the JMIS lineage on its own topic. If you write on platforms, e-commerce, IT value, or security/privacy economics, the journal has published streams on exactly those questions; engaging them signals you are joining JMIS's conversation, not just any IS conversation. This is also where the management/economics cut matters: position against the IT-value, platform-economics, or security-economics literatures (JMIS's home turf) rather than only against design-science or pure-behavioral streams, which read as a better fit for MISQ. The strongest front ends make the reader feel the paper was written for JMIS, not retrofitted to it.
A JMIS introduction's positioning usually resolves into three paragraphs. (1) The phenomenon and stake — a concrete IT/management development and why managers, firms, or platforms care. (2) The IS conversation and its tension — the specific stream you join, what it currently holds, and the contradiction or unresolved question (theory vs. evidence, or stream A vs. stream B) that your paper targets. (3) The delta and approach — what the field believed, what it should believe after your paper, and the leverage (identification, model, or evaluation) that lets you claim it. Reference-discipline tools appear in paragraph three as the method, never as the contribution. If a paragraph cannot be written because the stream, the tension, or the delta is missing, that is the gap to close before drafting further.
Resist the urge to inflate the gap. A reviewer who knows the literature will catch a "no one has studied this" claim that ignores a near-identical prior paper, and the credibility cost is high. State precisely what prior work established and where it stopped, then claim only the increment you actually deliver. Honest, well-bounded positioning that names the closest predecessor and the exact delta reads as command of the field; overstated novelty reads as not having done the reading.
【IS stream joined】name + current frontier belief
【Gap as tension】stream A vs. stream B (or theory vs. evidence)
【Delta】field believed X → should believe Y
【Closest IS predecessors】incl. prior JMIS work
【Sibling boundary handled】why JMIS not MISQ/ISR/MS
【Next step】jmis-methods© 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
Just SKILL.md in Journal-of-Management-Information-Systems-Skills/skills/jmis-literature-positioning of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Jmis Literature Positioning 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 Literature Positioning this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Marketing OsYuzzyuk/marketing-os | 540 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Startup Positioningferdinandobons/startup-skill | 1.2k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Stanley Druckenmiller Investmenttradermonty/claude-trading-skills | 3k | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| B2b Playbookweilun88313/B2B-Playbook | 203 | — | ~3.1k | Automated safety check: Pass | Proprietary |
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
ferdinandobons/startup-skill
Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test.
tradermonty/claude-trading-skills
Druckenmiller Strategy Synthesizer - Integrates 8 upstream skill outputs (Market Breadth, Uptrend Analysis, Market Top, Macro Regime, FTD Detector, VCP Screener, Theme Detector, CANSLIM Screener)…
weilun88313/B2B-Playbook
Turn B2B marketing work into evidence-aware outputs using market, positioning, demand, account-program, lifecycle, and tool-selection guidance.
onvoyage-ai/gtm-engineer-skills
Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging.
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…
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…
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…
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…
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…
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…
Categories
A skill your agent uses when staking a Journal of Management Information Systems (JMIS) manuscript's contribution against the IS literature and the basket siblings — showing it advances an…. Jmis Literature Positioning is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when staking a Journal of Management Information Systems (JMIS) manuscript's contribution against the IS literature and the basket siblings — showing it advances an IS-management/economics conversation rather than only a reference discipline.
Jmis Literature Positioning fits situations like: tasks that involve Positioning and messaging.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-literature-positioning -a claude-code`. Or copy the skill folder (Journal-of-Management-Information-Systems-Skills/skills/jmis-literature-positioning in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jmis-literature-positioning in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-literature-positioning -a codex`. Or copy the skill folder (Journal-of-Management-Information-Systems-Skills/skills/jmis-literature-positioning in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jmis-literature-positioning in your project. Codex loads it when a task matches its description.
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-literature-positioning -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-literature-positioning, .gemini/skills/jmis-literature-positioning, .github/skills/jmis-literature-positioning and .opencode/skills/jmis-literature-positioning in your project.
SKILL.md names no scripts, command-line tools or credentials: Jmis Literature Positioning is instructions for the agent only.
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.
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.
Jmis Literature Positioning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.1k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Jmis Literature Positioning: Marketing Os (Yuzzyuk/marketing-os, 540 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Positioning (ferdinandobons/startup-skill, 1.2k stars) and Stanley Druckenmiller Investment (tradermonty/claude-trading-skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.