Crawl4AI Web Scraping
smallnest/goclaw
Scrapes sites, handles JavaScript-heavy pages and extracts structured data with Crawl4AI, through its crwl CLI or Python SDK, including schema-based extraction without an LLM.
A skill your agent uses when designing or auditing IEEE ICDE experiments for a data-engineering paper: workload realism, tuned baselines, scale curves over single points, throughput and tail-latency…
Install Icde Experiments
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-experiments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-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/ICDE-Skills/skills/icde-experiments .claude/skills/icde-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 "icde-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-experiments into .claude/skills/icde-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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/ICDE-Skills/skills/icde-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 icde-experiments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-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/ICDE-Skills/skills/icde-experiments .agents/skills/icde-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 "icde-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-experiments into .agents/skills/icde-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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 icde-experiments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-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/ICDE-Skills/skills/icde-experiments .cursor/skills/icde-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 "icde-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-experiments into .cursor/skills/icde-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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 ICDE-Skills/skills/icde-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 icde-experiments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-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/ICDE-Skills/skills/icde-experiments .gemini/skills/icde-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 "icde-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-experiments into .gemini/skills/icde-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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 icde-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 icde-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/ICDE-Skills/skills/icde-experiments .github/skills/icde-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 "icde-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-experiments into .github/skills/icde-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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 icde-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 icde-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/ICDE-Skills/skills/icde-experiments .opencode/skills/icde-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 "icde-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-experiments into .opencode/skills/icde-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-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
icde-experiments- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 489 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when designing or auditing IEEE ICDE experiments for a data-engineering paper: workload realism, tuned baselines, scale curves over single points, throughput and tail-latency…
- Auditing IEEE ICDE experiments for a data-engineering paper: workload realism
- SKILL.md covers Experiment audit, What experiments are for at…, Evidence-burden table and Vignette: evaluating a…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tuned baselines
What it does
Icde Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing IEEE ICDE experiments for a data-engineering paper: workload realism, tuned baselines, scale curves over single points, throughput and tail-latency with declared variance, mechanism-isolating ablations, cost/loss disclosure, and hardware reporting that satisfies a builder-heavy committee.
Its SKILL.md is about 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 Data & Analytics, covering Data pipelines and ETL. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Auditing IEEE ICDE experiments for a data-engineering paper: workload realism
- Tuned baselines
- Scale curves over single points
- Throughput and tail-latency with declared variance
Example prompts
- “/icde-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
Icde Experiments loads about 1k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 489 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). 489 words, ~1,044 tokens.
Download SKILL.mdSave it as
.claude/skills/icde-experiments/SKILL.md (or your agent's skills folder).- name
- icde-experiments
- description
- Use when designing or auditing IEEE ICDE experiments for a data-engineering paper: workload realism, tuned baselines, scale curves over single points, throughput and tail-latency with declared variance, mechanism-isolating ablations, cost/loss disclosure, and hardware reporting that satisfies a builder-heavy committee.
ICDE Experiments
Use this before submission when the evaluation is not yet locked. At ICDE, the experiments are where a systems paper is won or lost; a builder-heavy committee reads them adversarially.
Experiment audit
- Map each performance claim to a figure, table, or measured crossover — no orphan claims.
- Run tuned baselines, not straw men. Document the tuning budget you gave each competitor; an untuned baseline is the single most common ICDE reject trigger.
- Prefer curves over points: show behavior across scale factors, data sizes, or contention levels, not one operating point where you happen to win.
- Report throughput and tail latency with variance — multiple runs, and captions that say whether bars are standard deviations, confidence intervals, or percentiles. A p99 that hides behind a median is a caught omission.
- Add ablations that isolate the mechanism: turn off the one idea and show the gain disappears, so the improvement cannot be attributed to unrelated engineering.
- Disclose the cost of every gain: memory, write amplification, CPU, or read-latency penalty. A loss map is a credibility signal, not a weakness.
- Report hardware, OS, storage device, software versions, dataset construction, and workload generators with seeds so the numbers are reconstructable.
What experiments are for at this venue
- ICDE experiments exist to establish and isolate a systems effect, not to top a leaderboard. One clean ablation proving the mechanism causes the gain outweighs five more datasets where it merely correlates.
- The strongest design pairs a synthetic generator you can sweep (to find the crossover and stress the mechanism) with a real workload (to show practical relevance). State where the synthetic regime matches the real one and where it does not.
- Reviewers check whether the operating regime — data size, concurrency, hardware — is one where the claimed effect should even appear; a cache-resident benchmark cannot support a claim about I/O-bound behavior.
Show full SKILL.md (185 more words)Show less
Evidence-burden table
| Claim | Matching evidence | Reject pattern avoided |
|---|---|---|
| "The problem exists" | Baseline stalls/degrades on the target workload | "Solving a problem nobody has" |
| "Our mechanism causes the gain" | Ablation toggling the one idea | "Gain from unrelated engineering" |
| "It scales" | Curve across scale factors, not a single point | "Single-point win, unknown scaling" |
| "The cost is acceptable" | Disclosed memory/CPU/latency cost table | "Free-lunch claim, hidden trade-off" |
| "It generalizes" | A real workload beside the synthetic sweep | "Only synthetic, no real relevance" |
Vignette: evaluating a write-optimized index
A paper claims higher ingestion by deferring ordering. The matching plan: sweep the append-to-scan ratio synthetically to locate the crossover, run a real telemetry trace at the claimed rate to show the baseline stalls where the new index does not, ablate the deferral to prove it is the cause, and report the read-latency tail and memory cost so the trade is legible — every panel tied to a claim in the text.
Reporting floor
- Multiple runs and reported variance for every performance figure; name the metric precisely (throughput, p50/p99 latency, amplification).
- Report the hardware and the compute actually consumed, not vague feasibility language.
Output format
[Experiment readiness] strong / adequate / weak
[Claim -> evidence map] <claim: figure/table/crossover>
[Baseline fairness] <tuning budget disclosed? untuned competitors?>
[Missing evidence] <scale curve / variance / ablation / cost disclosure>
[Reproducibility gaps] <hardware / versions / generators / seeds>
[Decision-critical next run] <one 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 ICDE-Skills/skills/icde-experiments of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icde 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 |
|---|---|---|---|---|---|---|
| Icde Experiments this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Crawl4AI Web Scrapingsmallnest/goclaw | 598 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Glue 09 10 Migrationaws-samples/aws-glue-samples | 1.5k | — | ~2.4k | Automated safety check: Pass | MIT-0 | |
| Migrate Glue Devendpoint To Interactive Sessionsaws-samples/aws-glue-samples | 1.5k | — | ~3.6k | Automated safety check: Pass | MIT-0 | |
| Dbt Databricks PR Readydatabricks/dbt-databricks | 380 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Mz Dbt ReleaseMaterializeInc/materialize | 6.4k | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Glue 09 10 Migration
aws-samples/aws-glue-samples
Upgrade an AWS Glue ETL job from Glue version 0.9 or 1.0 to Glue 4.0.
- Official
Migrate Glue Devendpoint To Interactive Sessions
aws-samples/aws-glue-samples
Migrate a legacy AWS Glue development endpoint to a Glue interactive session, following the official AWS migration checklist.
- Official
Dbt Databricks PR Ready
databricks/dbt-databricks
A skill your agent uses for an open dbt-databricks pull request, including your own PR or a fork PR, to assess merge readiness and optionally repair selected gaps on the PR head branch.
Mz Dbt Release
MaterializeInc/materialize
Cut a dbt-materialize PyPI release: bump the version in version.py and setup.py, date the Unreleased CHANGELOG entry, and open the release PR with a Ship: <url body.
Erd Studio Setup
liam-machine/erd-studio
Friendly, step-by-step setup for ERD Studio in an existing dbt project, for people who may be new to dbt or data modelling.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Icde Experiments
What does Icde Experiments do?
A skill your agent uses when designing or auditing IEEE ICDE experiments for a data-engineering paper: workload realism, tuned baselines, scale curves over single points, throughput and tail-latency…. Icde Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing IEEE ICDE experiments for a data-engineering paper: workload realism, tuned baselines, scale curves over single points, throughput and tail-latency with declared variance, mechanism-isolating ablations, cost/loss disclosure, and hardware reporting that satisfies a builder-heavy committee.
When should I use Icde Experiments?
Icde Experiments fits situations like: auditing IEEE ICDE experiments for a data-engineering paper: workload realism; tuned baselines; scale curves over single points; throughput and tail-latency with declared variance.
How do I install Icde Experiments in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-experiments -a claude-code`. Or copy the skill folder (ICDE-Skills/skills/icde-experiments in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icde-experiments in your project. Claude Code loads it when a task matches its description.
How do I install Icde Experiments in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-experiments -a codex`. Or copy the skill folder (ICDE-Skills/skills/icde-experiments in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icde-experiments in your project. Codex loads it when a task matches its description.
Can I use Icde 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 icde-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/icde-experiments, .gemini/skills/icde-experiments, .github/skills/icde-experiments and .opencode/skills/icde-experiments in your project.
What does Icde Experiments need to run?
SKILL.md names no scripts, command-line tools or credentials: Icde Experiments is instructions for the agent only.
Does Icde 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 Icde 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 Icde Experiments use?
Icde 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 Icde Experiments use?
About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Icde Experiments?
Skills that share tags, products or a category with Icde Experiments: Crawl4AI Web Scraping (smallnest/goclaw, 598 stars), Glue 09 10 Migration (aws-samples/aws-glue-samples, 1.5k stars), Migrate Glue Devendpoint To Interactive Sessions (aws-samples/aws-glue-samples, 1.5k stars) and Dbt Databricks PR Ready (databricks/dbt-databricks, 380 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icde 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.