Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline…
Install Iccv Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-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/ICCV-Skills/skills/iccv-workflow .claude/skills/iccv-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 "iccv-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-workflow into .claude/skills/iccv-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-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/ICCV-Skills/skills/iccv-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 iccv-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-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/ICCV-Skills/skills/iccv-workflow .agents/skills/iccv-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 "iccv-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-workflow into .agents/skills/iccv-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-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 iccv-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-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/ICCV-Skills/skills/iccv-workflow .cursor/skills/iccv-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 "iccv-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-workflow into .cursor/skills/iccv-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-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 ICCV-Skills/skills/iccv-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 iccv-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-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/ICCV-Skills/skills/iccv-workflow .gemini/skills/iccv-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 "iccv-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-workflow into .gemini/skills/iccv-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-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 iccv-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 iccv-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/ICCV-Skills/skills/iccv-workflow .github/skills/iccv-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 "iccv-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-workflow into .github/skills/iccv-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-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 iccv-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 iccv-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/ICCV-Skills/skills/iccv-workflow .opencode/skills/iccv-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 "iccv-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-workflow into .opencode/skills/iccv-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-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
iccv-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 824 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline…
- Works in 4 steps: Reviews were fixable → ECCV (the… → Reviews said "sound but not exciting" →… → Reviews revealed a missing foundation →… → …
- Project-managing an ICCV campaign across the odd-year cycle
- SKILL.md covers The autumn fork (the decision…, Cycle plan with owners…, Two ICCV-specific project risks and International logistics are…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Iccv Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline, May rebuttal week, late-June decisions, the October conference with international travel and visa lead times, and the ECCV/CVPR fallback ladder if the paper misses.
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
- Project-managing an ICCV campaign across the odd-year cycle
- Covering the autumn fork between CVPR and ICCV
- The early-March registration and single submission deadline
- May rebuttal week
Example prompts
- “/iccv-workflow”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Reviews were fixable → ECCV (the following even-year spring) or the next
- Reviews said "sound but not exciting" → in 2025, the new Findings workshop
- Reviews revealed a missing foundation → journal track (TPAMI/IJCV) after
- Idea overtaken during review → salvage the reusable component; do not
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
Iccv Workflow loads about 1.7k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 824 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). 824 words, ~1,749 tokens.
Download SKILL.mdSave it as
.claude/skills/iccv-workflow/SKILL.md (or your agent's skills folder).- name
- iccv-workflow
- description
- Use when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline, May rebuttal week, late-June decisions, the October conference with international travel and visa lead times, and the ECCV/CVPR fallback ladder if the paper misses.
ICCV Workflow
An ICCV campaign runs on a spring-deadline, autumn-conference rhythm that only exists in odd years. The 2025 cycle — the most recent completed one, verified 2026-07-08 — ran: paper registration March 3, full submission and supplementary March 7 (11:59pm HST), reviews to authors May 9, rebuttal May 10–16, decisions late June, conference October 19–23 in Honolulu (workshops the 19th–20th, main program the 21st–23rd). ICCV 2027 is announced for Hong Kong in early October 2027; its deadline chain was unpublished at check time, so every date below is a 2025-cycle anchor for shape, not a promise.
The autumn fork (the decision nobody schedules)
The ICCV cycle actually begins the previous autumn, when the team must choose between the imminent CVPR deadline (November) and holding four more months for ICCV (March). Make the fork an explicit meeting with a written outcome:
- Hold for ICCV when the missing evidence is real (a benchmark, a user study, a second domain) and four months genuinely closes it.
- Take CVPR when the paper is submittable now — holding a finished paper four months in a field with weekly arXiv turnover is negative-expected-value.
- Never split the difference by submitting to CVPR "as a free review round"; overlapping CVF reviewer pools remember, and dual-submission windows can trap a paper that gets held over.
Cycle plan with owners (2025-shaped)
| Window | Milestone | Failure this window causes |
|---|---|---|
| Sep–Oct (year before) | Autumn fork decided; claims frozen in one paragraph | Zombie project drifting between deadlines |
| Nov–Dec | Experiment matrix runs; draft skeleton with figure slots | March becomes an experiments deadline, not a writing one |
| Jan | Full internal draft; outside reader pass | No time to act on feedback |
| Feb | Baseline-freshness audit; anonymity sweep; supplement built in parallel | Same-day supplement rule catches the team |
| ~Mar 3 | Registration: title, abstract, full author list, complete OpenReview profiles | Registration lapse = no submission |
| ~Mar 7 | Paper + supplement, one upload event (2025: 11:59pm HST) | Anything unfinished is unfinished forever |
| Mar–May | Coauthors serve reviewer assignments — every author reviews at ICCV | Late reviews can desk-reject your paper |
| ~May 9–16 | Reviews land; seven-day rebuttal | Week lost to shock instead of triage |
| Late Jun | Decision | No plan B drafted |
| Summer | Camera-ready (exact 2025 deadline 待核实); artifact release runway | Promises to reviewers quietly expire |
| Oct | Conference week abroad | Visa/travel booked too late |
Note the timezone trap: 2025's deadline was Hawaii Standard Time — generous for Europe and Asia, but teams that reflexively assume AoE have missed CVF deadlines in both directions. Read the clock on the current Dates page, not from habit.
Two ICCV-specific project risks
The unified deadline. Since 2025, ICCV takes paper and supplementary material on the same day (an announced process change — it also shortened the decision timeline). Plan the supplement as a parallel workstream from February, with its own owner. Teams migrating from CVPR habits still budget a "supplement week" that no longer exists.
Reviewer duty with teeth. Every author is expected to review unless exempt (those new to or outside the vision community were exempted in 2025), each author may register at most 25 submissions, and the 2025 chairs enforced quality: 25 reviewers were judged highly irresponsible and 29 of their authored papers were desk-rejected, 12 of which would otherwise have been accepted. Treat coauthor review assignments as deliverables on the project plan with a senior reviewer proofreading first-timers' drafts.
Show full SKILL.md (277 more words)Show less
International logistics are part of the plan
ICCV rotates internationally by design — Honolulu in 2025, Hong Kong announced for 2027. For many team members that means visas, and visa appointment queues in some countries exceed the June-decision-to-October-conference gap. Do not wait for the decision:
travel-readiness ledger (start at submission, not at acceptance)
per author: passport expiry ≥ 6 months past conference? visa type needed?
appointment backlog in their country (weeks)?
per paper: who presents if the first author cannot travel?
funding source confirmed for at least one presenter?
deadline: visa paperwork drafted by decision day, filed within a week of itThe fallback ladder (the biennial part)
Missing ICCV costs two years of ICCV, but not two years of publishing. Draft the ladder before decisions arrive:
- Reviews were fixable → ECCV (the following even-year spring) or the next CVPR (November): repair every factual objection first; pools overlap.
- Reviews said "sound but not exciting" → in 2025, the new Findings workshop accepted technically sound rejected/withdrawn ICCV papers (a post-decision outlet — check whether it recurs); or WACV for application-leaning work.
- Reviews revealed a missing foundation → journal track (TPAMI/IJCV) after real revision, or back to the bench.
- Idea overtaken during review → salvage the reusable component; do not resubmit a superseded comparison table anywhere.
Multi-paper labs, odd-year edition
In odd years a vision lab may push papers at CVPR (Nov), ICCV (Mar), and ICCV workshops (summer CFPs) with the same people. Lab-level coordination: one shared duty roster (a single delinquent reviewer-coauthor endangers every ICCV paper the lab submitted), one shared compute reservation for rebuttal week in May, and one person owning OpenReview profile hygiene across all submissions — the 2025 cycle required complete profiles at registration.
Reverify before trusting any date here
- The entire 2027 chain: registration/paper deadlines, timezone, rebuttal window, decision date, camera-ready — all 待核实 until iccv.thecvf.com posts them.
- Whether the single paper+supplement deadline persists.
- Whether Findings runs again in 2027.
- Registration and presentation obligations for accepted papers (not verified even for 2025 — 待核实).
Output format
[Cycle position] autumn-fork / building / deadline-month / in-review / rebuttal / decided / pre-conference
[Next 3 milestones] <date — item — owner>
[Duty roster] coauthor reviewer assignments tracked: yes/no
[Supplement workstream] parallel owner assigned: yes/no
[Travel readiness] visas/funding per presenter: green/amber/red
[Fallback ladder] <ranked next venues with their real deadlines>© 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 ICCV-Skills/skills/iccv-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Iccv 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 |
|---|---|---|---|---|---|---|
| Iccv 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 Iccv Workflow
What does Iccv Workflow do?
A skill your agent uses when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline…. Iccv Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline, May rebuttal week, late-June decisions, the October conference with international travel and visa lead times, and the ECCV/CVPR fallback ladder if the paper misses.
When should I use Iccv Workflow?
Iccv Workflow fits situations like: project-managing an ICCV campaign across the odd-year cycle; covering the autumn fork between CVPR and ICCV; the early-March registration and single submission deadline; may rebuttal week.
How do I install Iccv Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-workflow -a claude-code`. Or copy the skill folder (ICCV-Skills/skills/iccv-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iccv-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Iccv Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-workflow -a codex`. Or copy the skill folder (ICCV-Skills/skills/iccv-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iccv-workflow in your project. Codex loads it when a task matches its description.
Can I use Iccv 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 iccv-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/iccv-workflow, .gemini/skills/iccv-workflow, .github/skills/iccv-workflow and .opencode/skills/iccv-workflow in your project.
What does Iccv Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Iccv Workflow is instructions for the agent only.
Does Iccv 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 Iccv 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 Iccv Workflow use?
Iccv 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 Iccv Workflow use?
About 1.7k 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 Iccv Workflow?
Skills that share tags, products or a category with Iccv 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 Iccv 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.