Agent skill · Testing & QA

percom-topic-selection

Use when deciding whether a pervasive-computing project belongs at IEEE PerCom or should be routed to ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, or IPSN, and when distinguishing PerCom's human-centric ubicomp focus from networked-sensor-systems venues by contribution shape, the human-centricity test, and the IEEE-conference vs. IMWUT-journal model.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-topic-selection --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: PerCom-Skills/skills/percom-topic-selection/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# PerCom Topic Selection Decide the venue before drafting. PerCom — the IEEE International Conference on Pervasive Computing and Communications — is IEEE's flagship for **human-centric ubiquitous computing**: activity recognition, context-awareness, wearable and mobile sensing, and smart environments. Its papers are IEEE Xplore proceedings read for a **pervasive-computing contribution grounded in real human use**. A technically strong paper whose real lesson is about network protocols, low-power hardware, or a pure ML model is respected and then rejected as out of scope. ## The routing question that matters most PerCom overlaps most with **ACM UbiComp/IMWUT** in *topic* — both cover HAR, wearables, and smart spaces — so the decisive question is rarely "is this ubicomp?" but **"which model and calendar fits this paper now?"** UbiComp presents papers published in the **IMWUT journal** on **rolling quarterly deadlines** with a revise cycle; PerCom is an **IEEE conference** with a **single annual deadline**, a **bounded rebuttal**, and an in-person-presentation requirement. A strong ubicomp paper is publishable at either — choose by the publication model you want and the nearer honest

What's inside
Steps it walks through
  1. The routing question that matters most
  2. Neighbor-venue routing table
  3. Contribution shapes PerCom rewards
  4. The human-centricity and model-swap tests
  5. Evidence maturity, without the ladder cliché
  6. Cheap reconnaissance before committing
  7. Decision procedure
More from Awesome-Journal-Skills
All skills →
About this skill
What does the percom-topic-selection skill do?

Use when deciding whether a pervasive-computing project belongs at IEEE PerCom or should be routed to ACM UbiComp/IMWUT, MobiCom, MobiSys, SenSys, or IPSN, and when distinguishing PerCom's human-centric ubicomp focus from networked-sensor-systems venues by contribution shape, the human-centricity test, and the IEEE-conference vs. IMWUT-journal model.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-topic-selection --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going