A skill your agent uses when targeting Nature Electronics or deciding whether an electronic-devices / circuits / systems manuscript fits this venue.

MITAuto-check passed

Install Nature Electronics

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nature-electronics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nature-electronics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Engineering-Technology-Journal-Skills/skills/nature-electronics .claude/skills/nature-electronics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nature-electronics
GitHub stars
1.2k
Token cost
~1.9k tokens
SKILL.md length
788 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when targeting Nature Electronics or deciding whether an electronic-devices / circuits / systems manuscript fits this venue.

  • Targeting Nature Electronics
  • SKILL.md covers Journal positioning, When to trigger, Scope & topic fit and Method & evidence bar, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Deciding whether an electronic-devices / circuits / systems manuscript fits this venue

What it does

Nature Electronics is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting Nature Electronics or deciding whether an electronic-devices / circuits / systems manuscript fits this venue. Encodes the journal's fit, the Nature-style significance and field-advancing bar, device-and-system measurement rigor, house style, the device-vs-materials-vs-systems routing, official-submission re-check, and desk-reject heuristics.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. | 覆盖主流期刊的… The licence is MIT.

When your agent uses it

  • Targeting Nature Electronics
  • Deciding whether an electronic-devices / circuits / systems manuscript fits this venue

Example prompts

  • “/nature-electronics”

What it can do on your machine

Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nature Electronics loads about 1.9k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 788 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~95
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 788 words, ~1,939 tokens.

Download SKILL.mdSave it as .claude/skills/nature-electronics/SKILL.md (or your agent's skills folder).
name
nature-electronics
description
Use when targeting Nature Electronics or deciding whether an electronic-devices / circuits / systems manuscript fits this venue. Encodes the journal's fit, the Nature-style significance and field-advancing bar, device-and-system measurement rigor, house style, the device-vs-materials-vs-systems routing, official-submission re-check, and desk-reject heuristics.

Nature Electronics (nature-electronics)

Journal positioning

Nature Electronics is the Nature Portfolio journal covering the science and engineering of electronics — from materials-level device physics through circuits to integrated systems and their applications. It selects for broad significance and a field-advancing result framed in the Nature style: a conceptual breakthrough, a new device or material with a clear performance or functional leap, or a system that demonstrates a genuinely new capability. An incremental device that improves a metric without a conceptual or capability advance, or a process tweak with no broader consequence, is a poor fit. This skill is a fit / venue-selection / re-framing tool. It does not replace the journal's current official author guidelines. Before submitting, re-check the live Nature Electronics submission guidelines on the Nature Portfolio site.

When to trigger

  • The author names Nature Electronics for an electronic-devices, circuits, or systems result and wants a fit/framing and significance check.
  • A device or systems result must be re-framed from a metric-improvement report into a Nature-style, field-advancing significance narrative.
  • The author is choosing between Nature Electronics and nature-materials / nature-communications, or an IEEE device/circuits transactions venue.
  • The author needs Nature Electronics' significance bar and its desk-reject heuristics.

Scope & topic fit

  • Device physics and emerging devices: transistors, memristors, 2D-material and organic/flexible electronics, spintronic and neuromorphic devices, when a new mechanism or capability is shown.
  • Integrated circuits and computing hardware: low-power, in-memory, analog, and domain-specific architectures with a demonstrated, broadly significant advance.
  • Sensors, flexible/wearable and bioelectronic systems where a new device concept enables a capability not previously achievable.
  • Power, RF, photonic-electronic, and quantum-electronic devices and systems with a field-moving result rather than parameter optimization.
  • Fabrication and integration advances (heterogeneous integration, new process schemes) when they unlock new device or system function, not just yield.
  • System-level demonstrations that bridge from device physics to a working integrated capability with measured performance.

Method & evidence bar

  • The contribution must carry an explicit significance argument: what is conceptually or functionally new and why it advances electronics broadly.
  • Device and system metrics must be quantitative and rigorously measured: report conditions, statistics across multiple devices, variability/yield where relevant, and uncertainty — not a single best-device datapoint.
  • Performance and capability claims must be benchmarked against the current state of the art under comparable, clearly stated conditions.
  • Reliability, stability, and scalability/manufacturability should be addressed honestly where they bear on the claimed advance, not deferred entirely.
  • Theory, modeling, and simulation must be tied to measured devices or make tested predictions; simulation-only device claims rarely clear the bar.
  • Reproducibility and reporting follow Nature-Portfolio expectations: methods, data availability, and statistics sufficient to reproduce key results.

Structure & house style

  • Nature-Portfolio article structure with a significance-forward abstract and introduction; re-check current article types and length/format on the live guide.
  • The introduction establishes the broad-significance gap and the stakes for electronics before the technical development, in accessible language.
  • Main display items are curated and load-bearing: device characteristics with statistics, benchmark comparisons, and clear schematics of the device/system concept.
  • Methods and extended/supplementary material carry full fabrication, measurement, and device-statistics detail; the main narrative must stand on the headline figures.
  • Multi-device statistics and variability data are expected in support, not optional afterthoughts.
Show full SKILL.md (270 more words)Show less

Official-submission checklist

  • Before giving submission-ready advice, read ../../resources/source-basis.md and ../../resources/official-source-map.md; start from the Nature-Portfolio anchors, then cite the current Nature Electronics guidelines page you checked.
  • Search the live site for "Nature Electronics submission guidelines" and follow the current Nature-Portfolio submission system.
  • Re-check article types (Article, Letter/short formats), length/format expectations, and the abstract requirements.
  • Confirm data-availability, code-availability, and reporting-summary requirements of Nature Portfolio.
  • Re-check open-access options, ORCID, competing-interests, funding, author-contribution, and AI-use disclosure requirements.
  • If the live official instructions conflict with this skill, the official instructions win.

Pre-submission self-check

  • The abstract/introduction states the broad significance and the field-advancing claim in Nature style.
  • The advance is conceptual or capability-level, not an incremental metric improvement.
  • Device/system metrics include multi-device statistics, variability, and uncertainty — not a single best device.
  • Performance is benchmarked against the state of the art under comparable conditions.
  • Reliability/scalability/manufacturability are addressed where they bear on the claim.
  • Any theory/simulation is anchored to measured devices or makes a tested prediction.

Common desk-reject triggers

  • Incremental device with a metric improvement but no conceptual or capability leap.
  • Single best-device result with no multi-device statistics or variability data.
  • Performance claims not benchmarked, or compared to a weak/non-comparable reference.
  • Process or fabrication tweak with improved yield but no new device/system function.
  • Simulation-only device claim with no fabricated, measured device.
  • Specialty-scoped engineering result better suited to a focused device/circuits journal.

Re-routing decision

  • Advance driven primarily by a new electronic material → nature-materials / advanced-materials.
  • Broad cross-disciplinary significance beyond electronics → nature-communications / science-advances.
  • Photonic-electronic or integrated-photonics emphasis → nature-photonics / light-science-and-applications / optica.
  • Specialty device, circuit, or process result → an IEEE device/circuits/electron-devices transactions venue.
  • Bioelectronic system with biomedical significance and validation → nature-biomedical-engineering.

Output format

text
[Fit] High / Medium / Low (one-line reason)
[Target] Nature Electronics
[Topic tags] <2–3 closest device/circuit/system subtopics>
[Significance statement] <the Nature-style field-advancing claim in one line>
[Method/evidence] <do device/system metrics + statistics + benchmarking clear the significance + rigor bar?>
[Top risk] <the single most likely reason for rejection>
[Official items to re-check] <article type / data & code availability / reporting summary / OA / disclosures>
[Re-route suggestion] <if incremental or better framed elsewhere, a matched venue>

© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in Engineering-Technology-Journal-Skills/skills/nature-electronics of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Nature Electronics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nature Electronics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nature Electronics this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.9kAutomated safety check: PassMIT
Desktop ElectronOpenHands/OpenHands90k—~302Automated safety check: PassMIT
Electron App Automationvercel-labs/agent-browser44k5 repos~1.7kAutomated safety check: PassApache-2.0
Electron Developmentdavila7/claude-code-templates32k3 repos~7kAutomated safety check: PassMIT
Use Vishot With Electronmoeru-ai/airi50k—~1.7kAutomated safety check: PassMIT
Agent Browser Electronmoeru-ai/airi50k—~3.1kAutomated safety check: PassMIT

Similar skills

  • Desktop Electron

    OpenHands/OpenHands

    This skill should be used when the user asks to "change the desktop app", "package Electron", "build a universal macOS app", "bundle Node or uv", "fix Electron startup", or changes electron/…

    90k GitHub stars~302 tokensUpdated today
    Auto-check passed
  • Electron App Automation

    vercel-labs/agent-browser

    Official

    Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.

    44k GitHub starsUsed in 5 repos~1.7k tokens
    Productivity & AutomationAuto-check passed
  • Electron Development

    davila7/claude-code-templates

    Master Electron desktop app development with secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update.

    32k GitHub starsUsed in 3 repos~7k tokens
    MobileAuto-check passed
  • Capture deterministic Electron windows with Vishot. An agent skill from moeru-ai/airi.

    50k GitHub stars~1.7k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • A skill your agent uses when Codex needs to inspect, debug, or automate an Electron app through agent-browser and Chrome DevTools Protocol, especially when the app has multiple BrowserWindow…

    50k GitHub stars~3.1k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Electron Drive Skill

    sickn33/agentic-awesome-skills

    Launch the project's Electron app on a scratch profile and drive it: click, type, screenshot, run renderer or main-process code, read logs.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Testing & QAAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo
  • Aaag Data Analysis

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…

    1.2k GitHub stars~1.3k tokensUpdated 12 days ago
    Auto-check passed
  • Aaag Literature Positioning

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…

    1.2k GitHub stars~1.3k tokensUpdated 12 days ago
    Auto-check passed
  • Aaag Rebuttal

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…

    1.2k GitHub stars~1.4k tokensUpdated 12 days ago
    Auto-check passed
  • Aaag Research Design

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…

    1.2k GitHub stars~1.4k tokensUpdated 12 days ago
    Auto-check passed
  • Aaag Review Process

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…

    1.2k GitHub stars~1.3k tokensUpdated 12 days ago
    Auto-check passed
  • Aaag Submission

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…

    1.2k GitHub stars~1.6k tokensUpdated 12 days ago
    Auto-check passed

Questions about Nature Electronics

What does Nature Electronics do?

A skill your agent uses when targeting Nature Electronics or deciding whether an electronic-devices / circuits / systems manuscript fits this venue. Nature Electronics is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting Nature Electronics or deciding whether an electronic-devices / circuits / systems manuscript fits this venue.

When should I use Nature Electronics?

Nature Electronics fits situations like: targeting Nature Electronics; deciding whether an electronic-devices / circuits / systems manuscript fits this venue.

How do I install Nature Electronics in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nature-electronics -a claude-code`. Or copy the skill folder (Engineering-Technology-Journal-Skills/skills/nature-electronics in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/nature-electronics in your project. Claude Code loads it when a task matches its description.

How do I install Nature Electronics in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nature-electronics -a codex`. Or copy the skill folder (Engineering-Technology-Journal-Skills/skills/nature-electronics in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/nature-electronics in your project. Codex loads it when a task matches its description.

Can I use Nature Electronics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nature-electronics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nature-electronics, .gemini/skills/nature-electronics, .github/skills/nature-electronics and .opencode/skills/nature-electronics in your project.

What does Nature Electronics need to run?

SKILL.md names no scripts, command-line tools or credentials: Nature Electronics is instructions for the agent only.

Does Nature Electronics access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nature Electronics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Nature Electronics use?

Nature Electronics is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nature Electronics use?

About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nature Electronics?

Skills that share tags, products or a category with Nature Electronics: Desktop Electron (OpenHands/OpenHands, 90k stars), Electron App Automation (vercel-labs/agent-browser, 44k stars), Electron Development (davila7/claude-code-templates, 32k stars) and Use Vishot With Electron (moeru-ai/airi, 50k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nature Electronics?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.

Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.