percom-writing-style
Use when revising an IEEE PerCom paper for a pervasive-computing contribution on the first page, cross-subject claims stated precisely, a limitations section that argues rather than recites, evidence proportional to the claim, double-blind wording, and disciplined use of the tight IEEEtran 9-page budget.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-writing-style --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PerCom Writing Style Use this when revising the main paper. PerCom papers are IEEE Xplore proceedings read by ubicomp reviewers, so they need a **pervasive-computing contribution stated in the first page** and evidence a reviewer trusts on **people they did not train on**. The failure this skill prevents is a technically fine paper that reads like an ML result with a wearable title glued on, or a systems demo with no human at its center. ## Revision rules - **Lead with the ubicomp contribution:** the problem a real user or deployment faces, why current sensing is inadequate, the contribution (system and/or finding), the evidence, and what changes for pervasive computing. - **State claims at the right granularity.** A recognition claim must say **cross-subject or within-subject**, on what population, with which metric. "97% accuracy" without a split or a class balance is a red flag to a PerCom reviewer, not a headline. - **Pair every claim with proportional evidence** — real subjects, a fair baseline, F1 with confidence intervals on realistic class balance, deployment realism — not adjectives. - **Argue limitations; do not recite them.** Name the external, construct, and generaliz
- Revision rules
- Ubicomp paper skeleton
- Sentence-level rewrites
- Cross-subject and metric discipline
- Vignette: compressing an over-length study into 9 pages
- Output format
What does the percom-writing-style skill do?
Use when revising an IEEE PerCom paper for a pervasive-computing contribution on the first page, cross-subject claims stated precisely, a limitations section that argues rather than recites, evidence proportional to the claim, double-blind wording, and disciplined use of the tight IEEEtran 9-page budget.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-writing-style --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.