Agent skill

Jpam Theory Building

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

MITAuto-check passed

Install Jpam Theory Building

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpam-theory-building -a claude-code

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

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpam-theory-building --agent claude-code

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

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-theory-building .claude/skills/jpam-theory-building && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "jpam-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-theory-building into .claude/skills/jpam-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-theory-building", 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

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-theory-building

Type 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpam-theory-building -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpam-theory-building --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-theory-building .agents/skills/jpam-theory-building && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "jpam-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-theory-building into .agents/skills/jpam-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-theory-building", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpam-theory-building -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpam-theory-building --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-theory-building .cursor/skills/jpam-theory-building && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "jpam-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-theory-building into .cursor/skills/jpam-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-theory-building", 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

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-theory-building

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpam-theory-building -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpam-theory-building --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-theory-building .gemini/skills/jpam-theory-building && rm -rf skills-src

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

Paste into Gemini CLI

Install the "jpam-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-theory-building into .gemini/skills/jpam-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-theory-building", 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.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpam-theory-building

Installs 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).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpam-theory-building -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ 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-theory-building .github/skills/jpam-theory-building && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "jpam-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-theory-building into .github/skills/jpam-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-theory-building", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpam-theory-building -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpam-theory-building --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-theory-building .opencode/skills/jpam-theory-building && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "jpam-theory-building" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-theory-building into .opencode/skills/jpam-theory-building/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpam-theory-building", 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: jpam-theory-building
GitHub stars: 1.2k
Token cost: ~1.3k tokens
SKILL.md length: 599 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 5 steps: Lever → mechanism → outcome. Write the… → Behavioral or institutional… → Predicted heterogeneity. Whom should the… → …
The scope conditions that govern transfer to other settings
SKILL.md covers When to trigger, Building the theory of change, What the theory buys… and Checklist, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Jpam Theory Building is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when building the conceptual frame of a Journal of Policy Analysis and Management (JPAM) manuscript — the theory of change / logic model linking the policy lever to outcomes, the mechanism, and the scope conditions that govern transfer to other settings. Sharpens the argument; it does not run estimation or design identification.

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.

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

The scope conditions that govern transfer to other settings

Example prompts

“/jpam-theory-building”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Lever → mechanism → outcome. Write the causal chain explicitly: the policy changes X (incentive,
Behavioral or institutional micro-foundation. Say who responds and why — incentives,
Predicted heterogeneity. Whom should the effect be larger or smaller for? Specify before
Scope conditions for transfer. What features of this setting (administrative capacity, market
Unintended effects and general equilibrium. Name plausible offsetting or spillover responses a

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

Jpam Theory Building loads about 1.3k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 599 words of instructions outside code blocks.

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

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). 599 words, ~1,347 tokens.

Download SKILL.mdSave it as .claude/skills/jpam-theory-building/SKILL.md (or your agent's skills folder).

name: jpam-theory-building
description: Use when building the conceptual frame of a Journal of Policy Analysis and Management (JPAM) manuscript — the theory of change / logic model linking the policy lever to outcomes, the mechanism, and the scope conditions that govern transfer to other settings. Sharpens the argument; it does not run estimation or design identification.

Theory of Change & Mechanism (jpam-theory-building)

JPAM is empirical, but the best policy papers are not atheoretical. The "theory" here is a theory of change: a transparent logic that says why the policy lever should move the outcome, through what mechanism, for whom, and under what conditions it would (or would not) transfer to another jurisdiction or scale. This frame is what turns a single estimate into evidence a policymaker elsewhere can use, and it disciplines the cost-benefit and heterogeneity analysis downstream.

When to trigger

Specifying the logic model / theory of change before or alongside the design
A reviewer asked "what's the mechanism?" or "why would this generalize?"
Deciding which heterogeneity and mediation analyses are theory-driven (not fishing)
Framing scope conditions for external validity and scale-up

Building the theory of change

Lever → mechanism → outcome. Write the causal chain explicitly: the policy changes X (incentive, constraint, information, price, access), which operates through mechanism M, producing outcome Y.
Behavioral or institutional micro-foundation. Say who responds and why — incentives, liquidity, salience, capacity, compliance, take-up. Ground it in the relevant econ / PS / PA theory.
Predicted heterogeneity. Whom should the effect be larger or smaller for? Specify before estimation so subgroup results read as tests, not data-mining.
Scope conditions for transfer. What features of this setting (administrative capacity, market structure, population, complementary policies) does the effect depend on? This governs external validity and scale-up claims.
Unintended effects and general equilibrium. Name plausible offsetting or spillover responses a policymaker would worry about (displacement, crowd-out, behavioral adaptation).

What the theory buys (JPAM-specific)

It tells policymakers in other jurisdictions whether the result should travel.
It pre-commits the heterogeneity and mediation analyses, protecting them from fishing critiques.
It specifies which costs and benefits enter the cost-benefit analysis and for whom (distribution).
It distinguishes "the program worked here" from "this kind of program works through this mechanism."

Checklist

An explicit lever → mechanism → outcome chain written down
A behavioral/institutional micro-foundation for who responds and why
Predicted heterogeneity stated before estimation
Scope conditions for transfer / scale-up named
Plausible unintended effects, spillovers, or GE responses flagged
Mechanism tied to specific, testable observable implications

Show full SKILL.md (245 more words)Show less

Anti-patterns

A bare estimate with no mechanism — "the program raised Y" with no account of why
Post hoc storytelling that fits whatever heterogeneity the data happened to show
Claiming broad generalizability with no stated scope conditions
Ignoring unintended consequences a policymaker would immediately ask about
Borrowing a formal model that adds notation but no testable, policy-relevant implication

Worked micro-example (illustrative)

A team evaluates a tax-credit expansion. The bare version says "the credit raised employment." The JPAM theory-of-change version writes the chain — credit raises the after-tax return to work (mechanism: labor-supply incentive) → larger response for the population facing the steepest participation tax (predicted heterogeneity: single parents near the phase-in) → effect depends on local labor demand and on take-up via tax-filing (scope conditions) — and flags a plausible unintended effect (employers capturing part of the credit through wage adjustment). Each link is then a testable implication the design and heterogeneity analysis must address, and the scope conditions tell a policymaker in another state whether the result should travel. (Fields/numbers illustrative.)

Calibration anchors (hedged)

The "theory" JPAM wants is a transparent logic model, not necessarily a formal model; added notation must buy a testable, policy-relevant implication.
Scope conditions are a strength, not a hedge: they are how a single evaluation informs decisions elsewhere, which is JPAM's whole purpose.
Pre-specify heterogeneity and mechanism tests so they read as confirmatory, not as fishing.

Output format

【Lever → mechanism → outcome】the causal chain in one line
【Micro-foundation】who responds and why
【Predicted heterogeneity】subgroups specified ex ante
【Scope conditions】what the effect depends on for transfer
【Unintended effects】spillovers / GE / displacement flagged
【Next】jpam-research-design

Supplementary resources

../../resources/exemplars/library.md — JPAM papers whose mechanism makes the result portable
../../resources/external_tools.md — mediation / mechanism estimation packages

Files

Just SKILL.md in Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-theory-building of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Jpam Theory Building 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.

Jpam Theory Building compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Jpam Theory Building this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.3k	Automated safety check: Pass	MIT	14 days ago
Implementing Policy As Code With Open Policy Agentmukul975/Anthropic-Cybersecurity-Skills	34k	—	~2.6k	Automated safety check: Notes	Apache-2.0	1 mo ago
Policy Acknowledgementsickn33/agentic-awesome-skills	47k	1 repos	~3.4k	Automated safety check: Pass	MIT	2 days ago
Privacy Policythedaviddias/Front-End-Checklist	74k	—	~617	Automated safety check: Pass	MIT	5 days ago
Frame Titlethedaviddias/Front-End-Checklist	74k	—	~438	Automated safety check: Pass	MIT	5 days ago
Editorial Policythedaviddias/Front-End-Checklist	74k	—	~763	Automated safety check: Pass	MIT	5 days ago

Similar skills

Implementing Policy As Code With Open Policy Agent
mukul975/Anthropic-Cybersecurity-Skills
Implements policy-as-code enforcement with Open Policy Agent (OPA) and Gatekeeper for Kubernetes and CI/CD pipelines, covering writing Rego policies, deploying OPA Gatekeeper as a Kubernetes…
34k GitHub stars~2.6k tokensUpdated 1 mo ago
DevOps & CloudAuto-check: notes
Policy Acknowledgement
sickn33/agentic-awesome-skills
Policy acknowledgement register: employee, policy and version, sent and due dates, acknowledged date and flag, days overdue, reminder sent and status.
47k GitHub starsUsed in 1 repo~3.4k tokens
Auto-check passed
Privacy Policy
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing whether a website has a visible, accessible privacy policy link, particularly in the footer navigation.
74k GitHub stars~617 tokensUpdated 5 days ago
Legal & ComplianceAuto-check passed
Frame Title
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Provide titles for iframes and frames.
74k GitHub stars~438 tokensUpdated 5 days ago
Frontend & DesignAuto-check passed
Editorial Policy
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing a blog, news site, or YMYL content site for trust signals, drafting editorial policy page content, or evaluating whether a site meets Google's quality rater…
74k GitHub stars~763 tokensUpdated 5 days ago
Auto-check passed
Policy Drafting
anthropics/claude-for-legal
Official
Draft an employment policy with state supplements where law differs across the jurisdictional footprint.
9.6k GitHub starsUsed in 2 repos~1.4k tokens
Legal & ComplianceAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
1.2k GitHub stars~1.6k tokensUpdated 14 days ago
Auto-check passed

Questions about Jpam Theory Building

What does Jpam Theory Building do?

A skill your agent uses when building the conceptual frame of a Journal of Policy Analysis and Management (JPAM) manuscript — the theory of change / logic model linking the policy lever to outcomes…. Jpam Theory Building is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when building the conceptual frame of a Journal of Policy Analysis and Management (JPAM) manuscript — the theory of change / logic model linking the policy lever to outcomes, the mechanism, and the scope conditions that govern transfer to other settings.

When should I use Jpam Theory Building?

Jpam Theory Building fits situations like: the scope conditions that govern transfer to other settings.

How do I install Jpam Theory Building in Claude Code?

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

How do I install Jpam Theory Building in Codex?

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

Can I use Jpam Theory Building 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 jpam-theory-building -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-theory-building, .gemini/skills/jpam-theory-building, .github/skills/jpam-theory-building and .opencode/skills/jpam-theory-building in your project.

What does Jpam Theory Building need to run?

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

Does Jpam Theory Building 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 Jpam Theory Building 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 Jpam Theory Building use?

Jpam Theory Building 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 Jpam Theory Building use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Jpam Theory Building?

Skills that share tags, products or a category with Jpam Theory Building: Implementing Policy As Code With Open Policy Agent (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Policy Acknowledgement (sickn33/agentic-awesome-skills, 47k stars), Privacy Policy (thedaviddias/Front-End-Checklist, 74k stars) and Frame Title (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jpam Theory Building?

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.

Install Jpam Theory Building

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Theory of Change & Mechanism (jpam-theory-building)

When to trigger

Building the theory of change

What the theory buys (JPAM-specific)

Checklist

Anti-patterns

Worked micro-example (illustrative)

Calibration anchors (hedged)

Output format

Supplementary resources

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Questions about Jpam Theory Building