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.
A skill your agent uses when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE…
MITAuto-check passed
Install Vis Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-workflow .claude/skills/vis-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 "vis-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-workflow into .claude/skills/vis-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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/VIS-Skills/skills/vis-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 vis-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-workflow .agents/skills/vis-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 "vis-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-workflow into .agents/skills/vis-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-workflow .cursor/skills/vis-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 "vis-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-workflow into .cursor/skills/vis-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 VIS-Skills/skills/vis-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 vis-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vis-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/VIS-Skills/skills/vis-workflow .gemini/skills/vis-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 "vis-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-workflow into .gemini/skills/vis-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-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 vis-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/VIS-Skills/skills/vis-workflow .github/skills/vis-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 "vis-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-workflow into .github/skills/vis-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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 vis-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 vis-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/VIS-Skills/skills/vis-workflow .opencode/skills/vis-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 "vis-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VIS-Skills/skills/vis-workflow into .opencode/skills/vis-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vis-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
vis-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 599 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 IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE…
- Planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines
- SKILL.md covers Milestones, Backward plan from the paper…, The annual-cycle reality and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The two-phase review
What it does
Vis Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE TVCG camera-ready, the Graphics Replicability Stamp, and presentation, with backward-planning offsets for a visualization paper and honest handling of the annual cycle and the second-round revision window.
Its SKILL.md is about 1.3k 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 IEEE VIS project timeline from area fit through the abstract and full-paper deadlines
- The two-phase review
- The conditional-accept second round
- The IEEE TVCG camera-ready
Example prompts
- “/vis-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
Vis Workflow loads about 1.3k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 599 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). 599 words, ~1,282 tokens.
Download SKILL.mdSave it as
.claude/skills/vis-workflow/SKILL.md (or your agent's skills folder).- name
- vis-workflow
- description
- Use when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE TVCG camera-ready, the Graphics Replicability Stamp, and presentation, with backward-planning offsets for a visualization paper and honest handling of the annual cycle and the second-round revision window.
VIS Workflow
Use this as the project-management skill for an IEEE VIS submission. Replace every date with the current official timetable and work backwards from the abstract deadline — which precedes the full-paper deadline and locks your author list. VIS publishes in IEEE TVCG, so plan for a likely conditional-accept second round inside the review cycle, not just an accept/reject.
VIS is a conference whose full papers are journal articles: the conference has no standing editor-in-chief, and the rotating analogue is the per-edition VIS Executive Committee, Overall Paper Chairs, and the six Area Paper Chairs (verify the roster on the current organizing page — 待核实 beyond named chairs). The cost model is conference registration; at least one author presents.
Milestones
- Area fit: confirm VIS over a sibling venue and pick the primary area among the six
(
vis-topic-selection). - Evidence lock: freeze the contribution type, the design rationale, the study/benchmark design, and the supplemental video plan.
- Abstract: submit real title, abstract, final author list, primary area, and keywords by the abstract deadline (VIS 2026: 21 March 2026).
- Full paper: upload the PDF (VIS 2026: 31 March 2026); title/abstract/PDF then freeze.
- Supplemental: finish and anonymize the video, code, and data in the one-week window (VIS 2026: 7 April 2026).
- First-round reviews: triage each comment by criterion (novelty, impact, evidence, methodology, encoding rationale, reproducibility).
- Conditional accept (if issued): execute a revision plus a summary-of-changes, re-read by the same reviewers against the required changes.
- Decision: archive reviews, response, and every submitted version.
- Acceptance: prepare the TVCG camera-ready, complete Open Practices disclosures, pursue the Graphics Replicability Stamp on its own track, register, and present.
Backward plan from the paper deadline
| Weeks out (heuristic) | Visualization-paper milestone |
|---|---|
| 10+ | Contribution type fixed; data/task abstraction and design rationale settled |
| 8 | Technique/system implemented; study or benchmark designed; preregistration filed if used |
| 6 | Study run / benchmark complete; effect sizes and CIs computed; figures drafted |
| 4 | Full draft in the VGTC/TVCG template; supplemental video shot |
| 3 | Internal mock review by a visualization reader |
| 2 | Encoding rationale hardened, related-work delta sharpened, 9-page budget met |
| 1 | Abstract submitted with final authors; anonymity sweep on PDF + video (if double-blind) |
| 0 | Full PDF uploaded; supplemental finished and anonymized in its extra week |
These offsets are planning heuristics only — anchor every one to the current call, never to a previous cycle's calendar.
Show full SKILL.md (217 more words)Show less
The annual-cycle reality
VIS runs a single annual full-paper cycle. Two planning consequences:
- A conditional accept has a hard second-round window. Under-budgeting the revision turns a winnable R&R into a reject; treat the required changes as a scored deadline, not a formality.
- Missing the annual deadline costs roughly a year at VIS; a sibling venue (EuroVis, PacificVis) or the TVCG journal track may have a nearer date — factor that into routing rather than idling.
Failure modes by stage
- Evidence still moving at week 4 forces last-minute studies nobody has audited — the classic methodology reject in the making.
- Leaving the video to the final week wastes VIS's extra supplemental week and ships an unpolished or identity-leaking video that reviewers judge harshly.
- Skipping the mock review forfeits the one chance to hear "your encoding is not justified" from a friend instead of a reviewer.
- Treating a conditional accept as an accept and under-budgeting the revision turns it into a rejection.
- Adding an author after the abstract deadline — not permitted; finalize authorship early.
Coordination notes
- Assign one owner for the supplemental video/code and another for the anonymity sweep; shared ownership is how both slip.
- Archive the exact submitted PDF, supplemental, and (later) summary-of-changes — the second round must quote them precisely and, if double-blind, stay anonymous through phase one.
Output format
[Current stage] idea / evidence / writing / abstract / submitted / conditional accept / accepted
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <page budget / anonymity / evidence / encoding rationale / video / second round>
[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 VIS-Skills/skills/vis-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vis 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 |
|---|---|---|---|---|---|---|
| Vis Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Project Timeline Reportthedotmack/claude-mem | 98k | 1 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GSAP Timelinegreensock/gsap-skills | 16k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Service Areathedaviddias/Front-End-Checklist | 74k | — | ~593 | 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
GSAP Timeline
greensock/gsap-skills
Teaches the GSAP timeline API for sequencing animations: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control.
Service Area
thedaviddias/Front-End-Checklist
A skill your agent uses when applies to service businesses (plumbers, lawyers, consultants) serving multiple regions.
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 Vis Workflow
What does Vis Workflow do?
A skill your agent uses when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE…. Vis Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE TVCG camera-ready, the Graphics Replicability Stamp, and presentation, with backward-planning offsets for a visualization paper and honest handling of the annual cycle and the second-round revision window.
When should I use Vis Workflow?
Vis Workflow fits situations like: planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines; the two-phase review; the conditional-accept second round; the IEEE TVCG camera-ready.
How do I install Vis Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-workflow -a claude-code`. Or copy the skill folder (VIS-Skills/skills/vis-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vis-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Vis Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vis-workflow -a codex`. Or copy the skill folder (VIS-Skills/skills/vis-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vis-workflow in your project. Codex loads it when a task matches its description.
Can I use Vis 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 vis-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/vis-workflow, .gemini/skills/vis-workflow, .github/skills/vis-workflow and .opencode/skills/vis-workflow in your project.
What does Vis Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Vis Workflow is instructions for the agent only.
Does Vis 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 Vis 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 Vis Workflow use?
Vis 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 Vis Workflow use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 Vis Workflow?
Skills that share tags, products or a category with Vis Workflow: Project Timeline Report (thedotmack/claude-mem, 98k stars), GSAP Timeline (greensock/gsap-skills, 16k stars), Service Area (thedaviddias/Front-End-Checklist, 74k 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 Vis 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.