Marketing Campaign
affaan-m/ECC
End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.
A skill your agent uses when planning a MICRO campaign end to end — the April-to-Athens 2026 cycle clock, the four-venue architecture calendar (MICRO/ISCA/HPCA/ASPLOS) seen from MICRO's October…
MITAuto-check passed
Install Micro Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-workflow .claude/skills/micro-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 "micro-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-workflow into .claude/skills/micro-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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/MICRO-Skills/skills/micro-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 micro-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-workflow .agents/skills/micro-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 "micro-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-workflow into .agents/skills/micro-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 micro-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-workflow .cursor/skills/micro-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 "micro-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-workflow into .cursor/skills/micro-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 MICRO-Skills/skills/micro-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 micro-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-workflow .gemini/skills/micro-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 "micro-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-workflow into .gemini/skills/micro-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 micro-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 micro-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/MICRO-Skills/skills/micro-workflow .github/skills/micro-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 "micro-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-workflow into .github/skills/micro-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 micro-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 micro-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/MICRO-Skills/skills/micro-workflow .opencode/skills/micro-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 "micro-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-workflow into .opencode/skills/micro-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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
micro-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 737 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a MICRO campaign end to end — the April-to-Athens 2026 cycle clock, the four-venue architecture calendar (MICRO/ISCA/HPCA/ASPLOS) seen from MICRO's October…
- Planning a MICRO campaign end to end — the April-to-Athens 2026 cycle clock
- SKILL.md covers The 2026 cycle clock (59th…, The four-venue calendar from…, Backward plan for a MICRO 2027… and Risk register for the…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The four-venue architecture calendar (MICRO/ISCA/HPCA/ASPLOS) seen from MICROs October seat
What it does
Micro Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a MICRO campaign end to end — the April-to-Athens 2026 cycle clock, the four-venue architecture calendar (MICRO/ISCA/HPCA/ASPLOS) seen from MICRO's October seat, resubmission lattices after each outcome, and starting the MICRO 2027 evaluation stack early enough to matter.
Its SKILL.md is about 1.7k 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
- Planning a MICRO campaign end to end — the April-to-Athens 2026 cycle clock
- The four-venue architecture calendar (MICRO/ISCA/HPCA/ASPLOS) seen from MICROs October seat
- Resubmission lattices after each outcome
- Starting the MICRO 2027 evaluation stack early enough to matter
Example prompts
- “/micro-workflow”
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
Micro Workflow loads about 1.7k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 737 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). 737 words, ~1,728 tokens.
Download SKILL.mdSave it as
.claude/skills/micro-workflow/SKILL.md (or your agent's skills folder).- name
- micro-workflow
- description
- Use when planning a MICRO campaign end to end — the April-to-Athens 2026 cycle clock, the four-venue architecture calendar (MICRO/ISCA/HPCA/ASPLOS) seen from MICRO's October seat, resubmission lattices after each outcome, and starting the MICRO 2027 evaluation stack early enough to matter.
MICRO Workflow
MICRO owns the autumn slot of computer architecture's four-venue year: an early April deadline feeding an end-of-October symposium. Because the four sibling venues interleave, a MICRO plan is really a lattice plan — every outcome has a next move within roughly four months. Dates below verified 2026-07-08; every one is a single-cycle snapshot.
The 2026 cycle clock (59th edition, Athens)
2026-03-31 abstract registration 11:59 PM EDT hard gate
2026-04-07 full paper 11:59 PM EDT micro2026.hotcrp.com
2026-06-03 → 06-17 rebuttal/revision two-week window (micro-author-response)
2026-07-07 notification
2026-09-11 camera-ready (AE runs in parallel; micro-camera-ready)
2026-10-31 → 11-04 symposium, Athens, GreeceAs of this pack's check date (2026-07-08), the 2026 cycle had just issued
decisions — the live work is camera-ready + AE for accepts, and lattice routing
for rejects. The next MICRO submission opportunity is the 2027 cycle, expected in
the same early-April position (待核实 when microarch.org posts it).
The four-venue calendar from MICRO's seat
| Venue | Deadline (verified for cycle shown) | Conference | Use it when |
|---|---|---|---|
| MICRO 2026 | Apr 7, 2026 (closed) | Oct 31–Nov 4, 2026, Athens | Mechanism-centric core work |
| HPCA 2027 | July 24, 2026 | March 2027, Salt Lake City | Fastest next slot after a MICRO reject — 17 days after notification |
| ASPLOS 2027 | Sept 9, 2026 (2nd of two; Apr 15 passed) | April 2027, Crete | Reviews said "the interesting part is the software interaction" |
| ISCA 2027 | abstracts Nov 10 / papers Nov 17, 2026 | June 2027, Atlanta | Four months of repair headroom; broadest architecture audience |
| MICRO 2027 | ~April 2027, 待核实 | autumn 2027 | Full-year rework or a new project |
The rhythm to internalize: architecture deadlines cluster in April (MICRO, ASPLOS-1st), July (HPCA), September (ASPLOS-2nd), and November (ISCA) — one submission window roughly every quarter. A healthy lab pipeline drafts against the next two windows simultaneously.
Backward plan for a MICRO 2027 submission
Working back from an assumed early-April 2027 deadline (verify the real date):
| When | Milestone | Owner risk |
|---|---|---|
| Aug–Sep 2026 | Mechanism sketch + micro-topic-selection gate; infrastructure choice (simulator, workloads) | Wrong venue discovered late |
| Oct–Nov 2026 | Baseline validated against published configs; characterization study done | Untuned baseline poisons all later data |
| Dec 2026 | Mechanism implemented in simulator; first end-to-end numbers | "It simulates" ≠ "it is modeled correctly" |
| Jan 2027 | Ablations + sensitivity sweeps; power/area modeling attached | Sweeps are compute-bound — queue early |
| Feb 2027 | Full draft; internal red-team review against micro-writing-style | Cost accounting missing |
| Mar 2027 | Freeze evaluation; micro-reproducibility manifests complete; format pass | Late "one more feature" restarts sweeps |
| T-7 days | Abstract registered in HotCRP | Missing the registration gate ends everything |
| T-0 | Upload (EDT arithmetic!) | See micro-submission |
The structural insight: in microarchitecture the evaluation stack is the schedule. Simulator bring-up, trace generation, and multi-week sweep queues dominate; prose is the cheap part. Any plan that allocates most of its calendar to writing is mis-costed.
Show full SKILL.md (324 more words)Show less
Risk register for the compute-bound schedule
| Risk | Early symptom | Mitigation |
|---|---|---|
| Sweep queue starvation | Cluster contention in Feb–Mar (everyone's MICRO crunch) | Reserve allocation in January; keep key-tier configs that finish overnight |
| Baseline invalidated late | A simulator bugfix changes baseline IPC | Freeze simulator commit by January; batch fixes into one revalidation |
| Trace regeneration cascade | New compiler/flags after traces cut | Version traces; treat regeneration as a one-week line item, not a checkbox |
| Writing squeezed to two weeks | "Evaluation almost done" through February | Draft intro + mechanism sections in parallel with sweeps — they do not depend on final numbers |
| Deadline-week format panic | First full format pass happens at T-2 | Run the micro-submission gate table at T-14 and T-1 |
Standing weekly cadence during a campaign
Mon queue review: sweeps finished / stalled / mis-configured; ledger updated
Wed claims meeting: does yesterday's data still support the paper's sentences?
Fri risk register walk (table above) + one live-page re-verification
(deadline, CFP, HotCRP) logged with date — rules change between visitsOutcome branches (July 7 has happened)
- Accepted: run
micro-camera-readyandmicro-artifact-evaluationas parallel tracks converging on September 11; book Athens logistics once attendance rules are confirmed (待核实 onmicro59/attend/). - Rejected, methodology wounds: the HPCA July 24 window is realistically only for papers whose fixes are textual; simulation repairs point at ISCA Nov 17.
- Rejected, "not microarchitectural enough": ASPLOS Sept 9 with a cross-layer
reframe — see
micro-topic-selectionrouting table. - Any branch: archive reviews, update the results ledger, and file rebuttal promises as the next version's spec.
Multi-paper pipelines and self-competition
Labs running more than one submission per cycle share one sweep queue and one set of senior readers — schedule both explicitly:
- Stagger internal red-team reviews (
micro-writing-stylechecklist) so the same professor is not reading two full drafts in deadline week. - Deconflict topics in HotCRP if two submissions are adjacent; two papers from one lab splitting the same reviewer pool can drag each other down in double-blind bidding without anyone noticing until the reviews land.
- After notification, the lattice branches diverge per paper — keep one shared calendar of the four venues' gates (table above) so a July HPCA sprint for paper A does not silently consume the cluster paper B needs for its ISCA repairs.
Output format
[Today] <date> → position in cycle: <phase>
[Active gate] <next deadline, venue, days remaining, timezone stated>
[Lattice] plan A <venue+date> · plan B <venue+date> · trigger condition between them
[Evaluation-stack status] simulator / baseline / traces / sweeps: ready-blocked each
[Backward plan] next 3 milestones with dates and owners
[待核实] <dates assumed but not yet posted on live pages>© 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 MICRO-Skills/skills/micro-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Micro 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 |
|---|---|---|---|---|---|---|
| Micro Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Marketing Campaignaffaan-m/ECC | 275k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Campaign Analyticsalirezarezvani/claude-skills | 28k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Campaign Cleaner AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~764 | Automated safety check: Pass | None | |
| LobeHub Micro App Splitting Guidelobehub/lobehub | 83k | — | ~9.3k | Automated safety check: Pass | Custom licence | |
| Ad Campaign Analyzersickn33/agentic-awesome-skills | 47k | 1 repos | ~4.3k | Automated safety check: Pass | MIT |
Similar skills
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Campaign Cleaner Automation
ComposioHQ/awesome-claude-skills
Automate Campaign Cleaner tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
LobeHub Micro App Splitting Guide
lobehub/lobehub
Documents how LobeHub's standalone micro apps are hosted, built and routed differently on Cloud versus self-hosted Docker, so a change does not break one path while fixing the other.
Ad Campaign Analyzer
sickn33/agentic-awesome-skills
Analyze cross-channel campaign data, quantify uncertainty, and propose evidence-labeled budget tests without overstating causality.
- Official
Ad Campaign Analyzer
github/awesome-copilot
A skill your agent uses when the user shares ad campaign performance data and asks what to cut, scale, or test.
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 Micro Workflow
What does Micro Workflow do?
A skill your agent uses when planning a MICRO campaign end to end — the April-to-Athens 2026 cycle clock, the four-venue architecture calendar (MICRO/ISCA/HPCA/ASPLOS) seen from MICRO's October…. Micro Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a MICRO campaign end to end — the April-to-Athens 2026 cycle clock, the four-venue architecture calendar (MICRO/ISCA/HPCA/ASPLOS) seen from MICRO's October seat, resubmission lattices after each outcome, and starting the MICRO 2027 evaluation stack early enough to matter.
When should I use Micro Workflow?
Micro Workflow fits situations like: planning a MICRO campaign end to end — the April-to-Athens 2026 cycle clock; the four-venue architecture calendar (MICRO/ISCA/HPCA/ASPLOS) seen from MICROs October seat; resubmission lattices after each outcome; starting the MICRO 2027 evaluation stack early enough to matter.
How do I install Micro Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-workflow -a claude-code`. Or copy the skill folder (MICRO-Skills/skills/micro-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/micro-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Micro Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-workflow -a codex`. Or copy the skill folder (MICRO-Skills/skills/micro-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/micro-workflow in your project. Codex loads it when a task matches its description.
Can I use Micro 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 micro-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/micro-workflow, .gemini/skills/micro-workflow, .github/skills/micro-workflow and .opencode/skills/micro-workflow in your project.
What does Micro Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Micro Workflow is instructions for the agent only.
Does Micro 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 Micro 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 Micro Workflow use?
Micro 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 Micro Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.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 Micro Workflow?
Skills that share tags, products or a category with Micro Workflow: Marketing Campaign (affaan-m/ECC, 275k stars), Campaign Analytics (alirezarezvani/claude-skills, 28k stars), Campaign Cleaner Automation (ComposioHQ/awesome-claude-skills, 77k stars) and LobeHub Micro App Splitting Guide (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Micro 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.