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

Spq Data And Transparency

ASecurity

Use when preparing the data, materials, and transparency posture for a Social Psychology Quarterly (SPQ) manuscript. SPQ ENCOURAGES sharing data, code, and materials but does NOT require it, and willingness to share has no impact on acceptance; the journal follows the ASA data-sharing norm and Code of Ethics. Covers quantitative and qualitative/interpretive transparency and confidentiality. Prepares the posture; it does not invent requirements.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill spq-data-and-transparency --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Spq Data And Transparency?

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

Security grade badge for Spq Data And Transparency
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-spq-data-and-transparency/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-spq-data-and-transparency)

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

Download with Pro
Files
SKILL.md
---
name: spq-data-and-transparency
description: Use when preparing the data, materials, and transparency posture for a Social Psychology Quarterly (SPQ) manuscript. SPQ ENCOURAGES sharing data, code, and materials but does NOT require it, and willingness to share has no impact on acceptance; the journal follows the ASA data-sharing norm and Code of Ethics. Covers quantitative and qualitative/interpretive transparency and confidentiality. Prepares the posture; it does not invent requirements.
---

# Data & Transparency (spq-data-and-transparency)

SPQ's posture is deliberately different from open-data-mandate journals. It **encourages** researchers to
make data, code, and materials available, but **this is not a requirement**, and **willingness to publicly
release data and materials has no impact on the likelihood of acceptance**. The journal recognizes that not
all areas of social psychology — especially ethnographic and interview work — can share data practically
or ethically. Transparency at SPQ means clear documentation and honoring the **ASA data-sharing norm**,
not a verified replication gate.

## When to trigger

- Deciding what data/code/materials to share, and how to describe your transparency posture
- Confidential or sensitive data (fieldnotes, interview transcripts, restricted survey data)
- A reviewer asked about materials, measures, or replicability
- Writing the data-availability and ethics language

## What SPQ actually asks (verify current wording on the policy page)

1. **Encouraged, not required.** SPQ encourages open data, code, and materials so others can review and
   use them — but does not require it, and **non-sharing does not lower acceptance odds**. Do not write as
   if it were a gate; do not over-claim "open" materials you cannot release.
2. **ASA data-sharing norm.** As a regular practice, sociologists share data and documentation as part of
   a research plan and **generally make data available after a project's completion or major
   publications**, except where proprietary agreements preclude it or where **confidentiality of
   participants cannot otherwise be protected** (e.g., fieldnotes, detailed ethnographic interviews).
3. **Quantitative materials (if shared).** Data, code, and documentation sufficient to regenerate reported
   results: master script + README + pinned versions + seeds + scale items.
4. **Qualitative / interpretive transparency.** You generally **cannot** share raw fieldnotes or interview
   transcripts; instead document the analytic process — sampling/site logic, coding scheme, and enough
   excerpts for readers to judge — and protect participant confidentiality.

## Confidentiality & ethics

- Protect participants: de-identify, aggregate, or withhold where re-identification is a risk.
- Honor IRB/consent terms and any data-provider restrictions; say so plainly if data cannot be shared.
- Submitting the same manuscript elsewhere while under SPQ review is unethical; flag prior appearance of
  significant findings.

## Good-practice checklist (not a mandate)

- [ ] Decide and state a clear, honest **data-availability posture** (what you can/can't share and why)
- [ ] If sharing quantitative materials: master script regenerates tables/figures; README; seeds; pinned versions
- [ ] If interpretive: document sampling/site logic and coding; provide representative excerpts; protect confidentiality
- [ ] Scale items / measures documented (in text or supplementary materials)
- [ ] Ethics/IRB and confidentiality handled per ASA Code of Ethics
- [ ] Preregistration linked (anonymized) where you used it — useful but not required

## Anti-patterns

- Writing as though SPQ mandates open data, or implying sharing buys acceptance (it does not)
- Claiming data are "available" when consent/confidentiality actually preclude release
- No documentation of measures or analytic procedure at all
- Exposing participant identities to perform "transparency"
- Treating qualitative transparency as impossible and so documenting nothing

## Output format

```
【Posture】what data/code/materials will (or will not) be shared, and why
【Encouraged-not-required understood?】[Y/N]
【Quantitative (if shared)】master script + README + seeds + measures? [Y/N/NA]
【Qualitative transparency】sampling/coding documented + confidentiality protected? [Y/N/NA]
【Ethics/IRB + ASA norm honored】[Y/N]
【Next】spq-review-process
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — reproducibility tooling and CAQDAS for documented interpretive work
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — SPQ data-and-materials statement + ASA data-sharing 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', ...

686011 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 →