Sub Skill
MoonshotAI/kimi-code
Discover and reorganize the skill inventory into hierarchical sub-skill bundles.
A skill your agent uses when deciding which ecopol- sub-skill to invoke next, or when sequencing manuscript work from topic pitch through post-panel revision for an Economic Policy (EP) manuscript.
MITAuto-check passed
Install Ecopol Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecopol-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecopol-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/Economic-Policy-Skills/skills/ecopol-workflow .claude/skills/ecopol-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 "ecopol-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Economic-Policy-Skills/skills/ecopol-workflow into .claude/skills/ecopol-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecopol-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/Economic-Policy-Skills/skills/ecopol-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 ecopol-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecopol-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/Economic-Policy-Skills/skills/ecopol-workflow .agents/skills/ecopol-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 "ecopol-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Economic-Policy-Skills/skills/ecopol-workflow into .agents/skills/ecopol-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecopol-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 ecopol-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecopol-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/Economic-Policy-Skills/skills/ecopol-workflow .cursor/skills/ecopol-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 "ecopol-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Economic-Policy-Skills/skills/ecopol-workflow into .cursor/skills/ecopol-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecopol-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 Economic-Policy-Skills/skills/ecopol-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 ecopol-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecopol-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/Economic-Policy-Skills/skills/ecopol-workflow .gemini/skills/ecopol-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 "ecopol-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Economic-Policy-Skills/skills/ecopol-workflow into .gemini/skills/ecopol-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecopol-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 ecopol-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 ecopol-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/Economic-Policy-Skills/skills/ecopol-workflow .github/skills/ecopol-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 "ecopol-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Economic-Policy-Skills/skills/ecopol-workflow into .github/skills/ecopol-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecopol-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 ecopol-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 ecopol-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/Economic-Policy-Skills/skills/ecopol-workflow .opencode/skills/ecopol-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 "ecopol-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Economic-Policy-Skills/skills/ecopol-workflow into .opencode/skills/ecopol-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecopol-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
ecopol-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 765 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 ecopol- sub-skill to invoke next, or when sequencing manuscript work from topic pitch through post-panel revision for an Economic Policy (EP) manuscript.
- Works in 11 steps: ecopol-topic-selection — lock a timely,… → ecopol-literature-positioning — stake… → ecopol-identification — make the… → …
- Deciding which ecopol- sub-skill to invoke next
- SKILL.md covers Overview, When to trigger, Routing table and Default order, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ecopol Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding which ecopol- sub-skill to invoke next, or when sequencing manuscript work from topic pitch through post-panel revision for an Economic Policy (EP) manuscript. Routes — it does not replace — the specialized skills.
Its SKILL.md is about 1.8k 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
- Deciding which ecopol- sub-skill to invoke next
- Sequencing manuscript work from topic pitch through post-panel revision for an Economic Policy (EP) manuscript
Example prompts
- “/ecopol-workflow”
Workflow steps
11 steps, taken from the first numbered list in SKILL.md.
- ecopol-topic-selection — lock a timely, Panel-worthy policy question
- ecopol-literature-positioning — stake the contribution to the live policy debate
- ecopol-identification — make the data-to-policy-claim mapping credible
- ecopol-theory-model — the minimal model that disciplines the policy logic
- ecopol-robustness — pre-empt the discussants' fragility tests
- ecopol-tables-figures — exhibits a minister could read
- ecopol-writing-style — accessible main text, technical appendix (do this late)
- ecopol-replication-package — verification-ready data + code
- ecopol-referee-strategy — war-game the two discussants + panel
- ecopol-submission — commissioning / camera-ready preflight
- ecopol-rebuttal — revise after the panel and discussant comments
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
Ecopol Workflow loads about 1.8k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 765 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). 765 words, ~1,750 tokens.
Download SKILL.mdSave it as
.claude/skills/ecopol-workflow/SKILL.md (or your agent's skills folder).- name
- ecopol-workflow
- description
- Use when deciding which ecopol-* sub-skill to invoke next, or when sequencing manuscript work from topic pitch through post-panel revision for an Economic Policy (EP) manuscript. Routes — it does not replace — the specialized skills.
Economic Policy Workflow Router (ecopol-workflow)
Overview
This is the router. It tells you which ecopol- skill to use at the current stage* of a paper aimed at Economic Policy — the CEPR / CESifo / Sciences Po (Fondation Nationale des Sciences Politiques) policy-economics journal published by Oxford University Press. EP's identity is European, policy-first, and accessible: rigorous analysis of a current policy question written so that economists and policymakers can read it, with the heavy machinery pushed to an appendix.
What makes EP unlike any sibling is its lifecycle. EP does not run standard anonymous refereeing. Papers are selected by the Managing Editor / Panel, presented at the journal's biannual conference (summer and winter), where two invited discussants debate each paper from an academic and a policy angle and act as the referees. The final paper is published together with the discussants' comments and a summary of the panel discussion, within ~6 months of presentation (检索于 2026-06；以官网为准). Since the 2025 relaunch as Economic Policy: Papers on European and Global Issues, the journal is online-only and commissioned — "all articles are invited by the Managing Editor"; unsolicited submissions are not accepted (检索于 2026-06；以官网为准). Treat ecopol-submission as the pitch / commissioning + camera-ready route, not an open portal.
Default assumption: unless the user says otherwise, the target is EP and the bottleneck is "will the Panel want this, and will it survive two discussants in front of a policy audience?"
When to trigger
- The user asks "what should I do next?" on an EP-bound paper
- A draft's current bottleneck (fit, framing, evidence, exhibits, prose) needs diagnosing
- Work is ping-ponging between the policy question, the identification, the writing, and the discussant-proofing
- A commissioning invitation or a post-panel revision request arrived and the user must switch modes
Routing table
| Current symptom | Next skill |
|---|---|
| Not clearly a timely, important policy question the Panel would commission | ecopol-topic-selection |
| Contribution vs. the policy debate / adjacent journals is fuzzy | ecopol-literature-positioning |
| Causal or structural credibility is the binding constraint | ecopol-identification |
| The mechanism / model that organizes the policy logic is loose | ecopol-theory-model |
| Results may be specification-, sample-, or inference-fragile | ecopol-robustness |
| Exhibits are too technical for a policy reader or don't carry the message | ecopol-tables-figures |
| Main text reads like a tech report, not accessible policy prose | ecopol-writing-style |
| Data / code package and verification material need assembling | ecopol-replication-package |
| Need to anticipate the two discussants and the panel debate | ecopol-referee-strategy |
| Camera-ready / commissioning logistics need a final check | ecopol-submission |
| A post-panel / discussant revision request needs a response plan | ecopol-rebuttal |
Default order
ecopol-topic-selection— lock a timely, Panel-worthy policy questionecopol-literature-positioning— stake the contribution to the live policy debateecopol-identification— make the data-to-policy-claim mapping credibleecopol-theory-model— the minimal model that disciplines the policy logicecopol-robustness— pre-empt the discussants' fragility testsecopol-tables-figures— exhibits a minister could readecopol-writing-style— accessible main text, technical appendix (do this late)ecopol-replication-package— verification-ready data + codeecopol-referee-strategy— war-game the two discussants + panelecopol-submission— commissioning / camera-ready preflightecopol-rebuttal— revise after the panel and discussant comments
ecopol-writing-styleis late polish; do not rewrite the intro before the identification and the headline policy number settle.
Show full SKILL.md (254 more words)Show less
Routing by paper archetype
The discussant duo and panel debate hit different papers at different seams. Read the archetype, enter the chain at the right link.
| Archetype | Likely first bottleneck | Enter at |
|---|---|---|
| empirical causal evaluation of a policy | staggered-DID / weak-IV credibility under a hostile discussant | ecopol-identification |
| structural / quantitative policy model | what identifies parameters + counterfactual policy-invariance | ecopol-theory-model → ecopol-identification |
| macro / fiscal / monetary policy analysis | timeliness + the central policy number's robustness | ecopol-topic-selection → ecopol-robustness |
| cross-country / EU-institutional study | comparability of data + the "so what for European policy" | ecopol-literature-positioning |
Worked routing example (illustrative)
A user says: "We were invited to present a paper on an EU minimum-wage directive at the winter conference; one likely discussant is a labor economist, the other sits in a finance ministry." That is the EP-specific bottleneck — survive two discussants from two worlds. The labor discussant will press identification (ecopol-identification) and robustness (ecopol-robustness); the ministry discussant will press the headline magnitude, the welfare/cost framing, and whether a non-economist can read it (ecopol-tables-figures, ecopol-writing-style). Route to ecopol-referee-strategy to map both personas, then to the two technical skills they will probe.
Anti-patterns
- Treating EP like a journal with an open submission portal and anonymous referees — it is commissioned, panel-reviewed, with named discussants
- Polishing prose before identification and the central policy number are stable
- Confusing EP with AEJ: Economic Policy (AEA, anonymous refereeing, more technical), Brookings Papers (the US panel analogue), or Journal of Public Economics (field journal, no panel)
- Letting the technical appendix carry a claim the accessible main text must make to a policymaker
Minimal decision snippet
if post_panel_revision: -> ecopol-rebuttal
elif commissioned_camera_ready: -> ecopol-submission
elif facing_the_two_discussants: -> ecopol-referee-strategy
elif exhibits_too_technical: -> ecopol-tables-figures
elif results_fragile: -> ecopol-robustness
elif identification_shaky: -> ecopol-identification
elif model_loose: -> ecopol-theory-model
elif contribution_fuzzy: -> ecopol-literature-positioning
else: -> ecopol-topic-selection© 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 Economic-Policy-Skills/skills/ecopol-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ecopol 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 |
|---|---|---|---|---|---|---|
| Ecopol Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Sub SkillMoonshotAI/kimi-code | 7.8k | — | ~281 | Automated safety check: Pass | MIT | |
| Sub Agentsparcadei/Continuous-Claude-v3 | 3.9k | 2 repos | ~929 | Automated safety check: Notes | MIT | |
| Offensive Lorawan Sub GhzSnailSploit/Claude-Red | 7.3k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Create Invoke TaskDataDog/datadog-agent | 3.8k | — | ~606 | Automated safety check: Notes | Apache-2.0 | |
| Sub-Agent DelegationTokenRhythm/opensquilla | 7.1k | — | ~3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Sub Agents
parcadei/Continuous-Claude-v3
Create and configure Claude Code sub-agents with custom prompts, tools, and models
Offensive Lorawan Sub Ghz
SnailSploit/Claude-Red
LoRaWAN and sub-GHz (433 / 868 / 915 MHz) attack methodology — LoRaWAN ABP/OTAA join attack, network/session key reuse, frame counter replay, downlink injection on TTN/Helium-style networks, sub-GHz…
- Official
Create Invoke Task
DataDog/datadog-agent
Create a new Python invoke task for the dda CLI. An agent skill from DataDog/datadog-agent.
Sub-Agent Delegation
TokenRhythm/opensquilla
Hands a self-contained coding task to Codex, Claude Code, OpenCode or Pi as a non-interactive background process, using OpenSquilla's exec_command and process tools.
Launch Sub Agent
NeoLabHQ/context-engineering-kit
Launch an intelligent sub-agent with automatic model selection based on task complexity, specialized agent matching, Zero-shot CoT reasoning, and mandatory self-critique verification
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…
Questions about Ecopol Workflow
What does Ecopol Workflow do?
A skill your agent uses when deciding which ecopol- sub-skill to invoke next, or when sequencing manuscript work from topic pitch through post-panel revision for an Economic Policy (EP) manuscript. Ecopol Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding which ecopol- sub-skill to invoke next, or when sequencing manuscript work from topic pitch through post-panel revision for an Economic Policy (EP) manuscript.
When should I use Ecopol Workflow?
Ecopol Workflow fits situations like: deciding which ecopol- sub-skill to invoke next; sequencing manuscript work from topic pitch through post-panel revision for an Economic Policy (EP) manuscript.
How do I install Ecopol Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecopol-workflow -a claude-code`. Or copy the skill folder (Economic-Policy-Skills/skills/ecopol-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ecopol-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Ecopol Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecopol-workflow -a codex`. Or copy the skill folder (Economic-Policy-Skills/skills/ecopol-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ecopol-workflow in your project. Codex loads it when a task matches its description.
Can I use Ecopol 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 ecopol-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/ecopol-workflow, .gemini/skills/ecopol-workflow, .github/skills/ecopol-workflow and .opencode/skills/ecopol-workflow in your project.
What does Ecopol Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Ecopol Workflow is instructions for the agent only.
Does Ecopol 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 Ecopol 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 Ecopol Workflow use?
Ecopol 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 Ecopol Workflow use?
About 1.8k tokens (SKILL.md is roughly 7k 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 Ecopol Workflow?
Skills that share tags, products or a category with Ecopol Workflow: Sub Skill (MoonshotAI/kimi-code, 7.8k stars), Sub Agents (parcadei/Continuous-Claude-v3, 3.9k stars), Offensive Lorawan Sub Ghz (SnailSploit/Claude-Red, 7.3k stars) and Create Invoke Task (DataDog/datadog-agent, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ecopol Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.