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

Joc Open Science And Transparency

ASecurity

Use when preparing the open-science and transparency materials for a Journal of Communication (JoC) manuscript. JoC requires a Data Availability Statement and supports Open Science Badges for open data, open materials, and preregistration. Covers quantitative, computational, and qualitative transparency and the restricted-data path. Prepares the materials; it does not waive requirements.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill joc-open-science-and-transparency --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Joc Open Science And Transparency?

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

Security grade badge for Joc Open Science And Transparency
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-joc-open-science-and-transparency/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-joc-open-science-and-transparency)

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

Download with Pro
Files
SKILL.md
---
name: joc-open-science-and-transparency
description: Use when preparing the open-science and transparency materials for a Journal of Communication (JoC) manuscript. JoC requires a Data Availability Statement and supports Open Science Badges for open data, open materials, and preregistration. Covers quantitative, computational, and qualitative transparency and the restricted-data path. Prepares the materials; it does not waive requirements.
---

# Open Science & Transparency (joc-open-science-and-transparency)

JoC requires a **Data Availability Statement** on every article and offers **Open Science Badges** for
open data, open materials, and preregistration. Transparency is not an afterthought — build the
statement and supporting materials as you write so submission and any badge claim go smoothly.

## When to trigger

- Drafting the **Data Availability Statement** (a submission requirement)
- Deciding whether to pursue **Open Science Badges** (open data / open materials / preregistration)
- Preparing a **preregistration** for a prospective design (note it in the cover letter)
- Data cannot be fully shared (privacy, ethics, platform/legal restrictions) and you need the path forward

## What JoC expects (verify current wording on the policy page)

1. **Data Availability Statement (required).** State where the data are (repository + identifier),
   under what conditions they can be accessed, and — if they cannot be shared — **why**, with
   instructions for how others might obtain them.
2. **Open Science Badges (optional, earned).**
   - **Open Data** — data and a codebook deposited in a trusted repository with a persistent identifier.
   - **Open Materials** — stimuli, instruments, code, and protocols deposited so the study can be reproduced.
   - **Preregistration** — a time-stamped, registered design/analysis plan; note it in the cover letter.
3. **Quantitative / computational materials.** Data, code, codebook, and documentation sufficient to
   regenerate every reported result; master script + README + pinned versions + seeds; for automated
   text measures, include the human-validation materials.
4. **Qualitative materials.** Share the materials that support the claims (e.g., coding schemes,
   evidence tables, de-identified excerpts) with access controls where needed (QDR for controlled access).

## When data cannot be shared (restricted-data path)

- **Explain why** in the Data Availability Statement (ethical/privacy concerns, platform terms of
  service, or legal restrictions by the provider).
- Provide **instructions on how others can obtain the data** (access process, application, provider contact).
- Where possible, provide **synthetic or de-identified data** so the code can be run.

## Build-as-you-go checklist

- [ ] **Data Availability Statement** drafted (repository, identifier, access conditions, or exemption)
- [ ] One **master script** regenerates **every** table and figure from raw/constructed data
- [ ] **README** documents data provenance, construction, and how to reproduce each exhibit
- [ ] **Seeds** set and reported for every stochastic step; software/package **versions pinned**
- [ ] Open Science Badge materials staged (open data / open materials / preregistration) where claimed
- [ ] Content analysis: codebook + intercoder-reliability report included
- [ ] Materials **anonymized** (no author-identifying paths/links) for double-anonymous review

## Anti-patterns

- Submitting without a Data Availability Statement (it is required)
- Claiming a badge whose materials are not actually deposited or do not reproduce the results
- A personal URL instead of a trusted repository with a persistent identifier
- Claiming data are restricted without giving an access path or synthetic substitute
- De-anonymizing the manuscript via an open-materials link during review

## Output format

```
【Data Availability Statement】drafted? repository + identifier or exemption? [Y/N]
【Reproduces tables/figures?】master script verified locally? [Y/N]
【Badges sought】open data / open materials / preregistration (materials staged?)
【Documentation】README + provenance + seeds + pinned versions? [Y/N]
【Restricted data?】exemption note + access path + synthetic data?
【Qualitative transparency】coding scheme / evidence documented? [Y/N/NA]
【Next】joc-review-process
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — reproducibility tooling and qualitative-transparency options (OSF, QDR)
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — Data Availability Statement requirement + Open Science Badges

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 →