Longbridge Research
helsome/folio
Institution ratings, consensus price targets, EPS/revenue forecasts, finance calendar, shareholder data, fund holders, insider trades (SEC Form 4), short interest, industry rankings, peer group…
A skill your agent uses when planning an IEEE ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible…
Install Icde Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-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/ICDE-Skills/skills/icde-workflow .claude/skills/icde-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 "icde-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-workflow into .claude/skills/icde-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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/ICDE-Skills/skills/icde-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 icde-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-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/ICDE-Skills/skills/icde-workflow .agents/skills/icde-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 "icde-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-workflow into .agents/skills/icde-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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 icde-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-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/ICDE-Skills/skills/icde-workflow .cursor/skills/icde-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 "icde-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-workflow into .cursor/skills/icde-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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 ICDE-Skills/skills/icde-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 icde-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-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/ICDE-Skills/skills/icde-workflow .gemini/skills/icde-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 "icde-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-workflow into .gemini/skills/icde-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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 icde-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 icde-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/ICDE-Skills/skills/icde-workflow .github/skills/icde-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 "icde-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-workflow into .github/skills/icde-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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 icde-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 icde-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/ICDE-Skills/skills/icde-workflow .opencode/skills/icde-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 "icde-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-workflow into .opencode/skills/icde-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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
icde-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 521 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 ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible…
- Planning an IEEE ICDE project timeline around the two-round-per-edition calendar
- SKILL.md covers The two-round unit, Milestones, Backward plan from the round… and Revision-bandwidth reasoning, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Choosing between the June and November research deadlines
What it does
Icde Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible revise-and-resubmit window, and backward-planning a data-engineering systems paper from CMT submission through review, camera-ready, and IEEE Xplore publication.
Its SKILL.md is about 1.1k 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 Business, Finance & HR, covering Budgeting and forecasting and Data pipelines and ETL. 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 ICDE project timeline around the two-round-per-edition calendar
- Choosing between the June and November research deadlines
- Budgeting for a possible revise-and-resubmit window
- Backward-planning a data-engineering systems paper from CMT submission through review
Example prompts
- “/icde-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
Icde Workflow loads about 1.1k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 521 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). 521 words, ~1,120 tokens.
Download SKILL.mdSave it as
.claude/skills/icde-workflow/SKILL.md (or your agent's skills folder).- name
- icde-workflow
- description
- Use when planning an IEEE ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible revise-and-resubmit window, and backward-planning a data-engineering systems paper from CMT submission through review, camera-ready, and IEEE Xplore publication.
ICDE Workflow
Use this as the project-management skill for an ICDE research submission. Replace every date with the current edition's official timetable and plan backward from the round you target.
ICDE is a conference, not a journal-of-the-conference: it has no standing editor-in-chief and
no article-processing charge. Leadership rotates per edition (General and Program Chairs named
on each icdeYYYY.github.io site), the cost model is registration, and accepted papers publish
in IEEE Xplore — not in a PACMMOD- or PVLDB-style venue journal. Re-check the current
organization page rather than carrying a name forward.
The two-round unit
Unlike SIGMOD's four quarterly PACMMOD rounds or PVLDB's twelve monthly deadlines, ICDE gives you two shots per edition and no more. ICDE 2027's Round 1 paper deadline was June 11, 2026; Round 2 is November 11, 2026 with notification February 10, 2027. Because a Round 1 reject cannot re-enter Round 2, the round choice is a real commitment, not a convenience.
Milestones
- Venue and round fit: confirm the contribution is a data-management primitive and that the chosen round is reachable without rushing the evaluation.
- Evidence lock: freeze the mechanism, workloads, baselines, scale grid, and the claims map.
- Paper deadline (CMT): upload the IEEE-format PDF plus supplemental material; file all co-author conflicts.
- Review release: triage correctness, novelty, evaluation soundness, and reproducibility.
- Revision window (if invited): ICDE 2026 granted invited revisions a 4-week window with a re-review before the final decision; budget for it or forfeit it (revision status for the current edition is 待核实 — confirm).
- Decision: archive reviews, the revision, and the submitted versions.
- Camera-ready + Xplore: IEEE eCF/PDF-eXpress checks, copyright form, final artifact release, registration, and in-person presentation.
Show full SKILL.md (251 more words)Show less
Backward plan from the round paper deadline
| Weeks out (heuristic) | Systems-paper milestone |
|---|---|
| 10+ | System implemented; workloads and baselines chosen |
| 8 | Scale grid running; measurement harness logging seeds and variance |
| 6 | All main-result runs complete; crossover/cost analysis drafted |
| 4 | Full draft sitting in IEEE two-column format |
| 3 | Internal mock review by a builder who did not write the system |
| 2 | Supplement assembled: run_all.sh, run_small.sh, README, generators |
| 1 | CMT profiles + conflicts filed; page count and format sweep |
| 0 | PDF and supplement in CMT before the round cutoff |
These offsets are planning heuristics — anchor each to the current important-dates page, never to a past edition's calendar.
Revision-bandwidth reasoning
- If your target round can return a Revise & Resubmit, the honest question at submission time is whether the team has four weeks of free bandwidth in the revision window; a revision you cannot execute is a reject in slow motion.
- The two-round structure means a missed Round 1 pushes you to Round 2 of the same edition (five months later) but a Round 1 reject pushes you a whole edition back — price both outcomes before choosing.
Failure modes by stage
- Treating the two rounds as interchangeable and burning Round 1 on an unfinished evaluation, losing the whole edition.
- Leaving IEEE format conversion to the final week, when two-column overflow surfaces late.
- Skipping the builder mock review — the one chance to hear "your baseline is untuned" from a colleague instead of a reviewer.
- Assuming a revision window exists for the current edition without confirming it.
Output format
[Current stage] idea / building / measuring / writing / submission / revision / accepted
[Target round] Round 1 or Round 2 (edition), with next official deadline + source
[Critical path] <three tasks that determine readiness>
[Revision reserve] <weeks of bandwidth available if R&R returns>
[Risk register] <round-choice / format / evaluation / reproducibility / presentation>
[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 ICDE-Skills/skills/icde-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icde 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 |
|---|---|---|---|---|---|---|
| Icde Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Longbridge Researchhelsome/folio | 270 | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Bet SizingJoelLewis/finance_skills | 205 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Cre Asset Managementahacker-1/cre-agent-skills | 113 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Dd LogsDataDog/pup | 1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Cash Flow ForecastWellApp-ai/Well | 345 | — | ~567 | Automated safety check: Pass | MIT |
Similar skills
Bet Sizing
JoelLewis/finance_skills
Determine how much capital to allocate to individual positions within a portfolio.
Cre Asset Management
ahacker-1/cre-agent-skills
CRE Asset Management analysis suite — 9 specialist skills for post-acquisition multifamily operations including annual budgeting, monthly variance analysis, rent collection, renewal decisions…
- Official
Dd Logs
DataDog/pup
Log management - search, pipelines, archives, and cost control.
Cash Flow Forecast
WellApp-ai/Well
Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions.
Cash Flow Snapshot
sandbaseai/sandbase-skills
Create a 30/60/90-day cash-flow forecast from AR, AP, opening cash, payment timing, and fixed-cost data.
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 Icde Workflow
What does Icde Workflow do?
A skill your agent uses when planning an IEEE ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible…. Icde Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible revise-and-resubmit window, and backward-planning a data-engineering systems paper from CMT submission through review, camera-ready, and IEEE Xplore publication.
When should I use Icde Workflow?
Icde Workflow fits situations like: planning an IEEE ICDE project timeline around the two-round-per-edition calendar; choosing between the June and November research deadlines; budgeting for a possible revise-and-resubmit window; backward-planning a data-engineering systems paper from CMT submission through review.
How do I install Icde Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-workflow -a claude-code`. Or copy the skill folder (ICDE-Skills/skills/icde-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icde-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Icde Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-workflow -a codex`. Or copy the skill folder (ICDE-Skills/skills/icde-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icde-workflow in your project. Codex loads it when a task matches its description.
Can I use Icde 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 icde-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/icde-workflow, .gemini/skills/icde-workflow, .github/skills/icde-workflow and .opencode/skills/icde-workflow in your project.
What does Icde Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Icde Workflow is instructions for the agent only.
Does Icde 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 Icde 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 Icde Workflow use?
Icde 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 Icde Workflow use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Icde Workflow?
Skills that share tags, products or a category with Icde Workflow: Longbridge Research (helsome/folio, 270 stars), Bet Sizing (JoelLewis/finance_skills, 205 stars), Cre Asset Management (ahacker-1/cre-agent-skills, 113 stars) and Dd Logs (DataDog/pup, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icde 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.