Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Jcr Theory Development

ASecurity

Use when building the conceptual core of a Journal of Consumer Research (JCR) manuscript — the psychological process and hypotheses for an experiments paper, or the interpretive theorization for a Consumer Culture Theory (CCT) paper. Builds the mechanism; it does not run the studies (jcr-methods/jcr-data-analysis).

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agents

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jcr-theory-development --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jcr Theory Development?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Jcr Theory Development
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jcr-theory-development/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jcr-theory-development)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: jcr-theory-development
description: Use when building the conceptual core of a Journal of Consumer Research (JCR) manuscript — the psychological process and hypotheses for an experiments paper, or the interpretive theorization for a Consumer Culture Theory (CCT) paper. Builds the mechanism; it does not run the studies (jcr-methods/jcr-data-analysis).
---

# Theory Development (jcr-theory-development)

## When to trigger

- You have a consumer effect but no explanatory mechanism
- Hypotheses read as "A relates to B" with no psychological or sociocultural account
- A reviewer says "the theory is thin" or "this is an effect in search of a process"
- You are theorizing fieldwork and need to move from description to conceptual claims

## The JCR standard: theory that advances, deepens, or repudiates

JCR judges manuscripts on whether they **advance, deepen, or repudiate existing theory** about consumption, with conceptual *and* empirical support. The theory section must do conceptual work — not just predict an effect, but explain **why** it occurs in a way that engages an established account and changes it. Substantive framing from psychology, anthropology, sociology, or economics is expected, not a decorative citation.

Because JCR's dominant tradition is **theory-driven behavioral experimentation**, the modal theory section specifies a **psychological process** (the mediator) and the **conditions** under which it operates (moderators), then derives testable hypotheses *a priori*. The journal also publishes interpretive **CCT** work, where "theory development" means building concepts and a conceptual framework grounded in the data rather than deriving point-prediction hypotheses.

## For experiments papers: specify the process

- **Mechanism (mediator):** name the psychological process that produces the effect (e.g., a shift in construal, inference, motivation, affect, or identity). The process — not just the outcome — is the contribution.
- **Moderation as theory test:** derive moderators that the mechanism *predicts*. A moderator that turns the effect off (or reverses it) when the proposed process is blocked is strong process evidence and a theoretical claim, not a robustness afterthought.
- **A priori hypotheses:** state hypotheses before the studies; avoid HARKing. Each study should test a distinct link in the causal chain (effect → mediation → moderation → boundary).
- **Alternative accounts:** name the rival processes a reviewer will raise and design to rule them out conceptually before you do so empirically.

## For CCT / interpretive papers: build concepts grounded in data

- Move from rich description to **second-order theoretical constructs** and a conceptual framework.
- Engage sociological/anthropological theory (meaning, ritual, identity, market dynamics, structure-agency) as the conceptual engine.
- The contribution is a **new way of seeing** a consumption phenomenon, not a tested point prediction; make the conceptual claims explicit and show their grounding.

## Checklist

- [ ] The mechanism is named and explained, not just asserted
- [ ] The theory **changes** an existing account (advance / deepen / repudiate), stated explicitly
- [ ] A base discipline (psych / anthro-soc / econ) does real conceptual work
- [ ] Experiments: a priori hypotheses map to a study chain (effect → process → boundary)
- [ ] CCT: data-grounded constructs and framework, engaging sociocultural theory
- [ ] Rival explanations are named and addressable

## Anti-patterns

- **Effect in search of a process**: a robust result with no mechanism.
- **Moderator dump**: boundary conditions with no theoretical rationale.
- **HARKing**: presenting post hoc explanations as a priori theory.
- **Borrowed-label theory**: invoking a construct's name without using its logic.
- **CCT-as-description**: thick description that never reaches conceptual claims.

## Output format

```
【Genre】experiments / CCT
【Core claim】what theory we advance/deepen/repudiate
【Mechanism】process (mediator) or grounded construct
【Boundary】moderators / scope conditions and their rationale
【Rivals】alternative accounts to rule out
【Study chain】how each study tests a link (experiments) / framework (CCT)
【Next step】jcr-literature-positioning then jcr-methods
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →