Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when deciding which humrel- sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Human Relations (HR) submission.
Install Humrel Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill humrel-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills humrel-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/Human-Relations-Skills/skills/humrel-workflow .claude/skills/humrel-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 "humrel-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-workflow into .claude/skills/humrel-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-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/Human-Relations-Skills/skills/humrel-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 humrel-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills humrel-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/Human-Relations-Skills/skills/humrel-workflow .agents/skills/humrel-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 "humrel-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-workflow into .agents/skills/humrel-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-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 humrel-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills humrel-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/Human-Relations-Skills/skills/humrel-workflow .cursor/skills/humrel-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 "humrel-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-workflow into .cursor/skills/humrel-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-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 Human-Relations-Skills/skills/humrel-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 humrel-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills humrel-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/Human-Relations-Skills/skills/humrel-workflow .gemini/skills/humrel-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 "humrel-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-workflow into .gemini/skills/humrel-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-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 humrel-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 humrel-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/Human-Relations-Skills/skills/humrel-workflow .github/skills/humrel-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 "humrel-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-workflow into .github/skills/humrel-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-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 humrel-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 humrel-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/Human-Relations-Skills/skills/humrel-workflow .opencode/skills/humrel-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 "humrel-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Human-Relations-Skills/skills/humrel-workflow into .opencode/skills/humrel-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "humrel-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
humrel-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 728 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 humrel- sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Human Relations (HR) submission.
- Works in 11 steps: humrel-topic-selection — lock the… → humrel-theory-development — build the… → humrel-literature-positioning — stake… → …
- Deciding which humrel- 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
Humrel Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding which humrel- sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Human Relations (HR) submission. Routes — it does not replace — the specialized skills.
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.
It sits in Research & Science. 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 humrel- sub-skill to invoke next
- Sequencing manuscript work from topic through rebuttal for a Human Relations (HR) submission
Example prompts
- “/humrel-workflow”
Workflow steps
11 steps, taken from the first numbered list in SKILL.md.
- humrel-topic-selection — lock the work-and-society question and HR fit
- humrel-theory-development — build the social-theoretical engine
- humrel-literature-positioning — stake the contribution vs. the conversation
- humrel-methods — design (qual / critical / quant / mixed) with rigor
- humrel-data-analysis — make the evidence-to-theory link transparent
- humrel-contribution-framing — sharpen the one-sentence theoretical claim
- humrel-tables-figures — exhibits that carry, not decorate
- humrel-writing-style — the reflexive HR voice (intro + abstract last)
- humrel-submission — anonymized ScholarOne preflight
- humrel-review-process — calibrate the scoping screen and developmental review
- humrel-rebuttal — after the R&R
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
Humrel Workflow loads about 1.7k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 728 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). 728 words, ~1,732 tokens.
Download SKILL.mdSave it as
.claude/skills/humrel-workflow/SKILL.md (or your agent's skills folder).- name
- humrel-workflow
- description
- Use when deciding which humrel-* sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Human Relations (HR) submission. Routes — it does not replace — the specialized skills.
Human Relations Workflow Router (humrel-workflow)
Overview
This is the router. It tells you which humrel- skill to use at the current stage* of a manuscript aimed at Human Relations (HR) — the long-established interdisciplinary social-science journal of work, organization, and management, published by SAGE for the Tavistock Institute of Human Relations (founded 1947, monthly). HR draws on organization studies, sociology, psychology, and critical perspectives, and its stated aim is "to advance our understanding of social relationships at and around work through theoretical development and empirical investigation." It treats qualitative, critical, quantitative, and mixed-methods work as equally first-class — what is non-negotiable is a unique and substantive theoretical contribution anchored in the relational, social nature of work.
Operational tells that you are at HR and not a sibling: review is double-anonymous, so the manuscript must be fully anonymized (no author names, no links to external sites); the total length cap is 13,000 words including everything (检索于 2026-06；以官网为准); referencing is SAGE Harvard (author-date); submission is through ScholarOne / ManuscriptCentral (mc.manuscriptcentral.com/hr). HR runs an editorial scoping screen before full review — "suitable data are a necessary but not sufficient feature to get to full peer review" — so the contribution and fit must be legible up front. Co-Editors-in-Chief are Smriti Anand and Penny Dick (检索于 2026-06；以官网为准).
When to trigger
- The user asks "what should I do next?" on an HR-targeted manuscript
- A draft needs its current bottleneck diagnosed
- Work is ping-ponging between theory, fieldwork/data, framing, writing, and the response letter
- An HR decision letter arrived and the user needs to switch into revision mode
- The team is weighing HR against Organization Studies, JMS, AMJ, or Organization
Routing table
| Current symptom | Next skill |
|---|---|
| Scope/audience fit uncertain; "is this an HR paper?" | humrel-topic-selection |
| Theory is thin, box-and-arrow, or under-engaged with social theory | humrel-theory-development |
| Contribution vs. adjacent conversations/journals is fuzzy | humrel-literature-positioning |
| Design choice and rigor (qual/critical/quant/mixed) unsettled | humrel-methods |
| Coding, estimation, or data-to-theory link is opaque | humrel-data-analysis |
| The "so what" / theoretical claim is not sharp | humrel-contribution-framing |
| Exhibits (data-structure table, models) hard to read | humrel-tables-figures |
| Prose flat; intro/abstract miss the reflexive HR register | humrel-writing-style |
| Anonymization, 13k cap, SAGE Harvard, portal preflight | humrel-submission |
| Want to calibrate scoping-screen odds / timeline / transfer | humrel-review-process |
| Received an R&R; need a response-letter strategy | humrel-rebuttal |
Default order
humrel-topic-selection— lock the work-and-society question and HR fithumrel-theory-development— build the social-theoretical enginehumrel-literature-positioning— stake the contribution vs. the conversationhumrel-methods— design (qual / critical / quant / mixed) with rigorhumrel-data-analysis— make the evidence-to-theory link transparenthumrel-contribution-framing— sharpen the one-sentence theoretical claimhumrel-tables-figures— exhibits that carry, not decoratehumrel-writing-style— the reflexive HR voice (intro + abstract last)humrel-submission— anonymized ScholarOne preflighthumrel-review-process— calibrate the scoping screen and developmental reviewhumrel-rebuttal— after the R&R
humrel-writing-styleis a late polish; do not rewrite the intro before the theory and evidence settle.
Show full SKILL.md (264 more words)Show less
Anti-patterns
- Treating HR as interchangeable with Organization Studies (EGOS), JMS, AMJ (US hypothesis-testing), or Organization (critical-only) — see the archetype table
- Sending a paper whose contribution is empirical-only ("we found X") with no theoretical advance — fails the scoping screen
- Polishing prose before theory, design, and the evidence hierarchy are stable
- Leaving author-identifying traces (acknowledgements, self-cites in first person, live URLs) in a double-anonymous submission
- Letting an appendix carry claims the 13k main text must establish
Routing by paper archetype
HR spans several traditions, and the binding constraint differs by archetype. Read the archetype, then enter the chain at the right link.
| Archetype | Likely first bottleneck | Enter at |
|---|---|---|
| Ethnographic / qualitative process study | data-to-theory transparency + theoretical payoff | humrel-theory-development → humrel-data-analysis |
| Critical / reflexive (power, identity, discourse) | sharpening the critique into a travelling contribution | humrel-literature-positioning → humrel-contribution-framing |
| Quantitative / survey / multilevel | construct validity + theorizing beyond the coefficient | humrel-methods → humrel-data-analysis |
| Mixed-methods | integration logic (why both, what each adds) | humrel-methods |
| Theory paper (no new data) | novelty + reach vs. existing organizational theory | humrel-theory-development |
Worked routing example (illustrative)
A user says: "My ethnography of platform couriers is rich, but a reviewer says it reads as 'a vivid case with thin theory' and feels closer to Work, Employment and Society than HR." That is two HR pushbacks — the data-to-theory ladder is invisible (owned by humrel-data-analysis) and the contribution is empirical not theoretical (owned by humrel-contribution-framing, scoped against siblings in humrel-literature-positioning). Route to theory and data first; only once the courier case yields a named, generative mechanism about control and identity at work — not just a labour-process description — do you return to humrel-writing-style and humrel-rebuttal.
Minimal decision snippet
if decision_letter_arrived: -> humrel-rebuttal
elif ready_to_submit: -> humrel-submission
elif exhibits_unclear: -> humrel-tables-figures
elif evidence_to_theory_opaque: -> humrel-data-analysis
elif design_or_rigor_unsettled: -> humrel-methods
elif claim_or_positioning_fuzzy: -> humrel-contribution-framing / humrel-literature-positioning
elif theory_thin: -> humrel-theory-development
else: -> humrel-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 Human-Relations-Skills/skills/humrel-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Humrel 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 |
|---|---|---|---|---|---|---|
| Humrel Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
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 Humrel Workflow
What does Humrel Workflow do?
A skill your agent uses when deciding which humrel- sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Human Relations (HR) submission. Humrel Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding which humrel- sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Human Relations (HR) submission.
When should I use Humrel Workflow?
Humrel Workflow fits situations like: deciding which humrel- sub-skill to invoke next; sequencing manuscript work from topic through rebuttal for a Human Relations (HR) submission.
How do I install Humrel Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill humrel-workflow -a claude-code`. Or copy the skill folder (Human-Relations-Skills/skills/humrel-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/humrel-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Humrel Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill humrel-workflow -a codex`. Or copy the skill folder (Human-Relations-Skills/skills/humrel-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/humrel-workflow in your project. Codex loads it when a task matches its description.
Can I use Humrel 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 humrel-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/humrel-workflow, .gemini/skills/humrel-workflow, .github/skills/humrel-workflow and .opencode/skills/humrel-workflow in your project.
What does Humrel Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Humrel Workflow is instructions for the agent only.
Does Humrel 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 Humrel 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 Humrel Workflow use?
Humrel 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 Humrel 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 Humrel Workflow?
Skills that share tags, products or a category with Humrel Workflow: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Humrel Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.