Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when positioning an ICDT (International Conference on Database Theory) paper against the database-theory literature — covering the ICDT/PODS lineage, finite model theory and…
Install Icdt Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-related-work --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-related-work .claude/skills/icdt-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-related-work into .claude/skills/icdt-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-related-work", 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-related-workType 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-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-related-work --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-related-work .agents/skills/icdt-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-related-work into .agents/skills/icdt-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-related-work", 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-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-related-work --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-related-work .cursor/skills/icdt-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-related-work into .cursor/skills/icdt-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-related-work", 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-related-work--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-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icdt-related-work --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-related-work .gemini/skills/icdt-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-related-work into .gemini/skills/icdt-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-related-work", 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-related-workInstalls 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-related-work -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-related-work .github/skills/icdt-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-related-work into .github/skills/icdt-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-related-work", 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-related-work -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-related-work --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-related-work .opencode/skills/icdt-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDT-Skills/skills/icdt-related-work into .opencode/skills/icdt-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icdt-related-work", 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-related-work- 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 positioning an ICDT (International Conference on Database Theory) paper against the database-theory literature — covering the ICDT/PODS lineage, finite model theory and…
- Finite model theory and complexity
- SKILL.md covers Cover the database-theory lanes, Delta-first positioning, Honesty about overlapping and… and Anonymous self-citation (since…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Delta-first positioning against the nearest prior theorem
What it does
Icdt Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ICDT (International Conference on Database Theory) paper against the database-theory literature — covering the ICDT/PODS lineage, finite model theory and complexity, delta-first positioning against the nearest prior theorem, honest treatment of overlapping bounds, and keeping self-citations anonymous under the since-2024 rule.
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 Research & Science, covering Literature review, Positioning and messaging and Citation management. 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
- Finite model theory and complexity
- Delta-first positioning against the nearest prior theorem
- Honest treatment of overlapping bounds
- Keeping self-citations anonymous under the since-2024 rule
Example prompts
- “/icdt-related-work”
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 Related Work loads about 1.1k tokens when it runs. Until then it costs about 93 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,128 tokens.
Download SKILL.mdSave it as
.claude/skills/icdt-related-work/SKILL.md (or your agent's skills folder).- name
- icdt-related-work
- description
- Use when positioning an ICDT (International Conference on Database Theory) paper against the database-theory literature — covering the ICDT/PODS lineage, finite model theory and complexity, delta-first positioning against the nearest prior theorem, honest treatment of overlapping bounds, and keeping self-citations anonymous under the since-2024 rule.
ICDT Related Work
Position the paper against the exact prior theorems it advances. At ICDT the related-work section is where a referee checks whether your result is genuinely new or a re-proof of something in the ICDT/PODS canon, so vague "much work has been done" prose is a liability. Every neighboring result should be named, its bound stated, and your delta made precise.
Cover the database-theory lanes
A database-theory paper usually sits in one or more of these literatures; name the relevant ones and the closest results in each:
- Query languages and expressiveness — CQs/UCQs, Datalog and its fragments, FO, regular path queries, and the separations between them.
- Complexity of query evaluation — combined/data/query complexity, dichotomies, parameterized and fine-grained bounds.
- Finite model theory — locality, games, zero-one laws, descriptive complexity as it applies to databases.
- Constraints and reasoning — TGDs/EGDs, the chase, decidability of implication and query answering under constraints.
- Consistent query answering and inconsistency — repairs, certain answers, complexity of CQA.
- Provenance and semiring semantics — annotated relations, provenance polynomials.
- Data integration and exchange — schema mappings, certain answers, the theory behind ETL.
Delta-first positioning
State your advance against the nearest theorem, not against a field:
"For [class], [Author, ICDT/PODS year] established a [complexity] upper bound but left the lower bound open; we close it, showing the problem is [class]-complete, and extend the result to [broader class]."
- Name the closest prior bound and say precisely how yours differs — tighter, broader, a matching lower bound, a new model, a removed assumption.
- If a prior result subsumes a special case of yours, say so and explain what your generality buys.
- If two lines of work appear to conflict with yours (e.g., a claimed hardness vs your tractability), reconcile them — usually a difference in the model or complexity measure — rather than ignoring one.
Show full SKILL.md (227 more words)Show less
Honesty about overlapping and concurrent results
- Concurrent work at the other flagship: if a PODS or arXiv result overlaps, cite it and delineate the independent contribution; the database-theory community is small and referees know the concurrent papers.
- Journal versions: distinguish a conference result from its extended journal version when both exist; attribute the bound to the right one.
- Do not inflate novelty by omitting the nearest neighbor — a referee who knows the omitted paper reads the omission as either ignorance or evasion.
Anonymous self-citation (since 2024)
ICDT regular submissions are anonymous, so your own prior theorems need third-person handling:
- Write "Building on the chase-based construction of [17]…", never "our earlier ICDT paper [17]."
- Do not let a self-citation pattern (citing one author cluster heavily, in the first person) de-anonymize you.
- If your result critically depends on an unpublished companion paper, cite it anonymously ("[Anon]") per the current call's wording rather than naming yourself — confirm the exact mechanism in the live CfP.
What not to do
- Related work as a bibliography dump — a paragraph of citations with no bound stated proves nothing about your delta.
- Positioning against systems papers only — an ICDT contribution is positioned against theorems; cite EDBT/SIGMOD work for motivation, not for the technical delta.
- Claiming an open problem is open without checking the recent ICDT/PODS programs — it may have been closed last cycle.
Output format
[Lanes covered] <which database-theory literatures the paper touches>
[Nearest prior] <closest theorem, its bound, its venue/year>
[Delta] <tighter | broader | matching lower bound | new model | removed assumption>
[Concurrent] <overlapping PODS/arXiv results cited and delineated? yes/no>
[Anonymity] self-citations third-person and non-identifying? yes/no
[Fix queue] <ordered edits>© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icdt Related Work 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 Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ieee Paper ReaderCloudWave818/ieee-skills | 359 | — | ~591 | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpe Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
Jpe Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when writing or repairing the introduction and related-work framing for a Journal of Political Economy (JPE) manuscript — situating the contribution in the economics…
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
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 Icdt Related Work
What does Icdt Related Work do?
A skill your agent uses when positioning an ICDT (International Conference on Database Theory) paper against the database-theory literature — covering the ICDT/PODS lineage, finite model theory and…. Icdt Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ICDT (International Conference on Database Theory) paper against the database-theory literature — covering the ICDT/PODS lineage, finite model theory and complexity, delta-first positioning against the nearest prior theorem, honest treatment of overlapping bounds, and keeping self-citations anonymous under the since-2024 rule.
When should I use Icdt Related Work?
Icdt Related Work fits situations like: finite model theory and complexity; delta-first positioning against the nearest prior theorem; honest treatment of overlapping bounds; keeping self-citations anonymous under the since-2024 rule.
How do I install Icdt Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-related-work -a claude-code`. Or copy the skill folder (ICDT-Skills/skills/icdt-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icdt-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Icdt Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdt-related-work -a codex`. Or copy the skill folder (ICDT-Skills/skills/icdt-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icdt-related-work in your project. Codex loads it when a task matches its description.
Can I use Icdt Related Work 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-related-work -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-related-work, .gemini/skills/icdt-related-work, .github/skills/icdt-related-work and .opencode/skills/icdt-related-work in your project.
What does Icdt Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Icdt Related Work is instructions for the agent only.
Does Icdt Related Work 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 Related Work 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 Related Work use?
Icdt Related Work 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 Related Work 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 Icdt Related Work?
Skills that share tags, products or a category with Icdt Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpe Literature Positioning (franklee16/academic-research-skills, 223 stars) and Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icdt Related Work?
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.