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 CVPR submission campaign end to end, covering the November abstract/paper/supplement deadline chain, coauthor reviewer-duty scheduling, the January rebuttal…
MITAuto-check passed
Install Cvpr Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cvpr-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/CVPR-Skills/skills/cvpr-workflow .claude/skills/cvpr-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 "cvpr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-workflow into .claude/skills/cvpr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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/CVPR-Skills/skills/cvpr-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 cvpr-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cvpr-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/CVPR-Skills/skills/cvpr-workflow .agents/skills/cvpr-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 "cvpr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-workflow into .agents/skills/cvpr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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 cvpr-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cvpr-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/CVPR-Skills/skills/cvpr-workflow .cursor/skills/cvpr-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 "cvpr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-workflow into .cursor/skills/cvpr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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 CVPR-Skills/skills/cvpr-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 cvpr-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cvpr-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/CVPR-Skills/skills/cvpr-workflow .gemini/skills/cvpr-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 "cvpr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-workflow into .gemini/skills/cvpr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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 cvpr-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 cvpr-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/CVPR-Skills/skills/cvpr-workflow .github/skills/cvpr-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 "cvpr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-workflow into .github/skills/cvpr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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 cvpr-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 cvpr-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/CVPR-Skills/skills/cvpr-workflow .opencode/skills/cvpr-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 "cvpr-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CVPR-Skills/skills/cvpr-workflow into .opencode/skills/cvpr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cvpr-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
cvpr-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 788 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 CVPR submission campaign end to end, covering the November abstract/paper/supplement deadline chain, coauthor reviewer-duty scheduling, the January rebuttal…
- Planning a CVPR submission campaign end to end
- SKILL.md covers Campaign calendar (2026-cycle…, The two windows people fail to…, Reviewer duty as a planned… and Multi-paper coordination, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the November abstract/paper/supplement deadline chain
What it does
Cvpr Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a CVPR submission campaign end to end, covering the November abstract/paper/supplement deadline chain, coauthor reviewer-duty scheduling, the January rebuttal sprint, February decisions, camera-ready and June conference logistics, and the resubmission ladder across ICCV, ECCV, and the next CVPR.
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 CVPR submission campaign end to end
- Covering the November abstract/paper/supplement deadline chain
- Coauthor reviewer-duty scheduling
- The January rebuttal sprint
Example prompts
- “/cvpr-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 (its code samples are yaml).
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
Cvpr Workflow loads about 1.7k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 788 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). 788 words, ~1,705 tokens.
Download SKILL.mdSave it as
.claude/skills/cvpr-workflow/SKILL.md (or your agent's skills folder).- name
- cvpr-workflow
- description
- Use when planning a CVPR submission campaign end to end, covering the November abstract/paper/supplement deadline chain, coauthor reviewer-duty scheduling, the January rebuttal sprint, February decisions, camera-ready and June conference logistics, and the resubmission ladder across ICCV, ECCV, and the next CVPR.
CVPR Workflow
CVPR is an annual machine with one intake: in the 2026 cycle, abstracts November 6, papers November 13, supplements November 20, rebuttal late January, decisions February 20, conference June 3–7 in Denver. This skill turns that spine into a project plan with owners, because CVPR deadline weeks are lost to coordination failures more often than to science failures.
Campaign calendar (2026-cycle anchors)
| When | Milestone | Owner discipline |
|---|---|---|
| T–10 weeks (early Sep) | Freeze scope: claims, benchmarks, baselines | PI + first author sign one paragraph |
| T–8 weeks | Experiment matrix running; recipe ledger live | Every table row has a config |
| T–6 weeks | First full draft; flip-test the figures | Co-authors annotate, don't rewrite |
| T–4 weeks (early Oct) | OpenReview profiles audited for every author | One named owner; new coauthors close the list |
| T–1 week (Nov 6) | Abstract registered; profiles valid | Desk-reject exposure if missed |
| Nov 13 | Paper + CRF submitted | Freeze 24h early; upload before the panic hour |
| Nov 20 | Supplement uploaded | Videos/code packaged per cvpr-supplementary |
| Dec – Jan 12 | Coauthors deliver their assigned reviews | Late reviews endanger your paper |
| Jan 22–29 | Reviews land; one-page rebuttal | Pre-book this week; nobody travels |
| Jan 30 – Feb 5 | Discussion (no author access) | Resist mailing the AC |
| Feb 20 | Decisions | Both branches pre-planned |
| Spring (待核实) | Camera-ready + dataset release due | See cvpr-camera-ready |
| Jun 3–7 | Conference (workshops 3–4, main 5–7 in 2026) | Poster/talk/travel logistics |
The two windows people fail to defend
Deadline fortnight (early November). The supplement trailing the paper by a week tempts teams to leave packaging "for week two" — then week two evaporates into video rendering and code scrubbing. Rule: the supplement plan (what goes in, who builds it) is written before the paper deadline; week two only executes it.
Rebuttal week (late January). Seven days, one page, all reviewers at once. Assign roles when reviews drop, not after a day of group grief:
# rebuttal-roles.yaml — filled within 12 hours of review release
reader: # summarizes all reviews neutrally, one page, no rebuttals yet
runner: # owns the 1-2 small requested experiments; hard stop at day 5
writer: # owns the single page; everyone else feeds bullets
adjudicator: # PI decides which objections get space, which get one line
deadline: # internal freeze 24h before OpenReview closeReviewer duty as a planned workload
Submitting enrolls qualifying authors into a 25k-reviewer pool, and undelivered or irresponsible reviews can desk-reject every paper the offender authored (verified 2026 enforcement). Treat December–January reviewing as a scheduled deliverable: at submission time, list which coauthors are likely reviewers, block their calendar for review weeks, and have the group's senior authors sanity-check first-time reviewers' drafts against the official reviewer guidelines.
Multi-paper coordination
Most labs submit several papers into the same November wall, which multiplies the process risks nonlinearly:
- Shared coauthors, shared exposure: one person's undelivered January review endangers every paper they touch; the duty ledger must be lab-level, not paper-level.
- Conflict hygiene: OpenReview conflicts must be complete across all submissions; a stale institution on one profile pollutes assignments for the whole batch.
- Compute contention: rebuttal-week reserve GPU allocations collide when three papers each promised "small requested experiments"; pre-negotiate priority order.
- Internal review: schedule lab-mates' cross-reads at T–10, not T–2 — at T–2 everyone is defending their own draft.
Show full SKILL.md (322 more words)Show less
The resubmission ladder
At a 25.42% acceptance rate, the rational plan covers rejection before it happens. The CV calendar offers a clean ladder — CVPR (Nov) → ICCV (spring deadline, odd years) / ECCV (spring deadline, even years) → WACV/3DV or back to CVPR. Rules for climbing:
- Bank the reviews: fix every factual objection before the next deadline; reviewer
pools overlap across CVF venues and repeat objections read badly (triage method in
cvpr-review-process). - Mind the dual-submission windows: the CVPR attestation covered Nov 13 – Feb 20 in 2026; the next venue's window must not overlap a paper still under CVPR review.
- Re-check freshness: three months of arXiv can obsolete a comparison table; budget a baseline-refresh pass, not just an edit pass.
Deadline fortnight, day by day
The last two weeks compress badly when run ad hoc. A schedule that has survived contact with real teams:
- T–14 to T–10: results freeze for the main table. New numbers after this go to the supplement or the rebuttal, not the body.
- T–10 to T–7: full-draft pass; run the figure flip test with an outsider; final baseline-freshness check against the leaderboard.
- T–7 (abstract day): register the abstract, verify every profile renders as complete when logged out of the authors' accounts, lock the author list.
- T–6 to T–3: claim-calibration pass (
cvpr-writing-style), bibliography venue verification (cvpr-related-work), CRF mandatory sections drafted. - T–2: full mechanical sweep from
cvpr-submission; internal freeze. - T–1: upload; re-download; cold read. Nobody edits after upload day.
- T to T+7 (supplement week): execute — do not design — the supplement plan; identity-scan code and videos; upload at T+5, not T+7, to survive a failed render.
Cycle-status note
As of 2026-07-08, CVPR 2026 has concluded and the CVPR 2027 cycle (Seattle, reported around June 20–24, 2027) had published no CFP or deadlines. Every date above is a 2026-cycle anchor for planning shape only — reopen cvpr.thecvf.com the moment your team commits, because the deadline chain (and things like the CRF) can change between editions.
Output format
[Campaign stage] scoping / building / deadline-fortnight / in-review / rebuttal / decided
[Calendar] next 3 milestones with dates and owners
[Duty ledger] reviewing coauthors + calendar blocked: yes/no
[Risk register] top 3 (missed-profile, supplement drift, rebuttal roles, …)
[Plan B] next venue + its verified deadline
[Cycle check] current-year pages reopened on: <date>© 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 CVPR-Skills/skills/cvpr-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cvpr 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 |
|---|---|---|---|---|---|---|
| Cvpr 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 | |
| Ad Campaign Analyzersickn33/agentic-awesome-skills | 47k | 1 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Ad Campaign Analyzergithub/awesome-copilot | 40k | 2 repos | ~3.5k | 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.
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.
Executing Marketing Campaigns
davila7/claude-code-templates
Plans, creates, and optimizes marketing campaigns including content strategy, social media, email, and analytics.
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 Cvpr Workflow
What does Cvpr Workflow do?
A skill your agent uses when planning a CVPR submission campaign end to end, covering the November abstract/paper/supplement deadline chain, coauthor reviewer-duty scheduling, the January rebuttal…. Cvpr Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a CVPR submission campaign end to end, covering the November abstract/paper/supplement deadline chain, coauthor reviewer-duty scheduling, the January rebuttal sprint, February decisions, camera-ready and June conference logistics, and the resubmission ladder across ICCV, ECCV, and the next CVPR.
When should I use Cvpr Workflow?
Cvpr Workflow fits situations like: planning a CVPR submission campaign end to end; covering the November abstract/paper/supplement deadline chain; coauthor reviewer-duty scheduling; the January rebuttal sprint.
How do I install Cvpr Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-workflow -a claude-code`. Or copy the skill folder (CVPR-Skills/skills/cvpr-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cvpr-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Cvpr Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-workflow -a codex`. Or copy the skill folder (CVPR-Skills/skills/cvpr-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cvpr-workflow in your project. Codex loads it when a task matches its description.
Can I use Cvpr 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 cvpr-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/cvpr-workflow, .gemini/skills/cvpr-workflow, .github/skills/cvpr-workflow and .opencode/skills/cvpr-workflow in your project.
What does Cvpr Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Cvpr Workflow is instructions for the agent only.
Does Cvpr 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 Cvpr 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 Cvpr Workflow use?
Cvpr 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 Cvpr Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Cvpr Workflow?
Skills that share tags, products or a category with Cvpr 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 Ad Campaign Analyzer (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cvpr 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.