Design Audit Against Rams' Principles
thedotmack/claude-mem
Audits a design against Dieter Rams' ten principles of good design, scores each with evidence, and hands off a make-plan prompt for a new, refined or redesigned outcome.
A skill your agent uses when designing or auditing the evaluation of a MobiCom submission — building real-device testbeds, choosing RF and channel measurement methodology, injecting realistic…
MITAuto-check passed
Install Mobicom Experiments
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-experiments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobicom-experiments --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/MobiCom-Skills/skills/mobicom-experiments .claude/skills/mobicom-experiments && 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 "mobicom-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-experiments into .claude/skills/mobicom-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-experiments", 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/MobiCom-Skills/skills/mobicom-experimentsType 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 mobicom-experiments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobicom-experiments --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/MobiCom-Skills/skills/mobicom-experiments .agents/skills/mobicom-experiments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mobicom-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-experiments into .agents/skills/mobicom-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-experiments", 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 mobicom-experiments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobicom-experiments --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/MobiCom-Skills/skills/mobicom-experiments .cursor/skills/mobicom-experiments && 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 "mobicom-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-experiments into .cursor/skills/mobicom-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-experiments", 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 MobiCom-Skills/skills/mobicom-experiments--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 mobicom-experiments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobicom-experiments --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/MobiCom-Skills/skills/mobicom-experiments .gemini/skills/mobicom-experiments && 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 "mobicom-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-experiments into .gemini/skills/mobicom-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-experiments", 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 mobicom-experimentsInstalls 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 mobicom-experiments -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/MobiCom-Skills/skills/mobicom-experiments .github/skills/mobicom-experiments && 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 "mobicom-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-experiments into .github/skills/mobicom-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-experiments", 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 mobicom-experiments -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 mobicom-experiments --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/MobiCom-Skills/skills/mobicom-experiments .opencode/skills/mobicom-experiments && 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 "mobicom-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-experiments into .opencode/skills/mobicom-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-experiments", 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
mobicom-experiments- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 601 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when designing or auditing the evaluation of a MobiCom submission — building real-device testbeds, choosing RF and channel measurement methodology, injecting realistic…
- Auditing the evaluation of a MobiCom submission — building real-device testbeds
- SKILL.md covers Questions before measurements, Measurement methodology…, Energy is a first-class metric and Baselines on tuned hardware, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Choosing RF and channel measurement methodology
What it does
Mobicom Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing the evaluation of a MobiCom submission — building real-device testbeds, choosing RF and channel measurement methodology, injecting realistic mobility and interference, profiling energy on hardware, picking tuned baselines, and reporting distributions so wireless reviewers see where the mechanism wins and breaks.
Its SKILL.md is about 1.4k 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
- Auditing the evaluation of a MobiCom submission — building real-device testbeds
- Choosing RF and channel measurement methodology
- Injecting realistic mobility and interference
- Profiling energy on hardware
Example prompts
- “/mobicom-experiments”
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
Mobicom Experiments loads about 1.4k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 601 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). 601 words, ~1,422 tokens.
Download SKILL.mdSave it as
.claude/skills/mobicom-experiments/SKILL.md (or your agent's skills folder).- name
- mobicom-experiments
- description
- Use when designing or auditing the evaluation of a MobiCom submission — building real-device testbeds, choosing RF and channel measurement methodology, injecting realistic mobility and interference, profiling energy on hardware, picking tuned baselines, and reporting distributions so wireless reviewers see where the mechanism wins and breaks.
MobiCom Experiments
MobiCom's evidence culture is physical: a mobile/wireless mechanism is believed when it is measured over the air, on real hardware, under conditions that resemble deployment. A simulation-only or single-run evaluation reads as under-done here. Design the evaluation as a set of questions about the mechanism, then build the smallest measurement campaign that answers them on real radios.
Questions before measurements
Write the evaluation's subsection titles as questions first — Does the mechanism hold under mobility? What does it cost in energy at rest? When does the channel defeat it? — then design one experiment per question. The inverted approach (run everything, narrate the survivors) produces the benchmark tour that MobiCom reviews call unfocused.
A minimal matrix for a wireless-mechanism paper:
| Question | Experiment | Metrics that answer it |
|---|---|---|
| Does it work in the motivating condition? | over-the-air run under the target channel/mobility | delivery rate, goodput, SNR/BER distribution |
| What does it cost when idle? | baseline with no stress | energy-per-bit, power draw, CPU/airtime overhead |
| Why does it work? | component breakdown / ablation | per-mechanism contribution |
| Does it scale? | node / distance / density sweeps | knee location, per-node or per-meter curve |
| When does it break? | interference, deep fades, high mobility | the regime where baselines win |
| Does it hold over time? | multi-hour or multi-day runs | drift, stability, tail behavior |
Measurement methodology reviewers check
- State the RF setup completely: radio/SDR model and firmware, carrier frequency, bandwidth, transmit power, antenna and gain, and receiver chain. A number without its radio context is not interpretable.
- Name the channel condition: distance, line-of-sight vs multipath, ambient interference, and how you characterized it (RSSI/CSI traces, coherence time). Do not let "in our lab" stand in for a channel description.
- Make mobility explicit: walker paths, speeds, and schedules for mobility experiments, and a stationary control. "Under mobility" without the traces is unverifiable.
- Report ground-truth honestly: how position, gesture, or decode-correctness truth was obtained, and its own error, since a sensing result is only as good as its reference.
Energy is a first-class metric
Battery and harvested-energy claims are common at MobiCom and are held to instrument-level scrutiny:
Energy report checklist:
instrument: power monitor / shunt + DAQ, sampling rate
quantity: energy-per-bit or per-operation, not just average power
boundary: what is inside the measured envelope (radio only? whole tag?)
budget: for harvested/batteryless designs, the source and the duty cycleAn energy claim that cannot be re-derived from a described measurement setup should not survive your own audit.
Show full SKILL.md (244 more words)Show less
Baselines on tuned hardware
- Compare against the incumbent people actually run, configured the way its own documentation prescribes — an untuned baseline is the most common credibility wound in systems and wireless reviewing.
- Include the do-less baseline: the trivial fix (more power, a fixed high rate, another antenna). If the mechanism cannot beat it at equal cost, that is the finding.
- When a competitor cannot be run (proprietary radio, unavailable hardware), reimplement and label it a reimplementation, or compare on published numbers with the configuration deltas stated.
Distributions, not superlatives
- Report percentiles and confidence intervals for delivery, latency, and throughput
claims; a single "up to N×" without the distribution behind it is a review risk
(
mobicom-writing-style). - Show CDFs for headline results and repeat runs across enough channel realizations, days, or walker paths to expose run-to-run spread; state what varies between repeats.
- Wireless results are time- and place-dependent — a result from one room at one hour is not a claim about the mechanism until the spread is characterized.
Audit checklist
- Every evaluation subsection answers a named question.
- RF setup, channel condition, and mobility fully specified per experiment.
- Energy measured with a described instrument and boundary, not estimated.
- Incumbent-grade baseline present and tuned; do-less baseline present.
- Percentiles + distributions for headline metrics; multi-run spread reported.
- At least one condition the mechanism does not win, discussed rather than buried.
- Numbers in abstract/intro regenerate from the recorded runs.
- A hardware-optional or downscaled variant exists for artifact evaluators
(
mobicom-artifact-evaluation).
Output format
[Evidence form] over-the-air testbed / deployment / trace / simulation (claimed vs actual)
[Question map] question -> experiment -> metric (gaps flagged)
[RF+channel] setup and conditions specified? y/n per headline experiment
[Energy] measured, with instrument and boundary? y/n
[Baseline audit] incumbent tuned? do-less present?
[Break condition] regime where the mechanism loses: <named or MISSING>
[Priority additions] ordered by review-risk reduction per testbed-week© 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 MobiCom-Skills/skills/mobicom-experiments of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mobicom Experiments 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 |
|---|---|---|---|---|---|---|
| Mobicom Experiments this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Design Audit Against Rams' Principlesthedotmack/claude-mem | 99k | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Experiment Auditwanshuiyin/Auto-claude-code-research-in-sleep | 17k | 1 repos | ~2.7k | Automated safety check: Notes | MIT | |
| Experiment Auditwanshuiyin/Auto-claude-code-research-in-sleep | 17k | — | ~3.2k | Automated safety check: Notes | MIT | |
| Experiment Designeralirezarezvani/claude-skills | 28k | 1 repos | ~783 | Automated safety check: Pass | MIT | |
| OpenClaw Design Auditopenclaw/clawhub | 9.5k | — | ~498 | Automated safety check: Pass | MIT |
Similar skills
Experiment Audit
wanshuiyin/Auto-claude-code-research-in-sleep
Audit experiment integrity before claiming results. An agent skill from wanshuiyin/Auto-claude-code-research-in-sleep.
Experiment Audit
wanshuiyin/Auto-claude-code-research-in-sleep
Audit experiment integrity before claiming results. An agent skill from wanshuiyin/Auto-claude-code-research-in-sleep.
Experiment Designer
alirezarezvani/claude-skills
A skill your agent uses when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor.
OpenClaw Design Audit
openclaw/clawhub
Audits OpenClaw frontend code and rendered pages for token misuse, reimplemented primitives, accessibility and responsive defects and off-brand copy, with an evidence-based report.
Design System
affaan-m/ECC
Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with…
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 Mobicom Experiments
What does Mobicom Experiments do?
A skill your agent uses when designing or auditing the evaluation of a MobiCom submission — building real-device testbeds, choosing RF and channel measurement methodology, injecting realistic…. Mobicom Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing the evaluation of a MobiCom submission — building real-device testbeds, choosing RF and channel measurement methodology, injecting realistic mobility and interference, profiling energy on hardware, picking tuned baselines, and reporting distributions so wireless reviewers see where the mechanism wins and breaks.
When should I use Mobicom Experiments?
Mobicom Experiments fits situations like: auditing the evaluation of a MobiCom submission — building real-device testbeds; choosing RF and channel measurement methodology; injecting realistic mobility and interference; profiling energy on hardware.
How do I install Mobicom Experiments in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-experiments -a claude-code`. Or copy the skill folder (MobiCom-Skills/skills/mobicom-experiments in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mobicom-experiments in your project. Claude Code loads it when a task matches its description.
How do I install Mobicom Experiments in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-experiments -a codex`. Or copy the skill folder (MobiCom-Skills/skills/mobicom-experiments in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mobicom-experiments in your project. Codex loads it when a task matches its description.
Can I use Mobicom Experiments 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 mobicom-experiments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mobicom-experiments, .gemini/skills/mobicom-experiments, .github/skills/mobicom-experiments and .opencode/skills/mobicom-experiments in your project.
What does Mobicom Experiments need to run?
SKILL.md names no scripts, command-line tools or credentials: Mobicom Experiments is instructions for the agent only.
Does Mobicom Experiments 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 Mobicom Experiments 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 Mobicom Experiments use?
Mobicom Experiments 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 Mobicom Experiments use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Mobicom Experiments?
Skills that share tags, products or a category with Mobicom Experiments: Design Audit Against Rams' Principles (thedotmack/claude-mem, 99k stars), Experiment Audit (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars), Experiment Audit (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars) and Experiment Designer (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mobicom Experiments?
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.