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

Reports On Progress In Physics

ASecurity

Use when targeting Reports on Progress in Physics (RoPP) or deciding whether a physics review manuscript fits this IOP authoritative progress-report venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill reports-on-progress-in-physics --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Reports On Progress In Physics?

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

Security grade badge for Reports On Progress In Physics
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-reports-on-progress-in-physics/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-reports-on-progress-in-physics)

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

Download with Pro
Files
SKILL.md
---
name: reports-on-progress-in-physics
description: Use when targeting Reports on Progress in Physics (RoPP) or deciding whether a physics review manuscript fits this IOP authoritative progress-report venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
---

# Reports on Progress in Physics (reports-on-progress-in-physics)

## Journal positioning

Reports on Progress in Physics is the Institute of Physics (IOP) Publishing journal for authoritative, in-depth review articles — "progress reports" — that survey the state of understanding in a physics topic and define its frontier. Like its APS counterpart Reviews of Modern Physics, RoPP is largely an invited venue; most content is solicited by the editorial board from recognized experts who can deliver a comprehensive, critical, and pedagogically clear account of a field. The readership spans the physics community broadly: specialists seeking a definitive reference, researchers entering an adjacent area, and advanced students. Primary research results are outside scope; RoPP articles synthesize what is established, identify what is contested, and map the open questions ahead.

This skill is a **fit / venue-selection / re-framing** tool. It does not replace the journal's current official submission guidelines. Before submitting, re-check the live author instructions on the IOP Publishing site and the RoPP submission system.

## When to trigger

- An author has been invited by the RoPP editorial board to write a progress report.
- An expert author is considering proposing a review topic to RoPP editors and needs to understand the scope and editorial expectations.
- A physicist wants to compare RoPP versus `reviews-of-modern-physics` to determine which venue is more appropriate for a proposed review.
- A primary-research manuscript is being mis-targeted here and requires re-routing.

## Scope & topic fit

- Comprehensive progress reports on active or recently matured physics subfields: condensed matter, quantum physics, nuclear and particle physics, plasma physics, AMO physics, quantum information, astrophysics, biological physics, photonics, and interdisciplinary areas where physics is central.
- Emerging paradigm areas where a critical synthesis is needed: topological materials, gravitational-wave physics, ultracold quantum matter, quantum computing hardware, precision tests of fundamental physics.
- Pedagogically valuable reports that serve both specialists and physicists crossing into the field; RoPP reviews are expected to be self-contained in their foundational section.
- Topics of sufficient breadth and maturity to warrant a definitive progress-report treatment; reviews of a single group's research program or a single technique without field-wide synthesis context are not appropriate.
- Primary experimental or theoretical research results without a surrounding synthesis framework are outside scope.

## Method & evidence bar

- The review must be comprehensive within its stated scope: major theoretical frameworks, experimental observations, and computational methods must all be addressed; significant omissions undermine the "progress report" mandate.
- Critical evaluation is expected: the authors should assess the strength of evidence for key claims, identify areas of consensus versus ongoing controversy, and flag where the community is uncertain.
- Pedagogical completeness is required: foundational concepts must be derived or explained at a level that allows a physics-PhD-level reader from an adjacent subfield to follow; this distinguishes RoPP from a literature survey.
- Historical context situating how the field reached its current state is part of the RoPP genre and should not be omitted.
- Quantitative claims must trace to the primary literature with citations; the review does not generate new data and should not present unreported analysis as its own contribution.

## Structure & house style

- RoPP articles are long-form by design — comparable in scope and depth to a focused monograph chapter; the length should reflect the scope of the topic, not be artificially constrained.
- A structured outline is essential for navigation; section hierarchy (numbered sections and subsections) is standard and expected by RoPP readers.
- An accessible introduction placing the topic in the context of physics broadly must precede specialist content; the first section should be readable by any physicist.
- An extensive reference list is expected; RoPP reviews are the primary citation that subsequent papers use for "for a review, see …" and completeness is a community trust obligation.
- The outlook/conclusion section should identify genuinely open questions and debate their probable trajectories; speculation clearly flagged as such is acceptable and valued.
- Tables summarizing experimental parameters, materials properties, or computational benchmarks across the literature are a signature RoPP exhibit type.

## Official-submission checklist

- Before giving submission-ready advice, read `../../resources/source-basis.md` and `../../resources/official-source-map.md`; start from the official source anchors for this journal family, then cite the current journal-specific page you checked.
- Search the live site for "Reports on Progress in Physics author guidelines" and follow the current IOP Publishing version.
- Confirm that the editorial board has invited the topic or respond to an invitation before preparing a full manuscript; unsolicited complete manuscripts without prior editorial contact are rare and typically require a proposal-inquiry first.
- Re-check article format requirements: IOP LaTeX templates, reference style (IOP preferred format), figure resolution and file-format specifications.
- Re-check IOP data and software availability policies if computational results or community datasets are discussed.
- Re-check copyright, open-access, and licensing options; IOP offers hybrid and full-OA routes and the APC must be confirmed if OA is chosen.
- If the live official instructions conflict with this skill, the official instructions win.

## Pre-submission self-check

- [ ] Editorial invitation or prior editorial engagement has occurred; submitting unsolicited primary data here is a category error.
- [ ] The review synthesizes the field, not just the authors' own contributions; coverage is balanced and representative.
- [ ] The introduction is accessible to a physicist from an adjacent subfield without requiring specialist background.
- [ ] Controversies and unsettled questions are explicitly identified and balanced, not glossed over.
- [ ] The reference list is comprehensive; seminal contributions across the field's development are all cited.
- [ ] The outlook section identifies specific open problems and their significance for the field.

## Common desk-reject triggers

- Unsolicited primary-research papers submitted to RoPP; these are outside scope and editors return them immediately.
- Reviews that are essentially extended accounts of the author's own group's research without field-wide synthesis.
- Articles with an introduction or opening sections written at specialist depth inaccessible to the broader physics community.
- Reviews that do not engage with major competing interpretations or theoretical frameworks; one-sided synthesis is considered a quality failure.
- Incomplete reference coverage — missing well-known foundational or recent landmark papers is flagged routinely by RoPP reviewers.

## Re-routing decision

For definitive, authoritative physics reviews with APS editorial culture, `reviews-of-modern-physics` (APS Colloquia and Reviews) is the closest peer venue; both are largely invited. For broad physics conceptual syntheses in shorter format targeting non-specialists, `nature-physics` publishes Review articles and Perspectives (often invited). For primary research advancing a specific area, redirect to the appropriate APS archival journal (`physical-review-b`, `physical-review-d`) or to `physical-review-letters` / `physical-review-x` for high-significance original results.

## Output format

```text
[Fit] High / Medium / Low (one-line reason)
[Target] Reports on Progress in Physics
[Topic tags] <2–3 closest topics>
[Method/evidence] <is this an invited, comprehensive, critical synthesis of a field — not new primary research?>
[Top risk] <the single most likely reason for rejection>
[Official items to re-check] <invitation status / IOP template / reference style / data policy / OA/APC>
[Re-route suggestion] <if not a fit, a better-matched venue>
```

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 →