Apple Container
sickn33/agentic-awesome-skills
Build, run, and manage OCI/Linux containers as lightweight per-container VMs on Apple-silicon macOS using Apple's open-source container CLI, no Docker daemon required.
A skill your agent uses 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…
MITAuto-check passed
Install Sensys Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-review-process .claude/skills/sensys-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 "sensys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-review-process into .claude/skills/sensys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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/SenSys-Skills/skills/sensys-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 sensys-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-review-process .agents/skills/sensys-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 "sensys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-review-process into .agents/skills/sensys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-review-process .cursor/skills/sensys-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 "sensys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-review-process into .cursor/skills/sensys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 SenSys-Skills/skills/sensys-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 sensys-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-review-process .gemini/skills/sensys-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 "sensys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-review-process into .gemini/skills/sensys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-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 sensys-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/SenSys-Skills/skills/sensys-review-process .github/skills/sensys-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 "sensys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-review-process into .github/skills/sensys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-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 sensys-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/SenSys-Skills/skills/sensys-review-process .opencode/skills/sensys-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 "sensys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-review-process into .opencode/skills/sensys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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
sensys-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 432 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Interpreting SenSyss two-deadline
- SKILL.md covers The outcome space, What SenSys reviewers weigh, Classifying a notification… and Confidentiality and conduct, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Self-contained review model — what a first-deadline outcome means
What it does
Sensys Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
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
- Interpreting SenSyss 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
Example prompts
- “/sensys-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
Sensys Review Process loads about 1.1k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 432 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). 432 words, ~1,119 tokens.
Download SKILL.mdSave it as
.claude/skills/sensys-review-process/SKILL.md (or your agent's skills folder).- name
- sensys-review-process
- description
- 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 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 |
| Resubmit with revision (next deadline) | The path the two-deadline model offers, not an automatic invitation | Treat the reviews as the required-changes list; see sensys-author-response |
Note that whether a given cycle also offers an explicit major-revision channel at notification (distinct from the first→second deadline resubmission) is 待核实 — read the current CFP; do not assume a rebuttal or revision stage that the edition does not run.
What SenSys reviewers weigh
SenSys reviewers are systems people who have built and deployed. They read for:
- Is it built and measured? Simulation-only or single-run results draw immediate skepticism.
- Is the energy real? Adjectives ("low-power") where a measurement belongs are flagged.
- Is the ground truth honest? Accuracy against an unstated or uncalibrated reference is a standard objection.
- Is the baseline fair? Cross-hardware or untuned comparisons undercut the headline.
- Does the design understand its space? Rejected alternatives and named limitations signal competence; their absence signals under-evaluation.
Knowing this lets you predict the review themes before they arrive and pre-empt them in the paper
(sensys-experiments, sensys-writing-style).
Show full SKILL.md (149 more words)Show less
Classifying a notification before you respond
Read every review and sort each point:
[Blocking] a claim the reviewer does not believe without new measurement
[Fixable] a gap addressable by a bench run or a clearer figure
[Framing] a misread you can prevent with rewriting, no new data
[Wishlist] a nice-to-have outside the paper's scope
Then decide:
Accept → move to camera-ready + artifacts
Resubmit → is the blocking set closable by the next deadline given testbed time?
Route away → if the blocking set needs a redesign, a different venue may be fasterThe decision to resubmit is a calendar-and-testbed decision as much as a scientific one: a
blocking reviewer objection that requires a new energy-harvesting deployment cannot be answered
in two weeks. sensys-workflow holds the backward schedule.
Confidentiality and conduct
Reviews are confidential; do not circulate them or identify reviewers, and do not attempt to de-anonymize. Concerns about a review's fairness or a conflict go to the chairs through the process, not into the response text. The exact conduct and appeal wording for the cycle is 待核实 — read the current pages.
Reviewer continuity across deadlines
Because a resubmission returns to the venue with its prior reviews attached, assume some
continuity of reviewer context between deadlines: the response-to-reviewers is read against
what was promised. This makes the response a contract (see sensys-author-response), not a
debate — every promised change must appear in the revised paper.
Output format
[Outcome] accept / reject / resubmit-with-revision — as the notification states
[Blocking] the points that must be answered with new measurement, listed
[Feasible] can the blocking set close by the next deadline given testbed time? Y/N
[Path] resubmit here / route elsewhere / proceed to camera-ready
[Open] any process ambiguity (major-revision channel? appeal?) marked 待核实© 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 SenSys-Skills/skills/sensys-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sensys 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 |
|---|---|---|---|---|---|---|
| Sensys Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Apple Containersickn33/agentic-awesome-skills | 47k | 1 repos | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Deadlinesanthropics/claude-for-legal | 9.6k | 3 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Container Security Hardeningsickn33/agentic-awesome-skills | 47k | 1 repos | ~1k | Automated safety check: Notes | MIT | |
| Container Queriesthedaviddias/Front-End-Checklist | 74k | — | ~526 | Automated safety check: Pass | MIT | |
| CSS Containmentthedaviddias/Front-End-Checklist | 74k | — | ~512 | Automated safety check: Pass | MIT |
Similar skills
- Official
Deadlines
anthropics/claude-for-legal
Track case deadlines — add, cross-case rollup report, update, complete, close.
Container Security Hardening
sickn33/agentic-awesome-skills
Harden Docker/container images and runtime deployments with secure base images, non-root users, CVE scanning, SBOM/signing, seccomp/AppArmor, and Kubernetes pod security controls.
Container Queries
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use container queries for component-level responsiveness.
CSS Containment
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use CSS containment to limit repaint scope.
Detecting Container Escape Attempts
mukul975/Anthropic-Cybersecurity-Skills
Detects container escape at runtime across tooling - namespace manipulation, capability abuse, kernel exploits, sensitive host mounts, and anomalous syscalls - and explains which signals matter…
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 Sensys Review Process
What does Sensys Review Process do?
A skill your agent uses 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…. Sensys Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Sensys Review Process?
Sensys Review Process fits situations like: interpreting SenSyss 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.
How do I install Sensys Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-review-process -a claude-code`. Or copy the skill folder (SenSys-Skills/skills/sensys-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sensys-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Sensys Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-review-process -a codex`. Or copy the skill folder (SenSys-Skills/skills/sensys-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sensys-review-process in your project. Codex loads it when a task matches its description.
Can I use Sensys 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 sensys-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/sensys-review-process, .gemini/skills/sensys-review-process, .github/skills/sensys-review-process and .opencode/skills/sensys-review-process in your project.
What does Sensys Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Sensys Review Process is instructions for the agent only.
Does Sensys 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 Sensys 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 Sensys Review Process use?
Sensys 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 Sensys Review Process 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 Sensys Review Process?
Skills that share tags, products or a category with Sensys Review Process: Apple Container (sickn33/agentic-awesome-skills, 47k stars), Deadlines (anthropics/claude-for-legal, 9.6k stars), Container Security Hardening (sickn33/agentic-awesome-skills, 47k stars) and Container Queries (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sensys 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.