en-engtech-journal-workflow
Use when deciding which English engineering / technology journal skill to invoke next, comparing fit across the 40-journal engineering roadmap, or routing a manuscript before venue-specific re-framing. Routes by engineering sub-discipline, contribution type (theory vs. method vs. system vs. device), and validation shape (proof / simulation / bench experiment / field deployment).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-engtech-journal-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Engineering & technology journal workflow (en-engtech-journal-workflow) ## Purpose This is the routing skill for the engineering bundle. It does not replace a single-journal profile; it first classifies the manuscript by **engineering sub-discipline, contribution type, and validation shape**, then routes into the matching per-journal skill for fit and re-framing. It is a sibling to `en-natsci-journal-workflow` (natural science) and `en-journal-workflow` (econ/finance/management). ## Ask four things first 1. **Sub-discipline:** electrical/EECS, control, communications/information theory, signal processing, power/energy systems, robotics, photonics/optics, electronics devices, biomedical engineering, mechanics/solids, fluids, manufacturing, aerospace, chemical/process engineering, energy conversion/storage, materials engineering, or civil/transportation? 2. **Contribution type:** a theorem/bound, a new algorithm/method, a system or architecture, a device/material with measured performance, a tutorial/survey, or a design methodology? 3. **Validation shape:** mathematical proof, numerical simulation, controlled bench experiment, hardware prototype, pilot/field deployment, or standard
- Purpose
- Ask four things first
- Quick routing
- Sibling-journal disambiguation
- Decision rules
- Output format
What does the en-engtech-journal-workflow skill do?
Use when deciding which English engineering / technology journal skill to invoke next, comparing fit across the 40-journal engineering roadmap, or routing a manuscript before venue-specific re-framing. Routes by engineering sub-discipline, contribution type (theory vs. method vs. system vs. device), and validation shape (proof / simulation / bench experiment / field deployment).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-engtech-journal-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.