submission-readiness

submission-readiness is a skill for Claude Code from jeonnoin-alt/Eureka. It costs 34 tokens per session (2,171 once invoked), scanned A, original, MIT.

A research-completion checklist and decision guide for choosing what to do with finished work. It verifies evidence and publication requirements before helping decide between journal submission, sharing a preprint, further refinement, or changing direction.

In plain words
What is it for?
Checking publication gates, assessing readiness, presenting next-step options, carrying out the selected path, and recording the decision.
Why use it?
It replaces a premature submission decision with checks for missing evidence, claims, novelty, review quality, and fit between the work and the intended venue.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the Eureka plugin — 16 skills, 1 agent, 1 hook shipped together

Good fit Checking publication gates, assessing readiness, presenting next-step options, carrying out the selected path, and recording the decision.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeonnoin-alt/eureka/submission-readiness
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jeonnoin-alt/Eureka --skill submission-readiness
Clone the repo
git clone --depth 1 https://github.com/jeonnoin-alt/Eureka

Made for: Claude Code.

Or install Eureka, the plugin that ships this one along with the rest of its 16 skills, 1 agent, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for submission-readiness

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeonnoin-alt/eureka/submission-readiness/github.svg)](https://agentmods.dev/skills/jeonnoin-alt/eureka/submission-readiness)
Your own site
<a href="https://agentmods.dev/skills/jeonnoin-alt/eureka/submission-readiness"><img src="https://agentmods.dev/badge/skills/jeonnoin-alt/eureka/submission-readiness/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for submission-readiness

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeonnoin-alt/eureka/submission-readiness"><img src="https://agentmods.dev/badge/skills/jeonnoin-alt/eureka/submission-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,171 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.02171
Opus 5 $0.00017 $0.01086
Sonnet 5 $0.00007 $0.00434
Haiku 4.5 $0.00003 $0.00217

Measured 12d ago against content hash 78bc72147dd4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

submission-readiness scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/submission-readiness/SKILL.md · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Submission Readiness

Overview

Guide completion of research work by verifying publication gates, then presenting clear options and handling the chosen path.

Core principle: Verify evidence → Present options → Execute choice → Document decision.

Announce at start: "I'm using the submission-readiness skill to evaluate next steps."

The Process

Step 1: Verify Prerequisites

Before presenting options, verify all gates pass:

  • eureka:novelty-competitive-audit: PASS? Internal rigor gates (below) don't check external competitiveness. This gate catches preemption — the most common desk-reject reason — before submission. See docs/references/novelty-audit-guide.md.
  • eureka:verification-before-publication checklist: PASS?
  • eureka:research-reviewer score at target threshold (≥95 for pre-submission): PASS?
  • eureka:claims-audit: PASS?
  • Venue-specific framing tuned? Confirm explicitly: does the manuscript's contribution altitude match the target venue's expected altitude? See docs/references/narrative-guide.md section "Venue-specific altitude tuning" for the altitude guide. A Nature-family contribution altitude paired with specialty-journal-tier evidence is a desk-reject risk; the inverse (specialty-journal pitch for Nature-tier evidence) undersells. If the user has not explicitly tuned framing to the target venue (or target venue changed since brainstorming), flag this gate as FAIL before proceeding.

Freshness verification (canonical output paths, v1.10.0):

Each upstream artifact writes to docs/eureka/<subdir>/YYYY-MM-DD-<kind>.md with YAML frontmatter including manuscript_hash, results_hash, and status. For each prerequisite above, read the latest artifact in the corresponding canonical path and verify:

Prerequisite Canonical path Freshness check
novelty-competitive-audit docs/eureka/novelty-audits/ latest file status: passed AND manuscript_hash matches current manuscript
verification-before-publication docs/eureka/verifications/ latest file status: passed AND hashes current
research-reviewer docs/eureka/reviews/ latest file score ≥ 95 AND hashes current
claims-audit docs/eureka/audits/ latest file status: passed AND hashes current

Read the full file on GitHub · 215 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 215 lines · 34 tokens per session scan A 78bc72147dd4

Subscribe to this mod's changes

submission-readiness is a skill published in the GitHub repository jeonnoin-alt/Eureka (2 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 2,171 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

chief-strategy-officer

Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…

cbrock84/headcount · 93 tokens

seo-strategy

Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…

cbrock84/headcount · 74 tokens

financial-statement-analysis

Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…

cbrock84/headcount · 93 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens

youtube-producer

Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…

cbrock84/headcount · 86 tokens

estimating-and-contingency

Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…

cbrock84/headcount · 87 tokens