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

The Astrophysical Journal

ASecurity

Use when targeting The Astrophysical Journal (ApJ) or its Letters companion (ApJL), or deciding whether an astrophysics manuscript fits this AAS 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-agentsgoapi

Works with

api

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill the-astrophysical-journal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of The Astrophysical Journal?

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

Security grade badge for The Astrophysical Journal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-the-astrophysical-journal/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-the-astrophysical-journal)

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

Download with Pro
Files
SKILL.md
---
name: the-astrophysical-journal
description: Use when targeting The Astrophysical Journal (ApJ) or its Letters companion (ApJL), or deciding whether an astrophysics manuscript fits this AAS venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
---

# The Astrophysical Journal (the-astrophysical-journal)

## Journal positioning

The Astrophysical Journal is the flagship archival research journal of the American Astronomical Society (AAS), published by IOP Publishing, and the primary record for astrophysics across theory, observation, and simulation. Its companion ApJL (The Astrophysical Journal Letters) publishes shorter, high-impact results requiring rapid dissemination. Together they serve the astrophysics community as the workhorse venue where methodological rigor, data quality, and completeness of analysis take precedence over narrative novelty; a paper can be definitive without being a conceptual first. The readership is the professional astrophysics community.

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 AAS/IOP submission portal.

## When to trigger

- The author names ApJ, ApJL, or The Astrophysical Journal as the target venue.
- A manuscript contains rigorous observational, theoretical, or computational astrophysics results that constitute a complete, archival-quality study rather than a single dramatic headline.
- The author is choosing between ApJ (full article) and ApJL (urgent, compact result) and needs to understand the distinction.
- A paper initially aimed at nature-astronomy was found to need more technical depth or scope than that venue allows.

## Scope & topic fit

- Observational studies of stars, galaxies, interstellar and intergalactic media, black holes, compact objects, and Solar System bodies — including full photometric/spectroscopic catalogues with scientific analysis.
- Theoretical astrophysics: analytic models, semi-analytic frameworks, and numerical simulations with direct comparison to observable predictions.
- Instrumentation and pipeline papers when the primary deliverable is community-usable data or methods with demonstrated astrophysical application.
- Multi-wavelength and multi-messenger analyses at the full methodological depth; systematic uncertainty budgets expected.
- Statistical and machine-learning methods for astrophysical inference, provided they are anchored to concrete astrophysical problems.

## Method & evidence bar

- Data quality, reduction, and calibration must be described in sufficient detail for reproduction; data and code availability are expected and increasingly required.
- Systematic uncertainties must be characterised and propagated through the analysis, not just statistical errors.
- Simulations must state initial conditions, resolution, and convergence tests; comparison to observations is expected where applicable.
- ApJL results must be self-contained but concise; the urgency and significance of prompt publication must be stated in the cover letter.
- Statistical methods should follow current community practice (Bayesian or frequentist both accepted, but the choice must be justified and priors stated).

## Structure & house style

- ApJ full articles may be long; thoroughness is valued. Appendices carry supplementary derivations; online-only material carries large data tables.
- ApJL articles are subject to a strict length limit (re-check current limit on the live site); conciseness is mandatory without sacrificing rigor.
- Abstract is unstructured; it should summarise the observational/theoretical approach and the quantitative headline result.
- A "facilities" keyword list and software/code citation section are standard community practice; re-check current AAS journal policy.
- Machine-readable tables, data behind figures, and code repositories should be linked; re-check current data availability requirements.

## 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 "Astrophysical Journal author instructions" or "AAS journals information for authors" and follow the current IOP/AAS version.
- Confirm which article type applies: ApJ Article, ApJL Letter, or ApJS (Supplement Series) for large data products.
- Re-check the current length limit for ApJL, abstract length, and figure/table policies.
- Verify facilities list, software citations, data/code availability, and machine-readable table requirements.
- Confirm author-contribution, competing-interests, and funding-acknowledgement requirements.
- If the live official instructions conflict with this skill, the official instructions win.

## Pre-submission self-check

- [ ] One sentence stating whether this is a complete archival study (ApJ) or an urgent, compact advance (ApJL), and why the scope matches.
- [ ] Systematic uncertainties are characterised and the analysis is reproducible from the Methods description.
- [ ] Data tables, code, and model outputs are linked or will be deposited; facilities and software are cited.
- [ ] Abstract states the quantitative result, not just the topic.
- [ ] For ApJL: manuscript fits within the current length limit and the cover letter articulates the urgency.

## Common desk-reject triggers

- An ApJL submission that exceeds the length limit or whose result is solid but not urgent enough to justify rapid publication.
- A paper with serious unaddressed systematics (e.g., uncalibrated photometry, unquantified selection effects) that makes the headline result unreliable.
- A theoretical paper with no connection to observable predictions, appropriate instead for a pure-theory preprint archive with subsequent submission elsewhere.
- A pipeline or data-release paper with no astrophysical analysis; those belong in ApJS or instrument-focused venues.
- Results already superseded by published work, or where the claimed advance is incremental by ApJ community standards.

## Re-routing decision

- Conceptual headline result with broad significance beyond astrophysics → `nature-astronomy` or Nature/Science.
- Large data releases or survey descriptions without deep per-object analysis → The Astrophysical Journal Supplement Series (ApJS).
- Broad archival astronomy (especially non-US community, optical surveys, stellar/galactic) → `monthly-notices-of-the-royal-astronomical-society`.

## Output format

```text
[Fit] High / Medium / Low (one-line reason)
[Target] The Astrophysical Journal (ApJ / ApJL)
[Topic tags] <2–3 closest topics>
[Method/evidence] <does the analysis meet the archival rigor and data-quality bar — or urgency bar for ApJL?>
[Top risk] <the single most likely reason for rejection>
[Official items to re-check] <article type ApJ/ApJL/ApJS / length / facilities / software citations / data-code availability>
[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 →