Agent skill · Data & Analytics

percom-artifact-evaluation

Use when packaging an IEEE PerCom sensing artifact and dataset for reproducibility and any badging (IEEE Open Research Objects / Results Reproduced, IEEE DataPort or Zenodo deposit), covering what a ubicomp evaluator checks first for human-subjects sensing data, cross-subject reproduction, de-identification, and honest degrees of reproducibility.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-artifact-evaluation --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: PerCom-Skills/skills/percom-artifact-evaluation/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 Artifact Evaluation Use this for reproducibility packaging. **First, a cycle caveat:** unlike SIGSOFT venues, PerCom has not historically run a *mandatory* formal artifact-evaluation track with a fixed badge set, and whether a given edition offers a reproducibility/badging track (e.g., **IEEE Open Research Objects / Results Reproduced**) is **待核实** — confirm on the current call. Regardless of whether a badge is offered, a well-packaged, de-identified sensing dataset and reproducible pipeline is a scored strength in the double-blind review and a lasting community contribution. ## What "reproducible" means for a ubicomp sensing paper Two deliverables, kept distinct: - **The anonymized review package** (at submission): dataset link and code scrubbed of owner, testbed, and lab identity, for the double-blind reviewers. - **The public deposit** (after acceptance): a de-identified dataset and code in a DOI-issuing archive under an open license — the version others cite and reuse, and the version any badge program evaluates. ## What a ubicomp evaluator opens first | Claim type | First thing inspected | Common failure caught | |---|---|---| | An activity/context recognizer | The sc

What's inside
Steps it walks through
  1. What "reproducible" means for a ubicomp sensing paper
  2. What a ubicomp evaluator opens first
  3. Packaging plan
  4. De-identification is the ubicomp-specific bar
  5. Worked vignette: a wearable-HAR dataset + recognizer
  6. Calibration
  7. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the percom-artifact-evaluation skill do?

Use when packaging an IEEE PerCom sensing artifact and dataset for reproducibility and any badging (IEEE Open Research Objects / Results Reproduced, IEEE DataPort or Zenodo deposit), covering what a ubicomp evaluator checks first for human-subjects sensing data, cross-subject reproduction, de-identification, and honest degrees of reproducibility.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-artifact-evaluation --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