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 deciding what counts as evidence for an ICDT (International Conference on Database Theory) result — matching-bound complexity analysis as the primary evidence, worked…
MITAuto-check passed
Install Icdt Experiments
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-experiments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-experiments --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-experiments .claude/skills/icdt-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-experiments into .claude/skills/icdt-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-experiments", 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-experimentsType 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-experiments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-experiments --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-experiments .agents/skills/icdt-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-experiments into .agents/skills/icdt-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-experiments", 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-experiments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-experiments --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-experiments .cursor/skills/icdt-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-experiments into .cursor/skills/icdt-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-experiments", 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-experiments--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-experiments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-experiments --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-experiments .gemini/skills/icdt-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-experiments into .gemini/skills/icdt-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-experiments", 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-experimentsInstalls 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-experiments -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-experiments .github/skills/icdt-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-experiments into .github/skills/icdt-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-experiments", 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-experiments -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-experiments --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-experiments .opencode/skills/icdt-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-experiments into .opencode/skills/icdt-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-experiments", 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-experiments- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 469 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding what counts as evidence for an ICDT (International Conference on Database Theory) result — matching-bound complexity analysis as the primary evidence, worked…
- Worked examples and counterexamples that establish separations
- SKILL.md covers Match the evidence to the…, Making the theoretical…, If your paper does include an… and Honesty and scope, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Only for papers with an algorithmic contribution
What it does
Icdt Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what counts as evidence for an ICDT (International Conference on Database Theory) result — matching-bound complexity analysis as the primary evidence, worked examples and counterexamples that establish separations, and, only for papers with an algorithmic contribution, a proportional and honestly-scoped experimental evaluation that does not pretend to be the contribution.
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.
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
- Worked examples and counterexamples that establish separations
- Only for papers with an algorithmic contribution
- A proportional and honestly-scoped experimental evaluation that does not pretend to be the contribution
Example prompts
- “/icdt-experiments”
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 Experiments loads about 1.1k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 469 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). 469 words, ~1,143 tokens.
Download SKILL.mdSave it as
.claude/skills/icdt-experiments/SKILL.md (or your agent's skills folder).- name
- icdt-experiments
- description
- Use when deciding what counts as evidence for an ICDT (International Conference on Database Theory) result — matching-bound complexity analysis as the primary evidence, worked examples and counterexamples that establish separations, and, only for papers with an algorithmic contribution, a proportional and honestly-scoped experimental evaluation that does not pretend to be the contribution.
ICDT Experiments
At ICDT the primary "evidence" is a proof, not a benchmark. This skill is about matching your form of evidence to your claim: most ICDT papers are purely theoretical and need no experiments at all, while a minority with a genuine algorithmic contribution benefit from a small, honest evaluation. Bolting a systems-style experiment section onto a theorem paper does not raise its standing — a loose bound or an unproved lemma will still sink it.
Match the evidence to the claim shape
| Claim shape | Primary evidence | Experiments? |
|---|---|---|
| Complexity of evaluating a query class | Matching upper and lower bounds, with proofs | No — the bound is the result |
| Expressiveness / separation | A construction or an Ehrenfeucht-Fraisse game establishing the separation | No — a witness, not a benchmark |
| Decidability / undecidability of a problem | An algorithm + termination proof, or a reduction from an undecidable problem | No |
| A new algorithm with a claimed practical complexity | The complexity proof plus an optional experiment showing the constants are reasonable | Optional, proportional |
| A dichotomy | Proof that each side holds and the boundary is exactly as stated | No |
The default answer is "the theorem is the evidence." Reach for experiments only when your paper claims something about practice that the asymptotic bound alone does not settle.
Making the theoretical evidence airtight
- Tightness: if you claim a bound is tight, prove both directions and label which is the upper and which the lower. A one-sided bound presented as a complete answer is the classic "revise."
- The right complexity measure: be explicit about data vs combined vs query complexity, and prove the bound in the measure you claim it for.
- Worked examples and counterexamples: a small concrete database and query that illustrates the construction, or a counterexample that rules out a tempting stronger statement, is high-value evidence a referee can check by hand — include it in the body.
- Corner cases: state what happens at the boundaries of your class (empty instances, cyclic vs acyclic, bounded arity) rather than leaving the referee to wonder whether a case breaks the proof.
Show full SKILL.md (132 more words)Show less
If your paper does include an experiment
Some ICDT papers contribute an algorithm whose worst-case bound understates or overstates its behavior on realistic inputs. If you evaluate it, do so with the rigor the theory earns:
[Purpose] state exactly what the experiment tests that the proof does not (e.g., typical-case
runtime, the size of the hidden constant, scaling on real query workloads)
[Subjects] real or standard benchmark data/queries, described precisely; no cherry-picked inputs
[Baseline] a fair comparison (a prior algorithm, a naive method) implemented honestly
[Reporting] enough runs, hardware stated, and results that support only what you claim
[Scope] the experiment supplements the theorem; it never substitutes for a missing proofKeep it proportional: an ICDT experiment is a paragraph-to-a-page confirmation, not a systems-paper
evaluation. If the experiment is the contribution, the paper likely belongs at EDBT/SIGMOD, not
ICDT (see icdt-topic-selection).
Honesty and scope
- Do not report an experiment whose setup you would not want a referee to reproduce; ICDT referees are skeptical of evaluations that appear to decorate a theorem.
- Do not claim practical impact the experiment does not show — "faster on our three instances" is not "faster in practice."
- State the model assumptions your algorithm relies on and whether the experiment respects them.
Output format
[Claim -> evidence] <each claim -> proof (bounds/construction) or experiment>
[Tightness] bounds matched and labeled? yes/no/na
[Complexity measure] data / combined / query, proven in the claimed measure? yes/no
[Experiment] none (theory-complete) / proportional supplement / over-scoped (reroute?)
[Fix queue] <ordered: close bound gaps first, then examples, then any experiment>© 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-experiments of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icdt Experiments 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 Experiments this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | 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 | |
| Finding ExperimentsPostHog/posthog | 40k | — | ~783 | Automated safety check: Pass | Custom licence | |
| Internal Communications Writeranthropics/skills | 180k | 38 repos | ~378 | Automated safety check: Pass | Apache-2.0 | |
| ExperimentsArize-ai/phoenix | 12k | — | ~1.8k | Automated safety check: Pass | Custom licence |
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.
- Official
Finding Experiments
PostHog/posthog
Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing experiment-list (not feature-flag tools), with disambiguation when multiple experiments match.
- 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…
Experiments
Arize-ai/phoenix
Run, read, and compare dataset-backed experiments to find evidence that a prompt or pipeline is improving.
Internal Comms Anthropic
sickn33/agentic-awesome-skills
Compatibility alias for internal-comms: draft status updates, newsletters and FAQs from approved sources.
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 Experiments
What does Icdt Experiments do?
A skill your agent uses when deciding what counts as evidence for an ICDT (International Conference on Database Theory) result — matching-bound complexity analysis as the primary evidence, worked…. Icdt Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding what counts as evidence for an ICDT (International Conference on Database Theory) result — matching-bound complexity analysis as the primary evidence, worked examples and counterexamples that establish separations, and, only for papers with an algorithmic contribution, a proportional and honestly-scoped experimental evaluation that does not pretend to be the contribution.
When should I use Icdt Experiments?
Icdt Experiments fits situations like: worked examples and counterexamples that establish separations; only for papers with an algorithmic contribution; A proportional and honestly-scoped experimental evaluation that does not pretend to be the contribution.
How do I install Icdt Experiments in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-experiments -a claude-code`. Or copy the skill folder (ICDT-Skills/skills/icdt-experiments in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icdt-experiments in your project. Claude Code loads it when a task matches its description.
How do I install Icdt Experiments in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-experiments -a codex`. Or copy the skill folder (ICDT-Skills/skills/icdt-experiments in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icdt-experiments in your project. Codex loads it when a task matches its description.
Can I use Icdt Experiments 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-experiments -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-experiments, .gemini/skills/icdt-experiments, .github/skills/icdt-experiments and .opencode/skills/icdt-experiments in your project.
What does Icdt Experiments need to run?
SKILL.md names no scripts, command-line tools or credentials: Icdt Experiments is instructions for the agent only.
Does Icdt Experiments 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 Experiments 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 Experiments use?
Icdt Experiments 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 Experiments use?
About 1.1k tokens (SKILL.md is roughly 4.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 Experiments?
Skills that share tags, products or a category with Icdt Experiments: Internal Comms (alirezarezvani/claude-skills, 28k stars), Internal Communication (sickn33/agentic-awesome-skills, 47k stars), Finding Experiments (PostHog/posthog, 40k 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 Experiments?
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.