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

Elife

ASecurity

Use when targeting eLife or deciding whether a life-sciences manuscript fits this open-access venue. Encodes eLife's unique Reviewed-Preprint model, 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-agentsgogitdatabase

Works with

cli

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Elife?

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

Security grade badge for Elife
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-elife/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-elife)

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

Download with Pro
Files
SKILL.md
---
name: elife
description: Use when targeting eLife or deciding whether a life-sciences manuscript fits this open-access venue. Encodes eLife's unique Reviewed-Preprint model, fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
---

# eLife (elife)

## Journal positioning

eLife is a non-profit open-access journal covering all of life sciences and biomedicine, operated by an independent board and funded by major research foundations. Its defining structural feature is the **Reviewed-Preprint model**: most submissions are posted as preprints on bioRxiv and receive a public eLife assessment plus full peer-review reports — the journal does not issue a binary accept/reject decision in the traditional sense. The eLife assessment uses a controlled vocabulary (landmark, fundamental, important, valuable, useful, incomplete, inadequate) to characterize significance and evidential strength. The readership is the global life-sciences research community, and the ethos strongly favors rigor, reproducibility, transparency, and open science over prestige signaling. 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 elifesciences.org.

## When to trigger

- The author names eLife as the target venue or is considering an open-access life-sciences outlet with public peer review.
- A manuscript is strong on rigor and reproducibility but may not carry the single-advance framing required by Nature/Cell flagship journals.
- The author wants the manuscript posted as a preprint and reviewed publicly, with transparent reviewer reports and eLife assessments visible to readers.
- The author needs guidance on eLife's Reviewed-Preprint workflow, assessment vocabulary, and what determines a "featured" eLife paper.

## Scope & topic fit

- All areas of life sciences and biomedicine: cell biology, developmental biology, neuroscience, evolutionary biology, genetics/genomics, structural biology, microbiology, immunology, computational biology, and clinical/translational work.
- Methods and resources: new tools, datasets, or software with demonstrated utility in life-sciences research are explicitly welcomed as a first-class article type.
- Negative results, replication studies, and resource papers are more welcome here than at flagship journals — eLife's ethos explicitly values rigor over novelty hype; the assessment vocabulary rewards evidential strength independent of whether results are positive.
- Quantitative and computational biology, biophysics, and cross-disciplinary work that does not fit a single specialty journal.
- Review and opinion content is published but typically commissioned; editors select topics where a synthesis would serve the community — unsolicited reviews should be proposed before full preparation.

## Method & evidence bar

- eLife assesses **evidential strength** explicitly using its assessment vocabulary: claims must be matched by appropriate experimental or computational evidence; overclaiming relative to evidence is a primary editorial concern and results in a lower significance or strength rating.
- Reproducibility practices are expected: data deposition (raw data, processed data), code availability, detailed methods — eLife pushes authors toward full transparency more forcefully than most traditional journals.
- Statistical rigor: pre-registration is not mandatory but is valued; sample sizes must be justified; effect sizes and confidence intervals preferred over significance thresholds alone.
- For animal studies, ARRIVE reporting guidelines apply; for human studies, CONSORT/STROBE as appropriate and ethics declarations.
- Revised manuscripts under the Reviewed-Preprint model are re-assessed publicly; the revision letter and author response are posted alongside the paper.
- The assessment distinguishes significance (landmark → important → valuable → useful) from evidential strength (exceptional → compelling → convincing → inadequate) independently — authors should calibrate which dimension their manuscript excels on.

## Structure & house style

- eLife uses a structured-summary abstract format (editor's evaluation is posted separately; author's abstract is standard unstructured).
- Article types include Research Articles, Short Reports, Tools and Resources, Research Advances, Feature Articles, and Reviews — each has distinct scope expectations (verify current definitions on the live site).
- The **eLife digest** (plain-language summary for a non-specialist audience) is expected with most research articles; it is public-facing.
- Figures should be publication-ready and accompanied by source data files (underlying numerical data for each panel).
- The public peer-review reports and author responses form part of the published record — draft the response letter with this in mind from submission.

## 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 "eLife author guide" or "eLife submission process" and follow the current version at elifesciences.org.
- Re-check the current Reviewed-Preprint model workflow, including preprint posting consent, assessment timeline, and the distinction between "eLife Reviewed Preprint" and a "Version of Record."
- Confirm data deposition requirements: raw data, processed data, and code repositories (Zenodo, GitHub, Dryad, GEO, SRA, RCSB, etc.) expected before publication.
- Check reporting guidelines: ARRIVE (animal), CONSORT/STROBE (clinical), MIQE (qPCR), or other community standards relevant to the study type.
- Verify open-access licensing (eLife publishes under CC-BY), funding and competing-interests disclosure, and AI-use policy.
- If the live official instructions conflict with this skill, the official instructions win.

## Pre-submission self-check

- [ ] One sentence matching the claimed significance level ("landmark," "fundamental," "important," or "valuable") to the actual evidence presented — do not overstate.
- [ ] All raw data, processed data, and analysis code are deposited or will be deposited, with accession numbers/links ready.
- [ ] The eLife digest is drafted and accessible to a scientifically literate non-specialist.
- [ ] The manuscript is posted or is ready to be posted as a preprint (bioRxiv or equivalent); consent for public posting is confirmed.
- [ ] Reporting guidelines relevant to the study type have been applied and a checklist is ready.

## Common desk-reject triggers

- Scope entirely outside life sciences or biomedicine (physics, chemistry without biological application, social science).
- Manuscripts where the significance claim is drastically mismatched with evidential strength — editors use the assessment vocabulary to flag this explicitly.
- Clinical trials or large-scale human studies without the appropriate reporting compliance (registration, CONSORT, ethics).
- Refusal to post a preprint or to participate in the Reviewed-Preprint workflow may affect routing (verify current policy on whether non-preprint submissions are accepted).
- Studies reporting software or databases without working, documented, publicly accessible code/data.

## Re-routing decision

- Flagship-level conceptual advance across life sciences → `nature`, `science`, `cell`, or `pnas`.
- Open-access general biology with a more pronounced methods/transparency culture → `plos-biology`.
- Genomics or computational biology focus → `genome-biology`.
- Neuroscience with field-leading conceptual advance → `nature-neuroscience` or `neuron`.

## Output format

```text
[Fit] High / Medium / Low (one-line reason)
[Target] eLife
[Topic tags] <2–3 closest topics>
[Method/evidence] <does the evidential strength match the claimed significance level per eLife's assessment vocabulary?>
[Top risk] <the single most likely reason for rejection or a weak assessment>
[Official items to re-check] <Reviewed-Preprint workflow / data deposition / reporting checklist / digest / CC-BY / ethics>
[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 →