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 reasoning about how an ICDT (International Conference on Database Theory) submission is evaluated, covering the two-submission-cycle model, the first-cycle revision…
MITAuto-check passed
Install Icdt Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-review-process --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-review-process .claude/skills/icdt-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-review-process into .claude/skills/icdt-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-review-process --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-review-process .agents/skills/icdt-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-review-process into .agents/skills/icdt-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-review-process --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-review-process .cursor/skills/icdt-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-review-process into .cursor/skills/icdt-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-review-process --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-review-process .gemini/skills/icdt-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-review-process into .gemini/skills/icdt-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/icdt-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-review-process into .github/skills/icdt-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/icdt-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-review-process into .opencode/skills/icdt-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-review-process", 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-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 696 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about how an ICDT (International Conference on Database Theory) submission is evaluated, covering the two-submission-cycle model, the first-cycle revision…
- Reasoning about how an ICDT (International Conference on Database Theory) submission is evaluated
- SKILL.md covers Process model, Reading a decision against the…, How ICDT differs from its… and Who reads you, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the two-submission-cycle model
What it does
Icdt Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an ICDT (International Conference on Database Theory) submission is evaluated, covering the two-submission-cycle model, the first-cycle revision (Accept / Revise / Reject) decision, anonymous review since 2024, the cross-cycle resubmission restriction, proof-correctness scrutiny by a database-theory PC, and how ICDT's process differs from PODS and from the co-located EDBT systems track.
Its SKILL.md is about 1.5k 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
- Reasoning about how an ICDT (International Conference on Database Theory) submission is evaluated
- Covering the two-submission-cycle model
- The first-cycle revision (Accept / Revise / Reject) decision
- Anonymous review since 2024
Example prompts
- “/icdt-review-process”
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 Review Process loads about 1.5k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 696 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). 696 words, ~1,507 tokens.
Download SKILL.mdSave it as
.claude/skills/icdt-review-process/SKILL.md (or your agent's skills folder).- name
- icdt-review-process
- description
- Use when reasoning about how an ICDT (International Conference on Database Theory) submission is evaluated, covering the two-submission-cycle model, the first-cycle revision (Accept / Revise / Reject) decision, anonymous review since 2024, the cross-cycle resubmission restriction, proof-correctness scrutiny by a database-theory PC, and how ICDT's process differs from PODS and from the co-located EDBT systems track.
ICDT Review Process
Model the pipeline before interpreting any single review. ICDT's process is built around two submission cycles per year and a first-cycle revision option, and the reviewing bar is proof correctness: the referees are database theorists who will check the argument, not just weigh the idea. The most consequential mental shift for authors arriving from a systems venue is that a wrong or incomplete proof is not a "revise" — it is often a reject, because the contribution is the theorem.
Process model
- Submission and review run on Microsoft CMT with anonymous review (regular track, since 2024): the PC does not see author identities.
- Each cycle has an abstract deadline then a paper deadline about a week later; the PC bids and is assigned from the registered abstracts.
- Cycle 1 decisions are Accept, Revise-and-resubmit, or Reject. A "revise" is a genuine invitation to fix identified gaps and return within the cycle for a second read.
- Cycle 2 reaches a final Accept/Reject. A paper rejected in Cycle 1 cannot be resubmitted to Cycle 2 unless the reviewers explicitly invited it — the cycles are not two independent lotteries.
- Accepted papers publish open access in LIPIcs (Schloss Dagstuhl), so camera-ready proof completeness and metadata matter as much as the verdict.
Reading a decision against the categories
| Decision | What it means | Author move |
|---|---|---|
| Accept | The theorem holds and the advance is real; polish only | Camera-ready; finalize the full-version proofs; do not reopen scope |
| Revise-and-resubmit (Cycle 1) | A fixable gap: a case in a proof, a missing bound, an unclear model | Treat as a deadline: fix each identified point and document it in the revised version |
| Reject | Structural: a broken proof, a known result, a model with no consequence | Do not resubmit to Cycle 2 uninvited; repair deeply or reroute (PODS / a journal) |
The strategic reading: an ICDT referee distinguishes a gap you can close (a missing lemma, a special case) from a claim that is wrong (the main theorem fails). Write so that any weakness a referee finds is of the first kind — an argument you can complete in the revision — not the second.
Show full SKILL.md (345 more words)Show less
How ICDT differs from its siblings
- vs. PODS: PODS is the other database-theory flagship, but North-American-leaning, co-located with SIGMOD, and now published in ACM PACMMOD. ICDT is the European venue, co-located with EDBT, published open access in LIPIcs, and runs a two-cycle calendar with a revision option rather than PODS's ACM-journal framing. The scope overlaps heavily; the calendar, publisher, and revision mechanics do not. Never assume a shared deadline or template.
- vs. EDBT (the co-located systems track): EDBT reviews systems and experimental data-management work with reproducibility expectations; ICDT reviews theorems. Being in the same building and the same week does not mean the same reviewer culture — an ICDT referee wants a proof, not a benchmark.
- vs. LICS / ICALP / STACS: these EATCS-adjacent theory venues share ICDT's proof rigor but not its data-management framing; ICDT rewards a result whose consequence for querying, constraints, or data is clear, not theory for its own sake.
Who reads you
Expect referees from your subarea of database theory — query languages, finite model theory, complexity of query evaluation, consistent query answering, provenance, or data-integration theory. They will read the proofs, look for the model of computation and the exact complexity class, check whether upper and lower bounds match, and notice an unstated assumption that makes a theorem easier than advertised. Vague "it can be shown that" statements are caught, not skimmed.
Where author leverage actually exists
[Before submission] precise abstract + subject areas -> the right referees (largest lever)
[Cycle choice] target Cycle 1 if the proof might still move (revision option)
[Revision round] the strongest lever: close every identified gap and say where you did
[After reject] no uninvited Cycle-2 carry; reroute to PODS or a journal (TODS/LMCS/TheoretiCS)A revision succeeds when it closes the specific gap the referees named and documents the change; it fails when it argues that the gap does not matter. Silent non-fixes — an identified missing case left unaddressed — turn the second read into a reject.
Misreadings to avoid
- Treating "revise" as an accept — the second read re-checks the proof; budget the revision window like a deadline.
- Treating Cycle 2 as a retry lane — the cross-cycle rule blocks uninvited resubmission of a Cycle-1 reject.
- Assuming a systems-style rebuttal exists — ICDT's mechanism is the revision, not a short rebuttal letter (confirm the current cycle's exact author-interaction rules; 待核实).
- Confusing ICDT with PODS process — different publisher, calendar, and revision model.
Output format
[Process stage] pre-submission / awaiting Cycle-N decision / revising / final / accepted
[Decision category] accept / revise / reject, with the criterion (correctness | novelty | consequence)
[Referee map] each point -> proof gap | model unclear | known result | bound not tight | scope
[Leverage plan] the next-stage action (which gap to close) that can change the outcome
[Forbidden moves] uninvited Cycle-2 resubmission / identity leak / unproved claim left standing© 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-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icdt Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | 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 | |
| Deepseek Reasonruvnet/ruflo | 74k | — | ~626 | Automated safety check: Notes | 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.
Deepseek Reason
ruvnet/ruflo
Reasoning-mode completion against DeepSeek's deepseek-reasoner model (R1) via /v1/chat/completions.
- 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 Review Process
What does Icdt Review Process do?
A skill your agent uses when reasoning about how an ICDT (International Conference on Database Theory) submission is evaluated, covering the two-submission-cycle model, the first-cycle revision…. Icdt Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an ICDT (International Conference on Database Theory) submission is evaluated, covering the two-submission-cycle model, the first-cycle revision (Accept / Revise / Reject) decision, anonymous review since 2024, the cross-cycle resubmission restriction, proof-correctness scrutiny by a database-theory PC, and how ICDT's process differs from PODS and from the co-located EDBT systems track.
When should I use Icdt Review Process?
Icdt Review Process fits situations like: reasoning about how an ICDT (International Conference on Database Theory) submission is evaluated; covering the two-submission-cycle model; the first-cycle revision (Accept / Revise / Reject) decision; anonymous review since 2024.
How do I install Icdt Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-review-process -a claude-code`. Or copy the skill folder (ICDT-Skills/skills/icdt-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icdt-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Icdt Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-review-process -a codex`. Or copy the skill folder (ICDT-Skills/skills/icdt-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icdt-review-process in your project. Codex loads it when a task matches its description.
Can I use Icdt Review Process 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-review-process -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-review-process, .gemini/skills/icdt-review-process, .github/skills/icdt-review-process and .opencode/skills/icdt-review-process in your project.
What does Icdt Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Icdt Review Process is instructions for the agent only.
Does Icdt Review Process 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 Review Process 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 Review Process use?
Icdt Review Process 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 Review Process use?
About 1.5k tokens (SKILL.md is roughly 6k 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 Review Process?
Skills that share tags, products or a category with Icdt Review Process: Internal Comms (alirezarezvani/claude-skills, 28k stars), Internal Communication (sickn33/agentic-awesome-skills, 47k stars), Deepseek Reason (ruvnet/ruflo, 74k 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 Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.