Agent skill

Ieee Transactions On Power Electronics

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses when targeting IEEE Transactions on Power Electronics (TPEL) or deciding whether a power-conversion manuscript fits this venue.

MITAuto-check passed

Install Ieee Transactions On Power Electronics

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieee-transactions-on-power-electronics -a claude-code

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

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ieee-transactions-on-power-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/ieee-transactions-on-power-electronics .claude/skills/ieee-transactions-on-power-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
ieee-transactions-on-power-electronics
GitHub stars
1.2k
Token cost
~1.9k tokens
SKILL.md length
743 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when targeting IEEE Transactions on Power Electronics (TPEL) or deciding whether a power-conversion manuscript fits this venue.

  • Targeting IEEE Transactions on Power Electronics (TPEL)
  • 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 a power-conversion manuscript fits this venue

What it does

Ieee Transactions On Power Electronics is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting IEEE Transactions on Power Electronics (TPEL) or deciding whether a power-conversion manuscript fits this venue. Encodes the journal's fit, the hardware-validation bar, the converter-and-control scope, the TPEL-vs-TIE routing, house style, 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 IEEE Transactions on Power Electronics (TPEL)
  • Deciding whether a power-conversion manuscript fits this venue

Example prompts

  • “/ieee-transactions-on-power-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

Ieee Transactions On Power Electronics loads about 1.9k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 743 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~89
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). 743 words, ~1,865 tokens.

Download SKILL.mdSave it as .claude/skills/ieee-transactions-on-power-electronics/SKILL.md (or your agent's skills folder).
name
ieee-transactions-on-power-electronics
description
Use when targeting IEEE Transactions on Power Electronics (TPEL) or deciding whether a power-conversion manuscript fits this venue. Encodes the journal's fit, the hardware-validation bar, the converter-and-control scope, the TPEL-vs-TIE routing, house style, official-submission re-check, and desk-reject heuristics.

IEEE Transactions on Power Electronics (ieee-transactions-on-power-electronics)

Journal positioning

IEEE Transactions on Power Electronics (TPEL) is the leading archival venue for power conversion: converter and inverter topologies, motor drives, control of power-electronic systems, magnetics and passive components, wide-bandgap devices in circuits, and power-electronics-enabled energy systems. The defining expectation is a concrete power-conversion advance backed by experimental validation — a topology, modulation, or control method whose benefit (efficiency, power density, reliability, dynamic response) is demonstrated on hardware, not only in simulation. Simulation-only proposals and minor topology permutations without measured benefit are a weak 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 IEEE Transactions on Power Electronics author information and submission system.

When to trigger

  • The author names TPEL for a converter, inverter, drive, or power-electronic-control manuscript and wants a fit/framing check.
  • A design must be re-framed from "we built a converter" into a generalizable power-conversion contribution with measured, benchmarked benefit.
  • The author is choosing between TPEL and ieee-transactions-on-industrial-electronics (broader industrial electronics) or an energy-systems venue.
  • The author needs the hardware-validation bar and desk-reject heuristics specific to power electronics.

Scope & topic fit

  • Converter and inverter topologies: DC-DC, DC-AC, AC-DC, multilevel, resonant, and soft-switching converters with a clear conversion advantage.
  • Modulation and control of power-electronic systems: current/voltage control, model predictive control, stability of grid-tied and standalone converters.
  • Motor drives and electric-machine control from the power-electronics side: drive topologies, modulation, and torque/efficiency performance.
  • Wide-bandgap (SiC/GaN) device application in converters, gate drives, packaging, and thermal management with measured impact.
  • Magnetics, passive components, EMI, and reliability of power-electronic converters; power-electronics interfaces for renewables, storage, and transportation.

Method & evidence bar

  • The contribution is a power-conversion method with experimental validation — a hardware prototype with measured efficiency, power density, thermal, dynamic, or reliability results, typically expected at this venue.
  • Simulation establishes design and operating principles but generally does not substitute for measurement; the absence of any hardware result is a common weakness.
  • Efficiency and performance must be benchmarked against the relevant state-of-the-art topology/control under comparable conditions, with operating points and loss breakdowns reported.
  • Claims (e.g., higher efficiency, lower EMI, better dynamics) must be supported by instrumented measurements with stated test conditions, component ratings, and control parameters.
  • The contribution must generalize beyond one built unit: the design principle, trade-offs, and applicable operating range should be made explicit.

Structure & house style

  • IEEE format; TPEL publishes full Papers and shorter Letters — match scope to the article type and re-check current definitions and limits on the live guide.
  • The introduction motivates the conversion problem and positions against prior topologies/control; the analysis derives the operating principle before the experiment validates it.
  • Figures are central and quantitative: schematics, modulation/control diagrams, measured waveforms, efficiency/loss curves, thermal images, and prototype photos.
  • Hardware specifications (devices, magnetics, switching frequency, power level) must be reported in enough detail to reproduce the result.
Show full SKILL.md (267 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 IEEE Author Center anchors, then cite the current Transactions on Power Electronics page you checked.
  • Search the live site for "IEEE Transactions on Power Electronics information for authors" and follow the current submission-system version.
  • Re-check article types (Paper vs. Letter), length/overlength policy, and the IEEE template.
  • Confirm expectations for experimental validation, measured-data reporting, and any reproducibility requirements.
  • Re-check ORCID, competing-interests, funding, author-contribution, and AI-use disclosure requirements, and IEEE open-access options.
  • If the live official instructions conflict with this skill, the official instructions win.

Pre-submission self-check

  • The contribution is a generalizable power-conversion advance, not a one-off build or a minor topology permutation.
  • A hardware prototype provides measured efficiency/dynamic/thermal/reliability results, not simulation only.
  • Performance is benchmarked against the relevant state-of-the-art topology/control under comparable conditions.
  • Loss breakdowns, operating points, and test conditions are reported.
  • Component ratings, switching frequency, and control parameters are detailed enough to reproduce.
  • Article type (Paper vs. Letter) and length fit current limits.

Common desk-reject triggers

  • Simulation-only converter/control proposal with no experimental validation.
  • A minor topology permutation with no measured efficiency/performance benefit over existing designs.
  • Efficiency claims with no loss breakdown, no benchmark, or under non-comparable test conditions.
  • Results from a single built unit with no generalizable design principle or trade-off analysis.
  • Application/integration paper where power electronics is incidental and no converter-level advance is shown.

Re-routing decision

  • Broader industrial-electronics, drives, or industrial-systems emphasis → ieee-transactions-on-industrial-electronics.
  • Grid/system-level integration rather than the converter → ieee-transactions-on-power-systems.
  • Energy-system performance is the primary narrative → applied-energy.
  • Battery/storage-cell or device materials focus → journal-of-power-sources / energy-storage-materials.
  • Broad tutorial/survey of a power-electronics area → proceedings-of-the-ieee.

Output format

text
[Fit] High / Medium / Low (one-line reason)
[Target] IEEE Transactions on Power Electronics
[Topic tags] <2–3 closest power-electronics subtopics>
[Conversion advance] <the topology/control idea and the metric it improves>
[Hardware validation] <prototype + measured results present? benchmarked?>
[Top risk] <the single most likely reason for rejection>
[Article type] Paper / Letter
[Official items to re-check] <article type / length / experimental-validation / disclosures>
[Re-route suggestion] <if not a fit, a better-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/ieee-transactions-on-power-electronics of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Ieee Transactions On Power 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.

Ieee Transactions On Power Electronics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ieee Transactions On Power Electronics this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.9kAutomated safety check: PassMIT
Desktop ElectronOpenHands/OpenHands91k—~302Automated safety check: PassMIT
Electron App Automationvercel-labs/agent-browser44k5 repos~1.7kAutomated safety check: PassApache-2.0
Electron Developmentdavila7/claude-code-templates33k3 repos~7kAutomated safety check: PassMIT
Statistical PowerK-Dense-AI/scientific-agent-skills48k1 repos~4.4kAutomated safety check: NotesMIT
Powerbergside/awesome-design-skills3.1k—~850Automated 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/…

    91k 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.

    33k GitHub starsUsed in 3 repos~7k tokens
    MobileAuto-check passed
  • Statistical Power

    K-Dense-AI/scientific-agent-skills

    Calculates sample sizes and statistical power for study planning.

    48k GitHub starsUsed in 1 repo~4.4k tokens
    Research & ScienceAuto-check: notes
  • Power

    bergside/awesome-design-skills

    High-end dark aesthetic with bold headings, monochromatic palette, and premium feel for premium brand experiences.

    3.1k GitHub stars~850 tokensUpdated 3 mo ago
    Frontend & DesignAuto-check passed
  • Official

    Govern Power Automate flows and Power Apps at scale using the FlowStudio MCP cached store.

    40k GitHub starsUsed in 2 repos~3.6k tokens
    DevelopmentAuto-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 14 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 14 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 14 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 14 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 14 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 14 days ago
    Auto-check passed

Questions about Ieee Transactions On Power Electronics

What does Ieee Transactions On Power Electronics do?

A skill your agent uses when targeting IEEE Transactions on Power Electronics (TPEL) or deciding whether a power-conversion manuscript fits this venue. Ieee Transactions On Power Electronics is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting IEEE Transactions on Power Electronics (TPEL) or deciding whether a power-conversion manuscript fits this venue.

When should I use Ieee Transactions On Power Electronics?

Ieee Transactions On Power Electronics fits situations like: targeting IEEE Transactions on Power Electronics (TPEL); deciding whether a power-conversion manuscript fits this venue.

How do I install Ieee Transactions On Power Electronics in Claude Code?

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

How do I install Ieee Transactions On Power Electronics in Codex?

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

Can I use Ieee Transactions On Power 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 ieee-transactions-on-power-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/ieee-transactions-on-power-electronics, .gemini/skills/ieee-transactions-on-power-electronics, .github/skills/ieee-transactions-on-power-electronics and .opencode/skills/ieee-transactions-on-power-electronics in your project.

What does Ieee Transactions On Power Electronics need to run?

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

Does Ieee Transactions On Power 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 Ieee Transactions On Power 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 Ieee Transactions On Power Electronics use?

Ieee Transactions On Power 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 Ieee Transactions On Power Electronics use?

About 1.9k tokens (SKILL.md is roughly 7.5k 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 Ieee Transactions On Power Electronics?

Skills that share tags, products or a category with Ieee Transactions On Power Electronics: Desktop Electron (OpenHands/OpenHands, 91k stars), Electron App Automation (vercel-labs/agent-browser, 44k stars), Electron Development (davila7/claude-code-templates, 33k stars) and Statistical Power (K-Dense-AI/scientific-agent-skills, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ieee Transactions On Power Electronics?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.