Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
A skill your agent uses when starting or orienting any Journal of Policy Analysis and Management (JPAM) manuscript and you need the entry point.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpam-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpam-workflow --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-Policy-Analysis-and-Management-Skills/skills/jpam-workflow .claude/skills/jpam-workflow && 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 "jpam-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-workflow into .claude/skills/jpam-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-workflow", 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-Policy-Analysis-and-Management-Skills/skills/jpam-workflowType 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 jpam-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpam-workflow --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-Policy-Analysis-and-Management-Skills/skills/jpam-workflow .agents/skills/jpam-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jpam-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-workflow into .agents/skills/jpam-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-workflow", 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 jpam-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpam-workflow --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-Policy-Analysis-and-Management-Skills/skills/jpam-workflow .cursor/skills/jpam-workflow && 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 "jpam-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-workflow into .cursor/skills/jpam-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-workflow", 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-Policy-Analysis-and-Management-Skills/skills/jpam-workflow--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 jpam-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpam-workflow --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-Policy-Analysis-and-Management-Skills/skills/jpam-workflow .gemini/skills/jpam-workflow && 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 "jpam-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-workflow into .gemini/skills/jpam-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-workflow", 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 jpam-workflowInstalls 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 jpam-workflow -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-Policy-Analysis-and-Management-Skills/skills/jpam-workflow .github/skills/jpam-workflow && 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 "jpam-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-workflow into .github/skills/jpam-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-workflow", 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 jpam-workflow -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 jpam-workflow --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-Policy-Analysis-and-Management-Skills/skills/jpam-workflow .opencode/skills/jpam-workflow && 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 "jpam-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-workflow into .opencode/skills/jpam-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-workflow", 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.
jpam-workflowA skill your agent uses when starting or orienting any Journal of Policy Analysis and Management (JPAM) manuscript and you need the entry point.
Jpam Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when starting or orienting any Journal of Policy Analysis and Management (JPAM) manuscript and you need the entry point. Routes to the right JPAM sub-skill based on lifecycle stage and which article type (Feature Research Article, Point/Counterpoint, Methods for Policy Analysis, Policy Insights, Policy Retrospective) fits. It dispatches; it does not draft content.
Its SKILL.md is about 1.3k 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 Product & Project Management, covering Retrospectives. 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.
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.
Jpam Workflow loads about 1.3k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 446 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). 446 words, ~1,319 tokens.
.claude/skills/jpam-workflow/SKILL.md (or your agent's skills folder).The orchestrator for a JPAM submission. Figure out the stage and the article type, then send the user to the matching skill. JPAM is the cross-disciplinary public-policy-analysis flagship of APPAM (published by Wiley) — the router's first job is to make sure the paper delivers a credibly identified effect of a real policy or program and a clear, non-overclaimed policy implication, legible to economists, political scientists, and public-management scholars alike.
jpam-rebuttal)| Situation | Type | Route to |
|---|---|---|
| Full causal evaluation of a policy/program with broad relevance | Feature Research Article | normal pipeline below |
| Invited debate between scholars on a timely policy question (not peer-reviewed) | Point/Counterpoint | jpam-writing-style + jpam-literature-positioning |
| A methodological advance for policy analysts | Methods for Policy Analysis | jpam-research-design + jpam-data-analysis |
| Short, fast-turnaround take on a pressing issue (≤ 3,000 words, not peer-reviewed) | Policy Insights | jpam-writing-style + jpam-topic-selection |
| Reflective look back at how a policy/literature evolved | Policy Retrospective | jpam-literature-positioning + jpam-theory-building |
Point/Counterpoint and Policy Insights are invited / not peer-reviewed — confirm the current invitation and length rules on the author page before pitching (检索于 2026-06;以官网为准).
Idea / policy relevance + fit? → jpam-topic-selection
Where does it sit across fields? → jpam-literature-positioning
What's the theory of change? → jpam-theory-building
Is identification credible? → jpam-research-design
Are the estimates + CBA sound? → jpam-data-analysis
Are the exhibits clear? → jpam-tables-figures
Does the implication land? → jpam-writing-style
Replication package ready? → jpam-transparency-and-data
How will it be judged? → jpam-review-process
Ready to submit? → jpam-submission
Got an R&R / decision? → jpam-rebuttaltopic-selection → literature-positioning → theory-building → research-design → data-analysis → tables-figures → writing-style → transparency-and-data → review-process → submission → rebuttal
Iterate: most papers loop theory-of-change ↔ design ↔ analysis several times before writing-style.
| Check | Pass condition | Route if weak |
|---|---|---|
| Policy relevance | A policymaker or program designer can state what decision this evidence informs. | jpam-topic-selection |
| Identification | The causal claim rests on a credible design (RCT / DiD / RD / IV / synthetic control), not selection-on-observables hope. | jpam-research-design |
| Cross-disciplinary reach | An economist, a political scientist, and a public-management reader each see why it matters. | jpam-literature-positioning |
| Implication discipline | The policy takeaway is calibrated to what the design actually identifies — no overclaiming. | jpam-writing-style |
If the paper fails the identification check, do not route to writing-style — JPAM reviewers reject well-written papers whose causal claim outruns the design. If it fails policy relevance, it may be a better fit for a field economics/political-science journal (see sibling guard in README).
【Stage】idea / positioning / theory / design / analysis / exhibits / writing / transparency / review / submit / rebut
【Type】Feature Research Article / Point-Counterpoint / Methods / Policy Insights / Policy Retrospective
【Route to】jpam-<skill>
【Why】one line
【Then】the next skill after that../../resources/external_tools.md — policy-evaluation data sources + software by method../../resources/official-source-map.md — official JPAM / APPAM / Wiley URLs behind every fact in this pack© 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-Policy-Analysis-and-Management-Skills/skills/jpam-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Jpam Workflow 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 |
|---|---|---|---|---|---|---|
| Jpam Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Weekly Engineering Retrogarrytan/gstack | 136k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Dough Execute Planterryyin/lizard | 2.6k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Oral Paper SkillAdkid-Zephyr/oral-paper-skill | 350 | — | ~1.9k | Automated safety check: Pass | None | |
| Deck Retroasheshgoplani/agent-deck | 1k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Dough Execution Retrospectiveterryyin/lizard | 2.6k | — | ~4k | Automated safety check: Pass | Custom licence |
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
terryyin/lizard
Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…
Adkid-Zephyr/oral-paper-skill
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.
asheshgoplani/agent-deck
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs.
terryyin/lizard
Reviews planned, completed planless quick, or quick-to-planned execution against original intent, aggregate commits, current whole-product architecture, and tests, including after cleanup.
HughYau/qiushi-skill
批评与自我批评:在工作完成、阶段验收、收到批评或同类错误反复出现时,对成果和过程做诚实、具体、基于事实的审视,输出可执行的改进项,并处理外来批评而不辩解。触发信号包括 review、复盘、审查、"帮我看看有没有问题"、"你确定吗";任务刚开始或只是单步查询时不触发。
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 starting or orienting any Journal of Policy Analysis and Management (JPAM) manuscript and you need the entry point. Jpam Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when starting or orienting any Journal of Policy Analysis and Management (JPAM) manuscript and you need the entry point.
Jpam Workflow fits situations like: orienting any Journal of Policy Analysis and Management (JPAM) manuscript and you need the entry point; tasks that involve Retrospectives.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpam-workflow -a claude-code`. Or copy the skill folder (Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jpam-workflow in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpam-workflow -a codex`. Or copy the skill folder (Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jpam-workflow 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 jpam-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jpam-workflow, .gemini/skills/jpam-workflow, .github/skills/jpam-workflow and .opencode/skills/jpam-workflow in your project.
SKILL.md names no scripts, command-line tools or credentials: Jpam Workflow 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.
Jpam Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Jpam Workflow: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.6k stars), Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 350 stars) and Deck Retro (asheshgoplani/agent-deck, 1k 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,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.