Agent skill

Ieee Transactions On Power Systems

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

A skill your agent uses when targeting IEEE Transactions on Power Systems (TPWRS) or deciding whether an electric-power-systems manuscript fits this venue.

MITAuto-check passed

Install Ieee Transactions On Power Systems

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieee-transactions-on-power-systems -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-systems --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-systems .claude/skills/ieee-transactions-on-power-systems && 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-systems
GitHub stars
1.2k
Token cost
~1.9k tokens
SKILL.md length
771 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 Systems (TPWRS) or deciding whether an electric-power-systems manuscript fits this venue.

  • Targeting IEEE Transactions on Power Systems (TPWRS)
  • 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 electric-power-systems manuscript fits this venue

What it does

Ieee Transactions On Power Systems is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when targeting IEEE Transactions on Power Systems (TPWRS) or deciding whether an electric-power-systems manuscript fits this venue. Encodes the journal's fit, the methodology-plus-case-study bar, the standard-test-system expectation, the power-system-vs-power-electronics 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 Systems (TPWRS)
  • Deciding whether an electric-power-systems manuscript fits this venue

Example prompts

  • “/ieee-transactions-on-power-systems”

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 Systems loads about 1.9k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 771 words of instructions outside code blocks.

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

Download SKILL.mdSave it as .claude/skills/ieee-transactions-on-power-systems/SKILL.md (or your agent's skills folder).
name
ieee-transactions-on-power-systems
description
Use when targeting IEEE Transactions on Power Systems (TPWRS) or deciding whether an electric-power-systems manuscript fits this venue. Encodes the journal's fit, the methodology-plus-case-study bar, the standard-test-system expectation, the power-system-vs-power-electronics routing, house style, official-submission re-check, and desk-reject heuristics.

IEEE Transactions on Power Systems (ieee-transactions-on-power-systems)

Journal positioning

IEEE Transactions on Power Systems (TPWRS) is the leading archival venue for electric power systems engineering: grid operation and planning, power flow and optimal power flow, stability and dynamics, electricity markets, reliability, and the integration of renewables, storage, and demand response at system scale. The defining expectation is a system-level methodological contribution validated on credible case studies — a new model, algorithm, or analysis whose value is shown on standard test systems or realistic networks against meaningful baselines. Component-level device work, power-electronics circuit design, or generic optimization with a thin power-system wrapper are 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 IEEE Transactions on Power Systems author information and submission system.

When to trigger

  • The author names TPWRS for a grid-operation, planning, market, or stability manuscript and wants a fit/framing check.
  • A method must be re-framed from "we ran an optimization" into a power-system contribution validated on standard test systems with the right baselines.
  • The author is choosing between TPWRS and ieee-transactions-on-power-electronics (converter-level) or an energy-systems venue (applied-energy).
  • The author needs the methodology-plus-case-study bar and desk-reject heuristics specific to power systems.

Scope & topic fit

  • Power-system operation: economic dispatch, unit commitment, optimal power flow, security-constrained operation, and real-time/look-ahead scheduling.
  • Planning and expansion: generation, transmission, and storage planning under uncertainty; reliability and resilience assessment.
  • Stability and dynamics: transient, small-signal, voltage, and frequency stability; wide-area monitoring and control; inverter-dominated grid dynamics.
  • Electricity markets and economics: market design, pricing, bidding, and the coupling of markets with physical operation.
  • Renewable, storage, demand-response, and electric-vehicle integration; distribution systems, microgrids, and the transmission–distribution interface at system scale.

Method & evidence bar

  • The contribution is a system-level method — model, algorithm, or analysis — whose correctness and value are demonstrated on standard IEEE test systems or realistic network data, not on a toy two-bus example alone.
  • Case studies must compare against meaningful baselines (existing formulations or solvers) and report computational performance, optimality/feasibility, and scalability where relevant.
  • Modeling assumptions (network model, uncertainty representation, time resolution) must be explicit and defensible; results must be reproducible from the described data and parameters.
  • For optimization or learning methods, the power-system formulation and constraints (physical, security, market) must be central — not a generic solver applied to a relabeled problem.
  • Stability/dynamics claims require appropriate models and validation; statistical or data-driven results need adequate sampling and out-of-sample evaluation.

Structure & house style

  • IEEE format; TPWRS 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 power-system problem and positions against prior formulations; the model and assumptions are stated precisely before the method.
  • Figures and tables are quantitative: single-line diagrams, convergence and cost/feasibility tables, time-series of operation, and scalability comparisons on named test systems.
  • Test-system identity, data sources, and solver/parameter settings should be reported in enough detail to reproduce the case studies.
Show full SKILL.md (278 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 Systems page you checked.
  • Search the live site for "IEEE Transactions on Power Systems 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 data/code-availability expectations and any test-system/data-sharing norms for reproducible case studies.
  • 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 system-level method (model/algorithm/analysis), not a component or circuit-level result.
  • Case studies use standard test systems or realistic network data, not a toy example alone.
  • Baselines are meaningful (existing formulations/solvers), with computation, optimality/feasibility, and scalability reported.
  • The power-system formulation and constraints are central, not a generic solver on a relabeled problem.
  • Modeling assumptions and data/parameters are explicit and reproducible.
  • Article type (Paper vs. Letter) and length fit current limits.

Common desk-reject triggers

  • A generic optimization or machine-learning method with only a thin power-system wrapper and no power-specific formulation.
  • Validation on a toy example only, with no standard test system or realistic network.
  • Missing or unfair baselines, or no reporting of computation/scalability for a method that claims to be practical.
  • Component-level or power-electronics circuit work that belongs at the converter venue.
  • Stability/market claims with inadequate models, sampling, or out-of-sample evaluation.

Re-routing decision

  • Converter/inverter/drive circuit-level contribution → ieee-transactions-on-power-electronics.
  • Broader energy-system or techno-economic analysis → applied-energy.
  • Control theorem about a dynamical system, not grid-specific → ieee-transactions-on-automatic-control / automatica.
  • Storage-cell, battery, or materials focus → journal-of-power-sources / energy-storage-materials.
  • Broad tutorial/survey of a power-systems area → proceedings-of-the-ieee.

Output format

text
[Fit] High / Medium / Low (one-line reason)
[Target] IEEE Transactions on Power Systems
[Topic tags] <2–3 closest power-systems subtopics>
[Method + validation] <the system-level method and the test systems it is shown on>
[Baselines + scalability] <meaningful baselines? computation/scalability reported?>
[Top risk] <the single most likely reason for rejection>
[Article type] Paper / Letter
[Official items to re-check] <article type / length / data-code / 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-systems of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Ieee Transactions On Power Systems 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 Systems compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ieee Transactions On Power Systems this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.9kAutomated 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
Flowstudio Power Automate Governancegithub/awesome-copilot40k2 repos~3.6kAutomated safety check: PassMIT
Power Bi Performance Troubleshootinggithub/awesome-copilot40k1 repos~2.6kAutomated safety check: PassMIT
Touch Targetsthedaviddias/Front-End-Checklist74k—~938Automated safety check: PassMIT

Similar skills

  • 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
  • Official

    Systematic Power BI performance troubleshooting prompt for identifying, diagnosing, and resolving performance issues in Power BI models, reports, and queries.

    40k GitHub starsUsed in 1 repo~2.6k tokens
    Data & AnalyticsAuto-check passed
  • Touch Targets

    thedaviddias/Front-End-Checklist

    A skill your agent uses when applies to all interactive elements on touchscreen interfaces: buttons, links, checkboxes, radio buttons, form inputs, icon buttons, and menu items.

    74k GitHub stars~938 tokensUpdated 5 days ago
    MobileAuto-check passed
  • Power Platform Architect

    github/awesome-copilot

    Official

    A skill your agent uses when the user needs to transform business requirements, use case descriptions, or meeting transcripts into a technical Power Platform solution architecture, including…

    40k GitHub starsUsed in 1 repo~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 Systems

What does Ieee Transactions On Power Systems do?

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

When should I use Ieee Transactions On Power Systems?

Ieee Transactions On Power Systems fits situations like: targeting IEEE Transactions on Power Systems (TPWRS); deciding whether an electric-power-systems manuscript fits this venue.

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

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

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

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

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

What does Ieee Transactions On Power Systems need to run?

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

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

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

Skills that share tags, products or a category with Ieee Transactions On Power Systems: Statistical Power (K-Dense-AI/scientific-agent-skills, 48k stars), Power (bergside/awesome-design-skills, 3.1k stars), Flowstudio Power Automate Governance (github/awesome-copilot, 40k stars) and Power Bi Performance Troubleshooting (github/awesome-copilot, 40k 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 Systems?

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.