Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
Agent skill
En Engtech Journal Workflow
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when deciding which English engineering / technology journal skill to invoke next, comparing fit across the 40-journal engineering roadmap, or routing a manuscript before…
Install En Engtech Journal Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-engtech-journal-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills en-engtech-journal-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/en-engtech-journal-workflow .claude/skills/en-engtech-journal-workflow && rm -rf skills-srcUse ~/.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/
Install the "en-engtech-journal-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow into .claude/skills/en-engtech-journal-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "en-engtech-journal-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-engtech-journal-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills en-engtech-journal-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow .agents/skills/en-engtech-journal-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "en-engtech-journal-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow into .agents/skills/en-engtech-journal-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "en-engtech-journal-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-engtech-journal-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills en-engtech-journal-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow .cursor/skills/en-engtech-journal-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "en-engtech-journal-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow into .cursor/skills/en-engtech-journal-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "en-engtech-journal-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-engtech-journal-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills en-engtech-journal-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow .gemini/skills/en-engtech-journal-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "en-engtech-journal-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow into .gemini/skills/en-engtech-journal-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "en-engtech-journal-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills en-engtech-journal-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-engtech-journal-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow .github/skills/en-engtech-journal-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "en-engtech-journal-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow into .github/skills/en-engtech-journal-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "en-engtech-journal-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-engtech-journal-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills en-engtech-journal-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow .opencode/skills/en-engtech-journal-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "en-engtech-journal-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow into .opencode/skills/en-engtech-journal-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "en-engtech-journal-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
en-engtech-journal-workflow- GitHub stars
- 1.2k
- Token cost
- ~2k tokens
- SKILL.md length
- 631 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding which English engineering / technology journal skill to invoke next, comparing fit across the 40-journal engineering roadmap, or routing a manuscript before…
- Works in 4 steps: Sub-discipline: electrical/EECS,… → Contribution type: a theorem/bound, a… → Validation shape: mathematical proof,… → …
- Deciding which English engineering / technology journal skill to invoke next
- SKILL.md covers Purpose, Ask four things first, Quick routing and Sibling-journal disambiguation, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
En Engtech Journal Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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).
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud. 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
- Deciding which English engineering / technology journal skill to invoke next
- Comparing fit across the 40-journal engineering roadmap
- Routing a manuscript before venue-specific re-framing
Example prompts
- “/en-engtech-journal-workflow”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Sub-discipline: electrical/EECS, control, communications/information theory,
- Contribution type: a theorem/bound, a new algorithm/method, a system or
- Validation shape: mathematical proof, numerical simulation, controlled bench
- Audience breadth: the whole field (Proceedings of the IEEE, a Nature
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
En Engtech Journal Workflow loads about 2k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 631 words of instructions outside code blocks.
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). 631 words, ~1,980 tokens.
Download SKILL.mdSave it as
.claude/skills/en-engtech-journal-workflow/SKILL.md (or your agent's skills folder).- name
- en-engtech-journal-workflow
- description
- 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).
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
- 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?
- 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?
- Validation shape: mathematical proof, numerical simulation, controlled bench experiment, hardware prototype, pilot/field deployment, or standardized materials/mechanical testing?
- Audience breadth: the whole field (Proceedings of the IEEE, a Nature Portfolio engineering title), a sub-discipline community (an IEEE Transactions, Automatica, JFM, Acta Materialia), or a specialty niche?
Quick routing
| Manuscript signature | Prefer skill |
|---|---|
| Authoritative tutorial / scanning-the-field review (EE/CS) | proceedings-of-the-ieee |
| Control theory, stability, optimal/robust/adaptive control | ieee-transactions-on-automatic-control / automatica |
| Coding, capacity, information-theoretic bound | ieee-transactions-on-information-theory |
| Estimation, detection, sampling, array/statistical signal processing | ieee-transactions-on-signal-processing |
| Communication systems, protocols, networks | ieee-transactions-on-communications / ieee-transactions-on-wireless-communications / ieee-journal-on-selected-areas-in-communications |
| Power electronics / converters / drives | ieee-transactions-on-power-electronics / ieee-transactions-on-industrial-electronics |
| Power grid, electricity markets, system operation | ieee-transactions-on-power-systems |
| Antennas, propagation, electromagnetics | ieee-transactions-on-antennas-and-propagation |
| Robot design, planning, control, manipulation | ieee-transactions-on-robotics / the-international-journal-of-robotics-research |
| Medical imaging reconstruction / analysis | ieee-transactions-on-medical-imaging |
| Biomedical devices, signals, instrumentation | ieee-transactions-on-biomedical-engineering / nature-biomedical-engineering |
| Photonics device / optical method, broad + high impact | optica / light-science-and-applications |
| Authoritative photonics review | laser-and-photonics-reviews |
| New electronic device / circuit concept, broad significance | nature-electronics |
| Implantable / regenerative / drug-delivery materials | biomaterials |
| Structural alloys / processing–microstructure | acta-materialia |
| Solid mechanics, fracture, constitutive theory | journal-of-the-mechanics-and-physics-of-solids / international-journal-of-plasticity |
| Fundamental fluid mechanics | journal-of-fluid-mechanics |
| Machining, forming, precision manufacturing | international-journal-of-machine-tools-and-manufacture |
| Additive manufacturing process–structure–property | additive-manufacturing |
| Composite materials / structures | composites-part-b-engineering |
| Aerospace systems review | progress-in-aerospace-sciences |
| Chemical/process engineering fundamentals | aiche-journal / chemical-engineering-journal |
| Combustion / energy-conversion fundamentals review | progress-in-energy-and-combustion-science |
| Membranes / separations | journal-of-membrane-science |
| Systems-level energy analysis, integration, decarbonization | applied-energy |
| Batteries / fuel cells / electrochemical power | journal-of-power-sources / energy-storage-materials |
| Authoritative materials review | progress-in-materials-science |
| Transportation/network methodology, theory | transportation-research-part-b-methodological |
| Concrete / cementitious materials science | cement-and-concrete-research |
Show full SKILL.md (302 more words)Show less
Sibling-journal disambiguation
| Confusable targets | Decision rule |
|---|---|
ieee-transactions-on-automatic-control vs automatica | Both are top control venues; TAC leans toward rigorous theory and shorter technical notes, Automatica toward methodological breadth — route by the form of the main result and re-check current scopes. |
ieee-transactions-on-robotics vs the-international-journal-of-robotics-research | T-RO favors complete, validated robotics contributions; IJRR favors longer, conceptually framed archival work — route by contribution length and framing. |
optica vs light-science-and-applications | Both are high-impact photonics; decide whether the advance is best framed for the Optica/OSA optics community or the Nature Portfolio breadth audience. |
Nature-Portfolio engineering (nature-electronics/nature-biomedical-engineering) vs IEEE Transactions | Nature titles need field-changing significance and broad framing; a complete, rigorous specialty result routes to the matching IEEE Transactions. |
acta-materialia vs the materials/energy titles in the natural-science bundle (advanced-materials, nature-materials) | Route structural/processing metallurgy to Acta Materialia; conceptual functional-materials advances to the Nature/Advanced family. |
applied-energy vs journal-of-power-sources/energy-storage-materials | Systems-level energy integration → Applied Energy; device-level electrochemical power/storage → the power-source/storage titles. |
Decision rules
- Name the engineering contribution. "We built/measured X" is not a contribution unless it advances a method, a bound, a design principle, or a performance frontier with a reproducible margin over the right baseline.
- Baseline and benchmark discipline. Performance claims need comparison to the current state of the art under stated, reproducible conditions — not to a strawman.
- Theory vs. system. A theorem/bound, a method with guarantees, and a deployed system are different products; pick the reviewer community that evaluates the main claim.
- Survey/tutorial venues are mostly invited or scoped (Proceedings of the IEEE, Progress in Materials Science / Aerospace Sciences / Energy and Combustion Science) — do not route an unsolicited primary-data paper there without checking scope.
- Reproducibility/data/code expectations are now standard in engineering — a results paper without enough to reproduce the key claim is a common reject.
- Always enter the single-journal skill's official-submission checklist before submitting; never rely on a stale template.
Output format
[Top journal skill] <skill-name>
[Alt 1] <skill-name> (reason)
[Alt 2] <skill-name> (reason)
[Do not submit to] <journal> (one-line mismatch reason)
[Biggest current gap] contribution-clarity / baseline / validation / reproducibility / formatting / official requirements
[Next step] invoke <skill-name> for single-venue fit and re-framing© 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/en-engtech-journal-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
En Engtech Journal Workflow 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| En Engtech Journal Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~2k | Automated safety check: Pass | MIT | |
| Monitor CInrwl/nx | 29k | 6 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Terraform and OpenTofu Guideagentscope-ai/QwenPaw | 36k | 6 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
Docs Learn PR Preview
netdata/netdata
Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag 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…
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…
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…
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…
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…
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…
Related
Categories
Questions about En Engtech Journal Workflow
What does En Engtech Journal Workflow do?
A skill your agent uses when deciding which English engineering / technology journal skill to invoke next, comparing fit across the 40-journal engineering roadmap, or routing a manuscript before…. En Engtech Journal Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use En Engtech Journal Workflow?
En Engtech Journal Workflow fits situations like: deciding which English engineering / technology journal skill to invoke next; comparing fit across the 40-journal engineering roadmap; routing a manuscript before venue-specific re-framing.
How do I install En Engtech Journal Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-engtech-journal-workflow -a claude-code`. Or copy the skill folder (Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/en-engtech-journal-workflow in your project. Claude Code loads it when a task matches its description.
How do I install En Engtech Journal Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill en-engtech-journal-workflow -a codex`. Or copy the skill folder (Engineering-Technology-Journal-Skills/skills/en-engtech-journal-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/en-engtech-journal-workflow in your project. Codex loads it when a task matches its description.
Can I use En Engtech Journal Workflow 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 en-engtech-journal-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/en-engtech-journal-workflow, .gemini/skills/en-engtech-journal-workflow, .github/skills/en-engtech-journal-workflow and .opencode/skills/en-engtech-journal-workflow in your project.
What does En Engtech Journal Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: En Engtech Journal Workflow is instructions for the agent only.
Does En Engtech Journal Workflow 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 En Engtech Journal Workflow 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 En Engtech Journal Workflow use?
En Engtech Journal Workflow 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 En Engtech Journal Workflow use?
About 2k tokens (SKILL.md is roughly 7.9k 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 En Engtech Journal Workflow?
Skills that share tags, products or a category with En Engtech Journal Workflow: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains En Engtech Journal Workflow?
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.