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

Psci Theory And Hypotheses

ASecurity

Use when stating the theory and hypotheses for a Psychological Science manuscript. The journal's credibility norms require a clear separation of confirmatory (preregistered) from exploratory analyses and theory stated before results. Structures the argument; it does not run analyses.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill psci-theory-and-hypotheses --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Psci Theory And Hypotheses?

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

Security grade badge for Psci Theory And Hypotheses
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-psci-theory-and-hypotheses/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-psci-theory-and-hypotheses)

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

Download with Pro
Files
SKILL.md
---
name: psci-theory-and-hypotheses
description: Use when stating the theory and hypotheses for a Psychological Science manuscript. The journal's credibility norms require a clear separation of confirmatory (preregistered) from exploratory analyses and theory stated before results. Structures the argument; it does not run analyses.
---

# Theory & Hypotheses (psci-theory-and-hypotheses)

Psychological Science rewards a **clear theoretical claim** and **honest hypothesis status**. Because
preregistration quality is weighed and a Research Transparency Statement is required, the cardinal
rule is: **state theory and confirmatory hypotheses before the data**, and label exploratory results
as exploratory.

## When to trigger

- Writing the theoretical framing and hypotheses
- Preparing a preregistration / pre-analysis plan (Registered Report or OSF)
- Reconciling what you predicted with what you found
- A reviewer flagged the work as "post hoc," "atheoretical," or "HARKed"

## Build the argument

1. **State the theory.** What mechanism or principle predicts the effect, and why. Keep it crisp —
   the format does not allow a long theoretical treatise.
2. **Derive directional hypotheses.** Translate the theory into specific, testable predictions
   (direction and, where possible, magnitude/effect-size expectations).
3. **Mark hypothesis status.** Separate **confirmatory** (preregistered, predicted in advance) from
   **exploratory** (generated after seeing data) analyses — clearly, in the text.
4. **Specify what would disconfirm.** Say which results would count against the theory; this is what
   makes a test credible.
5. **Match to the right format.** If the theory is best tested prospectively and confirmatorily, a
   **Registered Report** makes the claim far stronger (route via `psci-review-process`).

## Avoiding HARKing (Hypothesizing After Results are Known)

- Do not present an exploratory finding as if it were predicted.
- If you discovered something post hoc, **say so** and frame it as a hypothesis for future
  confirmation — Psychological Science values this honesty and the Transparency Statement surfaces it.

## Anti-patterns

- Theory written to fit the result after the fact (HARKing)
- Vague, non-directional "we expect a relationship" hypotheses
- No statement of what would disconfirm the theory
- Blurring confirmatory and exploratory analyses
- A theory section so long it breaks the 2,000-word budget

## Output format

```
【Theory】the mechanism/principle, briefly
【Hypotheses】directional, testable (H1, H2, …)
【Status】which are confirmatory (preregistered) vs exploratory
【Disconfirming evidence】what would count against the theory
【Format fit】Research Article vs Registered Report (if confirmatory + prospective)
【Next】psci-study-design
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — preregistration templates and tools
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — preregistration and transparency policy

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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 →