Deepseek Reason
ruvnet/ruflo
Reasoning-mode completion against DeepSeek's deepseek-reasoner model (R1) via /v1/chat/completions.
A skill your agent uses when reasoning about how an IEEE PerCom research submission is evaluated, covering double-blind review, the three-TPC-member model, the early-rejection stage, the…
MITAuto-check passed
Install Percom Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-review-process .claude/skills/percom-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 "percom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-review-process into .claude/skills/percom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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/PerCom-Skills/skills/percom-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 percom-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-review-process .agents/skills/percom-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 "percom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-review-process into .agents/skills/percom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-review-process .cursor/skills/percom-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 "percom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-review-process into .cursor/skills/percom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 PerCom-Skills/skills/percom-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 percom-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-review-process .gemini/skills/percom-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 "percom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-review-process into .gemini/skills/percom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-review-process .github/skills/percom-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 "percom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-review-process into .github/skills/percom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-review-process .opencode/skills/percom-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 "percom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-review-process into .opencode/skills/percom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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
percom-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 736 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 IEEE PerCom research submission is evaluated, covering double-blind review, the three-TPC-member model, the early-rejection stage, the…
- Reasoning about how an IEEE PerCom research submission is evaluated
- SKILL.md covers Process model, Reading a decision against the…, How PerCom differs from its… and Who reads you, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering double-blind review
What it does
Percom Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an IEEE PerCom research submission is evaluated, covering double-blind review, the three-TPC-member model, the early-rejection stage, the single-round bounded rebuttal gated by a "weak accept," the accept/reject decision, and how PerCom's process differs from ACM UbiComp/IMWUT's journal revise cycle.
Its SKILL.md is about 1.6k 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
- Reasoning about how an IEEE PerCom research submission is evaluated
- Covering double-blind review
- The three-TPC-member model
- The early-rejection stage
Example prompts
- “weak accept,”
- “s process differs from ACM UbiComp/IMWUT”
- “/percom-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
Percom Review Process loads about 1.6k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 736 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). 736 words, ~1,619 tokens.
Download SKILL.mdSave it as
.claude/skills/percom-review-process/SKILL.md (or your agent's skills folder).- name
- percom-review-process
- description
- Use when reasoning about how an IEEE PerCom research submission is evaluated, covering double-blind review, the three-TPC-member model, the early-rejection stage, the single-round bounded rebuttal gated by a "weak accept," the accept/reject decision, and how PerCom's process differs from ACM UbiComp/IMWUT's journal revise cycle.
PerCom Review Process
Model the pipeline before interpreting any single review. PerCom's process is a single annual review round with a bounded rebuttal and an early-rejection gate — not a journal-style revise-and-resubmit, and not a multi-deadline conference. The most consequential mental shift for authors arriving from ACM UbiComp/IMWUT is that there is no revise cycle: the paper is judged on what it submitted, with one bounded chance to answer questions.
Process model
- Submission and review run on HotCRP with double-blind review: authors anonymize in good faith and cite their own prior work in the third person.
- Each reviewed paper is read by three TPC members, who weigh the significance of the pervasive-computing contribution, soundness of the method, quality and honesty of the evaluation (real subjects, cross-subject generalization, appropriate metrics), and clarity.
- Early-rejection gate. After the initial reviews, papers for which no reviewer sees a path to publication are early-rejected and notified (PerCom 2027: ~20 November 2026), so authors can improve and target another venue promptly. There is no rebuttal for these papers.
- Rebuttal (bounded). Papers with at least one "weak accept" (a reviewer sees a path) are invited to submit a rebuttal (~26 November 2026) addressing explicit reviewer questions. The rebuttal resolves misunderstandings and clarifies; new experiments are not expected.
- Final decision (accept / reject) follows TPC discussion; notification PerCom 2027: ~18 December 2026. Accepted papers publish in IEEE Xplore.
Reading a decision against the stages
| Stage / outcome | What it means | Author move |
|---|---|---|
| Early reject | No reviewer saw a path; a structural gap (within-subject only, no baseline, thin contribution) | Reframe or reroute (UbiComp/IMWUT, MobiCom, or rework for next PerCom); do not resubmit unchanged |
| Invited to rebuttal | At least one reviewer is an advocate; repairable doubts remain | Answer explicit questions crisply; correct misreadings; point to existing evidence — no new claims |
| Accept | Contribution and evaluation hold | Camera-ready + dataset release; do not reopen scope |
| Reject after rebuttal | Doubts not resolved, or discussion turned | Use the reviews to rework; the study likely needs stronger cross-subject or deployment evidence |
The strategic reading: because the rebuttal cannot add experiments, write the initial submission so its weakest point is a misreading you can correct or a clarification you can give, not a missing experiment. The process rewards papers that arrive complete and only need disambiguating.
How PerCom differs from its neighbors
- vs. ACM UbiComp/IMWUT: IMWUT is a journal with rolling quarterly deadlines and a genuine major/minor revision cycle — you can add experiments in revision. PerCom has one deadline, one round, one bounded rebuttal, no revision. Never carry an IMWUT revise-and-resubmit mindset into a PerCom rebuttal.
- vs. MobiCom/SenSys: those venues center the network or the sensor system; PerCom reviewers center the human — a systems paper with no human-in-the-loop story reads as mis-venued here.
- vs. a plain accept/reject conference: the early-rejection gate is distinctive — many papers never reach the rebuttal at all, which is why the initial submission carries almost all the weight.
Show full SKILL.md (254 more words)Show less
Who reads you
Expect three ubicomp reviewers. They look for cross-subject / leave-one-subject-out evaluation, check whether an activity-recognition number is F1 on realistic class balance rather than pooled accuracy, ask whether subjects and deployments are real, and probe deployment realism and generalization. Because PerCom spans recognition, systems, and human factors, a paper is usually matched to reviewers from its own subarea — thin evaluations get caught, not skimmed.
Where author leverage actually exists
[Before submission] topic tags + a complete, cross-subject evaluation (largest lever)
[Early-rejection gate] nothing to do once here; the initial paper decided it
[Rebuttal] correct factual misreadings; answer explicit questions; cite existing
results the reviewer missed -- NOT promise new experiments
[After reject] no revise cycle; rework and target next PerCom or a neighbor venueA rebuttal moves borderline papers when it corrects a misreading or points to a number a reviewer overlooked; it does not move papers when it argues taste or promises work not in the submission.
Reading a review packet
Weight reviews before answering. A review that cites your sections, tables, and evaluation splits was read closely and will decide the discussion — its author is your likely advocate if the rebuttal holds. A review that discusses only novelty has left soundness to the others; answer each reviewer on the axis they raised. Reviewers usually end with an explicit question list; the rebuttal is scored on whether each question got a direct, evidenced answer from material already in the paper.
Misreadings to avoid
- Treating the rebuttal as a revision — you cannot add experiments; you can only clarify and correct.
- Assuming every paper gets a rebuttal — the early-rejection gate ends many papers first.
- Treating the rebuttal as a debate — the TPC discussion decides; your text is evidence for an advocate, not a closing argument.
- Projecting an IMWUT revise cycle — PerCom has one round; budget accordingly.
Output format
[Process stage] pre-submission / awaiting reviews / early-reject / invited-to-rebuttal / final
[Outcome likelihood] driver criterion (significance | soundness | evaluation | clarity)
[Criterion map] each review point -> significance | soundness | cross-subject evaluation | clarity
[Leverage plan] the next-stage action that can actually change the outcome
[Forbidden moves] identity leak / promising new experiments in the rebuttal© 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 PerCom-Skills/skills/percom-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Percom 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 |
|---|---|---|---|---|---|---|
| Percom Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Deepseek Reasonruvnet/ruflo | 74k | — | ~626 | Automated safety check: Notes | MIT | |
| Ejentum Reasoning Harnesssickn33/agentic-awesome-skills | 47k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Nowait Reasoning Optimizerdavila7/claude-code-templates | 32k | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Recall Reasoningparcadei/Continuous-Claude-v3 | 3.9k | 1 repos | ~758 | Automated safety check: Pass | MIT | |
| Nv Reason CxrNVIDIA/skills | 3.5k | — | ~3.9k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Ejentum Reasoning Harness
sickn33/agentic-awesome-skills
MCP server exposing four cognitive harness modes (reasoning, code, anti-deception, memory).
Nowait Reasoning Optimizer
davila7/claude-code-templates
Implements the NOWAIT technique for efficient reasoning in R1-style LLMs.
Recall Reasoning
parcadei/Continuous-Claude-v3
Search past reasoning for relevant decisions and approaches. An agent skill from parcadei/Continuous-Claude-v3.
- Official
Nv Reason Cxr
NVIDIA/skills
Used for command-shape or live NV-Reason-CXR chest X-ray reasoning smoke tests.
Diagnostic Reasoning
kunchenguid/firstmate
Agent-only procedure for diagnosing reported bugs. An agent skill from kunchenguid/firstmate.
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 Percom Review Process
What does Percom Review Process do?
A skill your agent uses when reasoning about how an IEEE PerCom research submission is evaluated, covering double-blind review, the three-TPC-member model, the early-rejection stage, the…. Percom Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how an IEEE PerCom research submission is evaluated, covering double-blind review, the three-TPC-member model, the early-rejection stage, the single-round bounded rebuttal gated by a "weak accept," the accept/reject decision, and how PerCom's process differs from ACM UbiComp/IMWUT's journal revise cycle.
When should I use Percom Review Process?
Percom Review Process fits situations like: reasoning about how an IEEE PerCom research submission is evaluated; covering double-blind review; the three-TPC-member model; the early-rejection stage.
How do I install Percom Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-review-process -a claude-code`. Or copy the skill folder (PerCom-Skills/skills/percom-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/percom-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Percom Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-review-process -a codex`. Or copy the skill folder (PerCom-Skills/skills/percom-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/percom-review-process in your project. Codex loads it when a task matches its description.
Can I use Percom 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 percom-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/percom-review-process, .gemini/skills/percom-review-process, .github/skills/percom-review-process and .opencode/skills/percom-review-process in your project.
What does Percom Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Percom Review Process is instructions for the agent only.
Does Percom 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 Percom 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 Percom Review Process use?
Percom 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 Percom Review Process use?
About 1.6k tokens (SKILL.md is roughly 6.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 Percom Review Process?
Skills that share tags, products or a category with Percom Review Process: Deepseek Reason (ruvnet/ruflo, 74k stars), Ejentum Reasoning Harness (sickn33/agentic-awesome-skills, 47k stars), Nowait Reasoning Optimizer (davila7/claude-code-templates, 32k stars) and Recall Reasoning (parcadei/Continuous-Claude-v3, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Percom Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.