Acm Sigmetrics
franklee16/academic-research-skills
A skill your agent uses when targeting ACM SIGMETRICS (SIGMETRICS) or deciding whether a computer-science manuscript fits this venue.
A skill your agent uses when planning an ACM SIGMETRICS project timeline across the three rolling deadlines (summer/fall/winter), from venue fit through abstract registration, submission…
MITAuto-check passed
Install Sigmetrics Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmetrics-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmetrics-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/SIGMETRICS-Skills/skills/sigmetrics-workflow .claude/skills/sigmetrics-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 "sigmetrics-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMETRICS-Skills/skills/sigmetrics-workflow into .claude/skills/sigmetrics-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmetrics-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/SIGMETRICS-Skills/skills/sigmetrics-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 sigmetrics-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmetrics-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/SIGMETRICS-Skills/skills/sigmetrics-workflow .agents/skills/sigmetrics-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 "sigmetrics-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMETRICS-Skills/skills/sigmetrics-workflow into .agents/skills/sigmetrics-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmetrics-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 sigmetrics-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmetrics-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/SIGMETRICS-Skills/skills/sigmetrics-workflow .cursor/skills/sigmetrics-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 "sigmetrics-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMETRICS-Skills/skills/sigmetrics-workflow into .cursor/skills/sigmetrics-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmetrics-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 SIGMETRICS-Skills/skills/sigmetrics-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 sigmetrics-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmetrics-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/SIGMETRICS-Skills/skills/sigmetrics-workflow .gemini/skills/sigmetrics-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 "sigmetrics-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMETRICS-Skills/skills/sigmetrics-workflow into .gemini/skills/sigmetrics-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmetrics-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 sigmetrics-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 sigmetrics-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/SIGMETRICS-Skills/skills/sigmetrics-workflow .github/skills/sigmetrics-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 "sigmetrics-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMETRICS-Skills/skills/sigmetrics-workflow into .github/skills/sigmetrics-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmetrics-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 sigmetrics-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 sigmetrics-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/SIGMETRICS-Skills/skills/sigmetrics-workflow .opencode/skills/sigmetrics-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 "sigmetrics-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMETRICS-Skills/skills/sigmetrics-workflow into .opencode/skills/sigmetrics-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmetrics-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
sigmetrics-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 657 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an ACM SIGMETRICS project timeline across the three rolling deadlines (summer/fall/winter), from venue fit through abstract registration, submission…
- Planning an ACM SIGMETRICS project timeline across the three rolling deadlines (summer/fall/winter)
- SKILL.md covers The rolling-deadline advantage, Milestones, Backward plan from a paper… and The 12-month bar and…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- From venue fit through abstract registration
What it does
Sigmetrics Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM SIGMETRICS project timeline across the three rolling deadlines (summer/fall/winter), from venue fit through abstract registration, submission, shepherding, the one-shot revision round, POMACS publication, and presentation, with backward-planning offsets for a performance-evaluation paper and honest handling of the rolling-deadline cadence and the 12-month resubmission bar.
Its SKILL.md is about 1.4k 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 an ACM SIGMETRICS project timeline across the three rolling deadlines (summer/fall/winter)
- From venue fit through abstract registration
- The one-shot revision round
- POMACS publication
Example prompts
- “/sigmetrics-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
Sigmetrics Workflow loads about 1.4k tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 657 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). 657 words, ~1,426 tokens.
Download SKILL.mdSave it as
.claude/skills/sigmetrics-workflow/SKILL.md (or your agent's skills folder).- name
- sigmetrics-workflow
- description
- Use when planning an ACM SIGMETRICS project timeline across the three rolling deadlines (summer/fall/winter), from venue fit through abstract registration, submission, shepherding, the one-shot revision round, POMACS publication, and presentation, with backward-planning offsets for a performance-evaluation paper and honest handling of the rolling-deadline cadence and the 12-month resubmission bar.
SIGMETRICS Workflow
Use this as the project-management skill for a SIGMETRICS submission. SIGMETRICS runs three rolling deadlines a year (summer / fall / winter) into the POMACS journal, so the calendar is a choice among deadlines, not a single annual scramble. Replace every date with the current official timetable and work backwards from the abstract-registration cutoff, which precedes each paper deadline by about a week.
SIGMETRICS has rotating per-edition General and Program Chairs (appointed by the SIGMETRICS executive committee) rather than a standing conference editor-in-chief; POMACS is open access with no APC, and at least one author presents each accepted paper. Re-check the current organizing-committee page rather than carrying a name forward.
The rolling-deadline advantage
Unlike a once-a-year venue, SIGMETRICS lets you aim at the next deadline that fits your evidence. Two consequences:
- Missing a deadline costs ~4 months, not a year — the next rolling deadline is a quarter away. Do not rush a proof or a measurement campaign to hit summer if fall gives you a clean result.
- Publication timing matters: summer/fall acceptances appear in POMACS before the conference; a winter acceptance publishes in the following issue. Choose the deadline whose POMACS timing and presentation slot fit your goals.
Milestones
- Venue fit: confirm SIGMETRICS over IMC/SIGCOMM/NSDI/a theory venue, and the correct track
(
sigmetrics-topic-selection). - Evidence lock: freeze the model and assumptions, complete the proofs, and finish the simulation/measurement that validates them.
- Abstract registration: submit real title, abstract, authors, conflicts, and track by the earlier registration deadline.
- Submission: upload the anonymized acmsmall PDF and the artifact reference by the paper deadline (23:59 AoE).
- Reviews: triage each comment by criterion (rigor, proof correctness, assumption validity, evidence, novelty, reproducibility).
- One-Shot Revision (if issued): close the entire required-changes list and resubmit to one of the two subsequent deadlines — a single shot, re-read by the original reviewers.
- Accept + shepherding: incorporate the shepherd's required changes into the final POMACS version.
- Publication + presentation: POMACS camera-ready, artifact/badges if the cycle offers them, register, and present.
Backward plan from a paper deadline
| Weeks out (heuristic) | Performance-evaluation milestone |
|---|---|
| 10+ | Model and assumptions fixed; main theorems stated; measurement/trace secured |
| 8 | Proofs complete and internally checked; simulator built with logged seeds |
| 6 | Analysis-vs-simulation agreement established; baselines chosen and tuned |
| 4 | Full draft in acmsmall; artifact (model, simulator, trace scripts) assembled and anonymized |
| 3 | Internal mock review by a performance-evaluation reader (check a proof case and an assumption) |
| 2 | Assumption-validity section hardened; related-work delta sharpened; 20-page budget met |
| 1 | Anonymity sweep on PDF and artifact; abstract registered |
| 0 | Paper + artifact reference on the correct per-deadline HotCRP site |
These offsets are planning heuristics only — anchor every one to the current call and the
per-deadline HotCRP deadlines page, never to a previous cycle.
Show full SKILL.md (211 more words)Show less
The 12-month bar and cycle-hopping
- A reject cannot be resubmitted to any SIGMETRICS deadline for 12 months from the initial submission — a structural reject costs a full year at SIGMETRICS, so route a fundamentally reframed paper elsewhere meanwhile rather than idling.
- A One-Shot Revision is not a reject: it resubmits to a subsequent deadline within the rolling process. Budget the revision window to close the whole list in one shot.
Failure modes by stage
- A proof still has an open case at week 4 forces a rushed appendix nobody has checked — the classic rigor reject in the making.
- An unvalidated assumption (claiming M/G/1 without fitting the workload) invites the "does the model match reality?" objection that a One-Shot Revision then has to repair.
- Leaving the simulator/trace scripts to the final week is how a cluster path or a provenance string leaks identity under double-anonymity.
- Rushing a One-Shot Revision into the nearer deadline and leaving a listed item half-done turns a winnable single-shot into a reject.
Coordination notes
- Assign one owner for the proofs/appendix and another for the simulator/measurement and the anonymity sweep; shared ownership is how both slip.
- Archive the exact submitted PDF, artifact, and (later) the required-changes list and response — the single-shot revision must close that list precisely.
Output format
[Current stage] idea / model+proof / evidence / registration / submitted / one-shot revision / accepted
[Chosen deadline] summer / fall / winter <cycle>, and its abstract + paper dates (source)
[Critical path] <three tasks that determine readiness>
[Risk register] <proof completeness / assumption validity / anonymity / reproducibility / page budget>
[Owner map] <task -> person or role>© 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 SIGMETRICS-Skills/skills/sigmetrics-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sigmetrics 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 |
|---|---|---|---|---|---|---|
| Sigmetrics Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Acm Sigmetricsfranklee16/academic-research-skills | 223 | 1 repos | ~1.9k | Automated safety check: Pass | None | |
| Project Timeline Reportthedotmack/claude-mem | 99k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GSAP Timelinegreensock/gsap-skills | 16k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Building Incident Timeline With Timesketchmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.4k | Automated safety check: Notes | Apache-2.0 | |
| Generating Forensic Timelines With Hayabusamukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
GSAP Timeline
greensock/gsap-skills
Teaches the GSAP timeline API for sequencing animations: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control.
Building Incident Timeline With Timesketch
mukul975/Anthropic-Cybersecurity-Skills
Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation…
Generating Forensic Timelines With Hayabusa
mukul975/Anthropic-Cybersecurity-Skills
Run Hayabusa against collected Windows EVTX files to apply Sigma detection rules and produce a prioritized, chronological CSV/JSON timeline with severity levels, MITRE ATT&CK mappings, and…
Performing Timeline Reconstruction With Plaso
mukul975/Anthropic-Cybersecurity-Skills
Builds comprehensive forensic super-timelines using Plaso (log2timeline and psort) to correlate events across file system metadata, event logs, browser history, and registry artifacts into a unified…
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 Sigmetrics Workflow
What does Sigmetrics Workflow do?
A skill your agent uses when planning an ACM SIGMETRICS project timeline across the three rolling deadlines (summer/fall/winter), from venue fit through abstract registration, submission…. Sigmetrics Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM SIGMETRICS project timeline across the three rolling deadlines (summer/fall/winter), from venue fit through abstract registration, submission, shepherding, the one-shot revision round, POMACS publication, and presentation, with backward-planning offsets for a performance-evaluation paper and honest handling of the rolling-deadline cadence and the 12-month resubmission bar.
When should I use Sigmetrics Workflow?
Sigmetrics Workflow fits situations like: planning an ACM SIGMETRICS project timeline across the three rolling deadlines (summer/fall/winter); from venue fit through abstract registration; the one-shot revision round; POMACS publication.
How do I install Sigmetrics Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmetrics-workflow -a claude-code`. Or copy the skill folder (SIGMETRICS-Skills/skills/sigmetrics-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigmetrics-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Sigmetrics Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmetrics-workflow -a codex`. Or copy the skill folder (SIGMETRICS-Skills/skills/sigmetrics-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigmetrics-workflow in your project. Codex loads it when a task matches its description.
Can I use Sigmetrics 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 sigmetrics-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/sigmetrics-workflow, .gemini/skills/sigmetrics-workflow, .github/skills/sigmetrics-workflow and .opencode/skills/sigmetrics-workflow in your project.
What does Sigmetrics Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Sigmetrics Workflow is instructions for the agent only.
Does Sigmetrics 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 Sigmetrics 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 Sigmetrics Workflow use?
Sigmetrics 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 Sigmetrics Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.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 Sigmetrics Workflow?
Skills that share tags, products or a category with Sigmetrics Workflow: Acm Sigmetrics (franklee16/academic-research-skills, 223 stars), Project Timeline Report (thedotmack/claude-mem, 99k stars), GSAP Timeline (greensock/gsap-skills, 16k stars) and Building Incident Timeline With Timesketch (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sigmetrics 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.