Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when reasoning about how an IPSN-lineage submission is evaluated, covering double-blind review, the per-track (IP / SPOTS) program committees, the rebuttal, Best Paper and…
Install Ipsn Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-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/IPSN-Skills/skills/ipsn-review-process .claude/skills/ipsn-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 "ipsn-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-review-process into .claude/skills/ipsn-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-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/IPSN-Skills/skills/ipsn-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 ipsn-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-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/IPSN-Skills/skills/ipsn-review-process .agents/skills/ipsn-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 "ipsn-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-review-process into .agents/skills/ipsn-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-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 ipsn-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-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/IPSN-Skills/skills/ipsn-review-process .cursor/skills/ipsn-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 "ipsn-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-review-process into .cursor/skills/ipsn-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-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 IPSN-Skills/skills/ipsn-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 ipsn-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ipsn-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/IPSN-Skills/skills/ipsn-review-process .gemini/skills/ipsn-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 "ipsn-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-review-process into .gemini/skills/ipsn-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-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 ipsn-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 ipsn-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/IPSN-Skills/skills/ipsn-review-process .github/skills/ipsn-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 "ipsn-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-review-process into .github/skills/ipsn-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-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 ipsn-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 ipsn-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/IPSN-Skills/skills/ipsn-review-process .opencode/skills/ipsn-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 "ipsn-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IPSN-Skills/skills/ipsn-review-process into .opencode/skills/ipsn-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ipsn-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
ipsn-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 652 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 IPSN-lineage submission is evaluated, covering double-blind review, the per-track (IP / SPOTS) program committees, the rebuttal, Best Paper and…
- Reasoning about how an IPSN-lineage submission is evaluated
- SKILL.md covers Process model, What each track's reviewers…, Reading a decision against the… and How IPSN differs from its…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering double-blind review
What it does
Ipsn Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an IPSN-lineage submission is evaluated, covering double-blind review, the per-track (IP / SPOTS) program committees, the rebuttal, Best Paper and Best Research Artifact judging, and how IPSN's process differs from SenSys's revision model, OpenReview venues, and CPS-IoT Week neighbors.
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.
It sits in Research & Science. 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 IPSN-lineage submission is evaluated
- Covering double-blind review
- The per-track (IP / SPOTS) program committees
- Best Paper and Best Research Artifact judging
Example prompts
- “s process differs from SenSys”
- “/ipsn-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
Ipsn Review Process loads about 1.5k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 652 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). 652 words, ~1,519 tokens.
Download SKILL.mdSave it as
.claude/skills/ipsn-review-process/SKILL.md (or your agent's skills folder).- name
- ipsn-review-process
- description
- Use when reasoning about how an IPSN-lineage submission is evaluated, covering double-blind review, the per-track (IP / SPOTS) program committees, the rebuttal, Best Paper and Best Research Artifact judging, and how IPSN's process differs from SenSys's revision model, OpenReview venues, and CPS-IoT Week neighbors.
IPSN Review Process
Model the pipeline before interpreting any single review. IPSN's process is double-blind, per-track, and conference-style (not journal-style): a submission is read by a program committee matched to its track — IP or SPOTS — and returns an accept/reject decision, usually with a rebuttal opportunity. Because IPSN merged into SenSys, confirm the successor's exact mechanics on the current call; the structure below is the IPSN-lineage model and what to expect.
Process model
- Submission and review run on HotCRP with double-blind anonymity: author identities are hidden from reviewers and reviewer identities from authors.
- Papers are matched to reviewers by track. An IP-track paper is read by method reviewers
(estimation, signal processing, learning, localization); a SPOTS-track paper by
platform/systems reviewers (hardware, embedded software, tools, deployment). This is why the track
choice in
ipsn-submissionmatters so much. - Reviewers weigh: the soundness of the information-processing method or platform design; whether the evidence is real (real sensors, ground truth, measured energy/latency, honest deployment numbers); novelty against the sensing literature; and reproducibility / artifact support.
- A rebuttal typically lets authors correct factual misreadings before the decision (verify the window and format on the current call).
- Accepted papers appeared in both ACM DL and IEEE Xplore; the successor publishes regular papers in the ACM proceedings and demos/posters in the IEEE proceedings.
What each track's reviewers check first
| Track | Reviewer's first question | Common reject trigger |
|---|---|---|
| IP | Is the estimator/inference sound, and is the baseline fair? | Simulation-only, or a proxy metric standing in for the real sensing outcome |
| SPOTS | Is the platform/tool reusable, and are the design trade-offs measured? | A one-off build with a datasheet but no measured power/robustness story |
| Either (deployment) | Are the real-world hardships reported honestly? | Yield, synchronization, and energy numbers missing or idealized |
Reading a decision against the criteria
| Signal in the reviews | What it means | Author move |
|---|---|---|
| "Only simulated / no real hardware" | Evidence-realism doubt (fatal at IPSN) | If possible add a real-sensor result in rebuttal; otherwise reroute |
| "Baseline is not a real alternative / untuned" | Soundness doubt | Add or justify a fair baseline; report the comparison |
| "Deployment numbers look idealized" | Honesty/realism doubt | Report yield, sync error, energy as measured, with limits |
| "Artifact would strengthen this" | Reproducibility gap | Commit to (and anonymize) a firmware+dataset artifact |
| "Wrong track / out of scope" | Track or venue mismatch | Hard to fix in rebuttal; a ipsn-topic-selection lesson for next time |
Show full SKILL.md (265 more words)Show less
How IPSN differs from its neighbors and successor
- vs. SenSys (pre-merger): SenSys is the sibling embedded-networked-sensing flagship; IPSN's distinctive move was the IP/SPOTS split and its information-processing/estimation flavor. Post-merger the two communities share one venue — but an IP-track style paper is still judged on its estimation/inference soundness.
- vs. OpenReview ML venues: IPSN is not open-review, not score-thread public, and not leaderboard-driven. Offline accuracy on a clean dataset does not carry a paper here; on-device or in-field evidence does.
- vs. CPS-IoT Week neighbors (RTAS/HSCC/ICCPS): those reviewers want timing guarantees, control theory, or hybrid-systems verification. An IPSN paper is judged on sensing/information-processing soundness and real measurement, not worst-case schedulability.
Where author leverage actually exists
[Before submission] track choice + topic tags -> reviewer pool (largest lever)
[Initial reviews] factual corrections, a real-hardware number a reviewer said was missing
[Rebuttal] narrow, evidence-backed answers to soundness/realism doubts
[After reject] no journal-style guaranteed revision round; reroute or resubmit next cycleA rebuttal moves borderline papers when it corrects a misread table or supplies a measured number a reviewer flagged; it does not move papers that argue taste or promise experiments not yet run.
Best Paper and Best Research Artifact judging
IPSN gave a Best Paper Award and a Best Research Artifact Award. The artifact award is a
distinct incentive: a firmware+dataset package that an evaluator can actually run and reuse is judged
on more than the paper's claims. Target it deliberately (ipsn-artifact-evaluation) — verify whether
it persists under the successor (待核实).
Misreadings to avoid
- Expecting a journal-style Major Revision — IPSN is conference-style accept/reject with a rebuttal, not a guaranteed revise-and-resubmit round (unlike a journal or a Major-Revision venue).
- Treating the rebuttal as a debate — the PC discussion decides; the rebuttal is evidence for an advocate, not a closing argument.
- Assuming the successor keeps IPSN's exact mechanics — the merged SenSys may differ; confirm.
Output format
[Process stage] pre-submission / awaiting reviews / rebuttal / decision / accepted
[Track] IP / SPOTS (or successor category)
[Criterion map] each review point -> soundness | evidence-realism | novelty | reproducibility | track-fit
[Leverage plan] the next-stage action that can actually change the outcome
[Forbidden moves] identity leak / unrun experiments promised as done / arguing taste© 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 IPSN-Skills/skills/ipsn-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ipsn 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 |
|---|---|---|---|---|---|---|
| Ipsn Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
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 Ipsn Review Process
What does Ipsn Review Process do?
A skill your agent uses when reasoning about how an IPSN-lineage submission is evaluated, covering double-blind review, the per-track (IP / SPOTS) program committees, the rebuttal, Best Paper and…. Ipsn Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an IPSN-lineage submission is evaluated, covering double-blind review, the per-track (IP / SPOTS) program committees, the rebuttal, Best Paper and Best Research Artifact judging, and how IPSN's process differs from SenSys's revision model, OpenReview venues, and CPS-IoT Week neighbors.
When should I use Ipsn Review Process?
Ipsn Review Process fits situations like: reasoning about how an IPSN-lineage submission is evaluated; covering double-blind review; the per-track (IP / SPOTS) program committees; best Paper and Best Research Artifact judging.
How do I install Ipsn Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-review-process -a claude-code`. Or copy the skill folder (IPSN-Skills/skills/ipsn-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ipsn-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Ipsn Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-review-process -a codex`. Or copy the skill folder (IPSN-Skills/skills/ipsn-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ipsn-review-process in your project. Codex loads it when a task matches its description.
Can I use Ipsn 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 ipsn-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/ipsn-review-process, .gemini/skills/ipsn-review-process, .github/skills/ipsn-review-process and .opencode/skills/ipsn-review-process in your project.
What does Ipsn Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Ipsn Review Process is instructions for the agent only.
Does Ipsn 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 Ipsn 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 Ipsn Review Process use?
Ipsn 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 Ipsn Review Process use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Ipsn Review Process?
Skills that share tags, products or a category with Ipsn Review Process: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ipsn 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.