Individual skill
sensys-review-process
Use when interpreting SenSys's two-deadline, self-contained review model — what a first-deadline outcome means, that a reject may return at the second deadline only with a substantive revision and Response to Reviewers, how systems reviewers weigh energy and deployment evidence, and how to classify a notification before drafting a response.
SenSys-Skills/skills/sensys-review-process/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- operations Derived category
- devops Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,509 bytes
Read excerpt
# SenSys Review Process
SenSys does not run a single annual verdict. It runs **two submission deadlines per cycle, each
a self-contained review round**, and the connective tissue between them is a **resubmission
rule**: a paper rejected at one deadline may re-enter at the next **only with a substantive
revision and a "Response to Reviewers"** that maps each concern to a specific change. Reading
your notification correctly means knowing which move the process is offering you.
## The outcome space
| Outcome | What it means | Your move |
|---|---|---|
| **Accept** | The paper is in the edition the deadline feeds | `sensys-artifact-evaluation` + `sensys-camera-ready` |
| **Reject** | Not accepted at this deadline | Decide whether to **resubmit with revision** at the next deadline, or route elsewhere |