Internal Comms
alirezarezvani/claude-skills
A skill your agent uses when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement…
A skill your agent uses when planning an ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline…
MITAuto-check passed
Install Icdt Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-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/ICDT-Skills/skills/icdt-workflow .claude/skills/icdt-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 "icdt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-workflow into .claude/skills/icdt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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/ICDT-Skills/skills/icdt-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 icdt-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-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/ICDT-Skills/skills/icdt-workflow .agents/skills/icdt-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 "icdt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-workflow into .agents/skills/icdt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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 icdt-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-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/ICDT-Skills/skills/icdt-workflow .cursor/skills/icdt-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 "icdt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-workflow into .cursor/skills/icdt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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 ICDT-Skills/skills/icdt-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 icdt-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-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/ICDT-Skills/skills/icdt-workflow .gemini/skills/icdt-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 "icdt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-workflow into .gemini/skills/icdt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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 icdt-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 icdt-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/ICDT-Skills/skills/icdt-workflow .github/skills/icdt-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 "icdt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-workflow into .github/skills/icdt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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 icdt-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 icdt-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/ICDT-Skills/skills/icdt-workflow .opencode/skills/icdt-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 "icdt-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-workflow into .opencode/skills/icdt-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-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
icdt-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 414 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 ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline…
- Planning an ICDT (International Conference on Database Theory) campaign end to end
- SKILL.md covers The two-cycle calendar (verify…, Choosing the cycle, Backward plan from a paper… and After the deadline, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration
What it does
Icdt Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration, the first-cycle revision round, LIPIcs camera-ready, and presentation at the co-located EDBT/ICDT event.
Its SKILL.md is about 1.2k 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 ICDT (International Conference on Database Theory) campaign end to end
- Running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration
- The first-cycle revision round
- LIPIcs camera-ready
Example prompts
- “/icdt-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
Icdt Workflow loads about 1.2k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 414 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). 414 words, ~1,230 tokens.
Download SKILL.mdSave it as
.claude/skills/icdt-workflow/SKILL.md (or your agent's skills folder).- name
- icdt-workflow
- description
- Use when planning an ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration, the first-cycle revision round, LIPIcs camera-ready, and presentation at the co-located EDBT/ICDT event.
ICDT Workflow
Plan the campaign backward from a chosen cycle deadline. ICDT's defining calendar feature is two submission cycles per year, so the first planning act is not "when is the deadline" but "which cycle, and does the Cycle-1 revision option help me?" Everything downstream — abstract registration, the revision window, LIPIcs camera-ready, and the talk at the co-located EDBT/ICDT event — hangs off that choice.
The two-cycle calendar (verify live dates)
Using ICDT 2027 (Lille) as the concrete snapshot, all AoE:
Cycle 1: abstracts 3 Mar 2026 -> papers 10 Mar 2026 -> notification 1 Jun 2026 (Accept/Revise/Reject)
Cycle 2: abstracts 3 Sep 2026 -> papers 10 Sep 2026 -> notification 1 Dec 2026 (Accept/Reject)
Event: EDBT/ICDT 2027, Lille, France, 6-9 April 2027 (ICDT sessions 6-8 April per the CfP)As of 2026-07-09, Cycle 1 is decided and Cycle 2 (papers 10 Sep 2026) is the immediate live target. Reconfirm every date against the current databasetheory.org call before you commit — the two cycles do not always both run, and the dates shift per edition.
Choosing the cycle
| Situation | Target | Why |
|---|---|---|
| Proof is complete and polished now | Whichever cycle is nearer | No reason to wait; both publish in the same volume year |
| Main theorem holds but a case or bound may still move | Cycle 1 | The revision option lets referees ask for the fix instead of rejecting |
| Result not yet fully proved | Later cycle / next year | A one-sided bound or a gap invites a reject; finish first |
| Rejected in Cycle 1 (not invited back) | Not Cycle 2 | The cross-cycle rule blocks uninvited resubmission; reroute or wait |
Backward plan from a paper deadline (D)
D minus 8-10 weeks : freeze theorem statements; decide ICDT vs PODS (icdt-topic-selection)
D minus 6 weeks : full proofs written; identify what goes in body vs the marked appendix
D minus 3 weeks : draft in lipics-v2021; body within 15 pages excl. refs; appendix holds proofs
D minus 1 week : register the abstract in the chosen cycle (abstract deadline is ~a week before D)
D minus 3 days : anonymity sweep (icdt-submission); self-citations neutralized; metadata scrubbed
D : upload to Microsoft CMT; re-download and read coldAfter the deadline
[Awaiting decision] calibrate with icdt-review-process; prepare nothing you cannot support
[If Revise (Cycle 1)] treat the revision window as a deadline: close each named gap, document it,
resubmit within the cycle (icdt-author-response)
[If Accept] LIPIcs camera-ready (icdt-camera-ready): lipics-v2021 final, CCS + keywords +
ORCID, complete proofs, DOI on DROPS; post/refresh the full version (arXiv)
[If Reject] reroute per icdt-topic-selection (PODS / a journal); do not carry into Cycle 2
uninvitedShow full SKILL.md (189 more words)Show less
The revision window (Cycle 1)
A Cycle-1 "revise" is the highest-leverage moment in the calendar. Budget it like a submission: list every point the referees raised, close the ones about correctness first (a missing case, an unproved lemma), then the ones about clarity, and write a short account of what changed and where. The same referees re-read; an unaddressed correctness point is what turns a revision into a reject.
Presentation at EDBT/ICDT
- Accepted ICDT papers are presented at the joint EDBT/ICDT event — the same week and venue as the EDBT systems track. Expect a mixed audience; pitch the talk to the theory-literate but keep the data-management motivation legible to systems attendees.
- At least one author presents; plan travel around the April event window.
- Watch for co-located Test-of-Time and Best-Paper / Best-Newcomer announcements — the community norms your paper is measured against are visible in those talks.
Reverify each cycle
- Which cycles run this edition and their exact AoE dates.
- The revision-window length and the exact cross-cycle resubmission wording.
- The event dates and city (EDBT/ICDT rotates: Tampere 2026, Lille 2027).
- The LIPIcs class revision and page limit for the camera-ready.
Output format
[Target] ICDT 20NN, Cycle 1 / Cycle 2, paper deadline <date, AoE>
[Cycle rationale] complete-now / revision-hedge / finish-first
[Backward plan] <milestones with dates back from D>
[Post-decision] awaiting / revising / camera-ready / rerouting
[Next skill] icdt-submission | icdt-author-response | icdt-camera-ready | icdt-topic-selection© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ICDT-Skills/skills/icdt-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icdt 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 |
|---|---|---|---|---|---|---|
| Icdt Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Internal Commsalirezarezvani/claude-skills | 28k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Internal Communicationsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Marketing Campaignaffaan-m/ECC | 276k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Internal Communications Writeranthropics/skills | 180k | 38 repos | ~378 | Automated safety check: Pass | Apache-2.0 | |
| Internal Comms Anthropicsickn33/agentic-awesome-skills | 47k | 1 repos | ~702 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Internal Communication
sickn33/agentic-awesome-skills
Internal communication log: title, type, date, department, host and attendees, agenda, action items, follow-up date, meeting link and delivery status.
Marketing Campaign
affaan-m/ECC
End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.
- Official
Internal Communications Writer
anthropics/skills
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill…
Internal Comms Anthropic
sickn33/agentic-awesome-skills
Compatibility alias for internal-comms: draft status updates, newsletters and FAQs from approved sources.
Nofollow Internal
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing internal link structure or reviewing link attributes.
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 Icdt Workflow
What does Icdt Workflow do?
A skill your agent uses when planning an ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline…. Icdt Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration, the first-cycle revision round, LIPIcs camera-ready, and presentation at the co-located EDBT/ICDT event.
When should I use Icdt Workflow?
Icdt Workflow fits situations like: planning an ICDT (International Conference on Database Theory) campaign end to end; running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration; the first-cycle revision round; LIPIcs camera-ready.
How do I install Icdt Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-workflow -a claude-code`. Or copy the skill folder (ICDT-Skills/skills/icdt-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icdt-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Icdt Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-workflow -a codex`. Or copy the skill folder (ICDT-Skills/skills/icdt-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icdt-workflow in your project. Codex loads it when a task matches its description.
Can I use Icdt 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 icdt-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/icdt-workflow, .gemini/skills/icdt-workflow, .github/skills/icdt-workflow and .opencode/skills/icdt-workflow in your project.
What does Icdt Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Icdt Workflow is instructions for the agent only.
Does Icdt 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 Icdt 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 Icdt Workflow use?
Icdt 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 Icdt Workflow use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Icdt Workflow?
Skills that share tags, products or a category with Icdt Workflow: Internal Comms (alirezarezvani/claude-skills, 28k stars), Internal Communication (sickn33/agentic-awesome-skills, 47k stars), Marketing Campaign (affaan-m/ECC, 276k stars) and Internal Communications Writer (anthropics/skills, 180k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icdt 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.