Individual skill
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.
PerCom-Skills/skills/percom-writing-style/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,404
- 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
- finance Derived category
- writing Derived category
- research 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 · 5,355 bytes
Read excerpt
# 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