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

Monthly Notices Of The Royal Astronomical Society

ASecurity

Use when targeting Monthly Notices of the Royal Astronomical Society (MNRAS) or deciding whether an astronomy manuscript fits this RAS/OUP 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
0 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 monthly-notices-of-the-royal-astronomical-society --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Monthly Notices Of The Royal Astronomical Society?

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

Security grade badge for Monthly Notices Of The Royal Astronomical Society
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-monthly-notices-of-the-royal-astronomical-society/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-monthly-notices-of-the-royal-astronomical-society)

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

Download with Pro
Files
SKILL.md
---
name: monthly-notices-of-the-royal-astronomical-society
description: Use when targeting Monthly Notices of the Royal Astronomical Society (MNRAS) or deciding whether an astronomy manuscript fits this RAS/OUP venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
---

# Monthly Notices of the Royal Astronomical Society (monthly-notices-of-the-royal-astronomical-society)

## Journal positioning

Monthly Notices of the Royal Astronomical Society is published by Oxford University Press on behalf of the Royal Astronomical Society and is one of the world's principal archival journals for astronomy and astrophysics, covering observational, theoretical, and computational work across all sub-fields. MNRAS is a broad-scope workhorse comparable in positioning to ApJ: it rewards completeness, methodological rigour, and thorough characterisation of uncertainties over narrative novelty. The journal has a strong European, Southern-hemisphere, and radio/optical-survey community base, though its scope is fully international. Papers do not need to be conceptual firsts to be published, but they must constitute a meaningful, self-contained contribution.

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 OUP/RAS submission portal.

## When to trigger

- The author names MNRAS or Monthly Notices as the target venue.
- An astronomy or astrophysics manuscript is archival quality but not a Nature-tier conceptual headline; the author is choosing between MNRAS and the-astrophysical-journal.
- An observational survey, simulation paper, or statistical analysis needs a broad-scope archival home that will not penalise technical depth.
- The author needs MNRAS's desk-reject risks and alternative-venue guidance.

## Scope & topic fit

- Observational astronomy across all wavelengths: stellar physics, variable stars, stellar populations, extragalactic astronomy, galaxy surveys, large-scale structure, cosmology.
- Theoretical and numerical astrophysics: N-body/hydrodynamic simulations, semi-analytic models, analytic theory across all sub-fields.
- Radio, optical, infrared, X-ray, and high-energy astrophysics; Solar System science.
- Astrometry and survey characterisation when the scientific analysis is present and complete.
- Statistical and computational methods for astronomical data, including machine-learning applications with astrophysical validation.

## Method & evidence bar

- The analysis must be self-contained and reproducible: data reduction and calibration steps, software used, and parameter choices must be described in sufficient detail.
- Systematic and statistical uncertainties must both be reported and propagated; selection effects in survey data must be characterised.
- Simulations require statement of physical setup, numerical resolution, and convergence or resolution tests.
- MNRAS uses referee review; revisions are expected to address all referee comments; the review process is not as editorially curated as Nature-family journals.
- Data and code availability is encouraged and increasingly expected; re-check the current OUP/RAS policy.

## Structure & house style

- Article length is relatively unconstrained for full papers; Supporting Information can carry large tables and supplementary figures.
- Abstract is unstructured, typically one paragraph; it must state the method, key result, and quantitative conclusion.
- Section structure follows the standard astronomical format: Introduction, Observations/Data, Analysis/Methods, Results, Discussion, Conclusions.
- LaTeX is the mandatory manuscript format; MNRAS provides its own LaTeX class file (mnras.cls), which must be used.
- References follow the author-year (Harvard) style as implemented in the MNRAS class.
- MNRAS also publishes shorter Letters (MNRAS Letters) for urgent, high-impact results; these have a strict length limit — re-check the current limit.

## 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 "MNRAS author instructions" or "Monthly Notices information for authors" and follow the current OUP/RAS version.
- Confirm article type: standard paper or MNRAS Letters; re-check the current length limit for Letters.
- Download and use the current mnras.cls LaTeX class file; submissions not using it may be returned.
- Verify data/code availability, Supporting Information policy, and figure resolution and format requirements.
- Check author-contribution, competing-interests, funding, and any ethics/consent requirements.
- Re-check the preprint (arXiv) policy; MNRAS generally permits arXiv posting.
- If the live official instructions conflict with this skill, the official instructions win.

## Pre-submission self-check

- [ ] One sentence stating why this constitutes a complete, meaningful archival contribution to the field.
- [ ] Systematic and statistical uncertainties are both reported and propagated through to the headline result.
- [ ] Manuscript is formatted with the current mnras.cls LaTeX class file.
- [ ] Abstract states the method and quantitative result concisely.
- [ ] For Letters: manuscript fits within the current length limit and the cover letter justifies urgent publication.

## Common desk-reject triggers

- A Letters submission exceeding the strict length limit without editor pre-approval.
- A paper whose analysis is essentially descriptive (presenting data without interpretation or comparison to models).
- Missing systematic-uncertainty treatment — in survey or photometric work, uncorrected selection effects or calibration issues that make the results unreliable.
- Not using the required MNRAS LaTeX class, causing the manuscript to be returned before review.
- A purely conceptual or speculative paper with no new data, simulation, or methodological content (more appropriate for a review or opinion venue).

## Re-routing decision

- Conceptual advance demanding broad significance narrative for an astronomy audience → `nature-astronomy`.
- AAS-community-focused astrophysics result, or when rapid open-access publication via AAS journals is preferred → `the-astrophysical-journal`.
- Large data product or survey description with minimal per-object analysis → ApJS or a dedicated survey-data venue.

## Output format

```text
[Fit] High / Medium / Low (one-line reason)
[Target] Monthly Notices of the Royal Astronomical Society
[Topic tags] <2–3 closest topics>
[Method/evidence] <does the analysis meet the archival rigor and completeness bar for MNRAS?>
[Top risk] <the single most likely reason for rejection>
[Official items to re-check] <article type / MNRAS LaTeX class / length / Supporting Information / data-code / disclosure>
[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.

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