Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
A skill your agent uses when positioning a SenSys paper against the sensing, embedded, IoT, and on-device-AI literature — sweeping the right venue lanes after the SenSys/IPSN/IoTDI merger, proving…
Install Sensys Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-related-work --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/SenSys-Skills/skills/sensys-related-work .claude/skills/sensys-related-work && 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 "sensys-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-related-work into .claude/skills/sensys-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-related-work", 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/SenSys-Skills/skills/sensys-related-workType 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 sensys-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-related-work --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/SenSys-Skills/skills/sensys-related-work .agents/skills/sensys-related-work && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sensys-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-related-work into .agents/skills/sensys-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-related-work", 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 sensys-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-related-work --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/SenSys-Skills/skills/sensys-related-work .cursor/skills/sensys-related-work && 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 "sensys-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-related-work into .cursor/skills/sensys-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-related-work", 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 SenSys-Skills/skills/sensys-related-work--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 sensys-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-related-work --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/SenSys-Skills/skills/sensys-related-work .gemini/skills/sensys-related-work && 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 "sensys-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-related-work into .gemini/skills/sensys-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-related-work", 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 sensys-related-workInstalls 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 sensys-related-work -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/SenSys-Skills/skills/sensys-related-work .github/skills/sensys-related-work && 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 "sensys-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-related-work into .github/skills/sensys-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-related-work", 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 sensys-related-work -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 sensys-related-work --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/SenSys-Skills/skills/sensys-related-work .opencode/skills/sensys-related-work && 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 "sensys-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-related-work into .opencode/skills/sensys-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-related-work", 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
sensys-related-work- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 406 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning a SenSys paper against the sensing, embedded, IoT, and on-device-AI literature — sweeping the right venue lanes after the SenSys/IPSN/IoTDI merger, proving…
- Positioning a SenSys paper against the sensing
- SKILL.md covers Sweep the right lanes, Prove the venue before you…, Distinguish from the closest… and Self-cite without breaking blind, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- On-device-AI literature — sweeping the right venue lanes after the SenSys/IPSN/IoTDI merger
What it does
Sensys Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a SenSys paper against the sensing, embedded, IoT, and on-device-AI literature — sweeping the right venue lanes after the SenSys/IPSN/IoTDI merger, proving each citation's venue via dblp/ACM DL against the MobiCom/NSDI/IPSN traps, distinguishing your mechanism from the nearest prior system, and self-citing blind-safely.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Literature review and Citation management. 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
- Positioning a SenSys paper against the sensing
- On-device-AI literature — sweeping the right venue lanes after the SenSys/IPSN/IoTDI merger
- Proving each citations venue via dblp/ACM DL against the MobiCom/NSDI/IPSN traps
- Distinguishing your mechanism from the nearest prior system
Example prompts
- “/sensys-related-work”
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
Sensys Related Work loads about 1k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 406 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). 406 words, ~1,047 tokens.
Download SKILL.mdSave it as
.claude/skills/sensys-related-work/SKILL.md (or your agent's skills folder).- name
- sensys-related-work
- description
- Use when positioning a SenSys paper against the sensing, embedded, IoT, and on-device-AI literature — sweeping the right venue lanes after the SenSys/IPSN/IoTDI merger, proving each citation's venue via dblp/ACM DL against the MobiCom/NSDI/IPSN traps, distinguishing your mechanism from the nearest prior system, and self-citing blind-safely.
SenSys Related Work
A SenSys related-work section has one job: show that you know the closest prior systems and can name, precisely, what your mechanism does that theirs does not. Vague "prior work is limited" draws blood at a systems venue where reviewers built that prior work. The 2026 merger widened the lanes you must sweep — IPSN and IoTDI literature is now sibling canon, not a separate world.
Sweep the right lanes
After the merger, a thorough sweep covers more ground than a pre-2026 SenSys paper did:
| Lane | Where it lives | What to look for |
|---|---|---|
| Low-power networked sensing | SenSys, IPSN (pre-2026) | The primitive/service your mechanism competes with |
| IoT design & deployment | SenSys, IoTDI (pre-2026) | Deployment methodology and system architecture priors |
| On-device / embedded AI | SenSys, TinyML venues, embedded-ML tracks | Footprint/latency baselines on real MCUs |
| Mobile & wireless systems | MobiCom, MobiSys | Adjacent mechanisms you must distinguish from, not claim |
| Sensing algorithms / DSP | Signal-processing venues | The math you build on but do not re-derive |
Prove the venue before you cite it
The sensing canon is the most-misfiled literature in systems. Directed diffusion is MobiCom, not SenSys; Glossy is IPSN; TinyDB's core is OSDI/SIGMOD. Getting a venue wrong in related work signals you do not know the field. Verify every load-bearing citation:
For each key citation:
1. Look it up on dblp (dblp.org) — read the venue key: conf/sensys? conf/ipsn? conf/mobicom?
2. Cross-check the ACM DL / proceedings for year and edition.
3. Record venue + year; if a rendering is unavailable, mark 待核实 — do NOT guess.Post-merger nuance: a paper's community may now be part of SenSys, but its historical venue is unchanged. A 2011 IPSN paper is still cited as IPSN 2011, even though IPSN merged into SenSys in 2026. Do not retroactively relabel.
Show full SKILL.md (161 more words)Show less
Distinguish from the closest system, concretely
The paragraph that matters most contrasts you with the single nearest prior system. Make it mechanism-level and, where possible, measurable:
Weak: "Unlike prior work, our system is more efficient."
Strong: "CTP-style collection assumes a persistent radio; our node duty-cycles the radio to a
1% budget and recovers routing state from non-volatile memory after each sleep, trading
a stated latency increase for a measured order-of-magnitude energy reduction (§4.2)."The strong version names the prior mechanism, the specific difference, and the trade-off with a
pointer — exactly what a systems reviewer checks (sensys-writing-style).
Self-cite without breaking blind
Double-blind still applies to related work:
- Cite your own prior papers in the third person ("Prior work [12] showed...", never "our earlier work [12]").
- Do not drop a relevant citation to preserve anonymity — omission is itself a signal and hurts the positioning.
- Keep any comparison to your own unpublished/concurrent work blind and factual.
Position, do not inflate
A SenSys reviewer distrusts a related-work section that makes every prior system sound broken. Credit what prior systems got right, then carve the specific gap you fill. A paper that respects its lineage and names one crisp delta is more credible than one that claims to obsolete the field.
Output format
[Lanes] which venue lanes swept (SenSys/IPSN/IoTDI/MobiCom/DSP) — gaps
[Venues] citations with unverified venues — listed for dblp/ACM DL check
[Nearest] the closest prior system + the concrete, measurable delta stated
[Blind] self-citations in third person? pass/gap
[Open] the one prior system a reviewer will expect and whether it is addressed© 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 SenSys-Skills/skills/sensys-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sensys Related Work 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 |
|---|---|---|---|---|---|---|
| Sensys Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Preprint Search on bioRxivLigphiDonk/Oh-my--paper | 739 | 12 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Deep Research WorkflowTokenRhythm/opensquilla | 7.1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Deep Research Workflow
TokenRhythm/opensquilla
Runs multi-round research in three stages with a persisted state file, evidence tracking and a long-form report with per-claim citations.
Academic Research Suite for Codex
Imbad0202/academic-research-skills-codex
A router skill that sends academic work such as literature reviews, drafting, citation checks, peer review and revision to the right workflow in the ARS suite.
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…
Related
Categories
Questions about Sensys Related Work
What does Sensys Related Work do?
A skill your agent uses when positioning a SenSys paper against the sensing, embedded, IoT, and on-device-AI literature — sweeping the right venue lanes after the SenSys/IPSN/IoTDI merger, proving…. Sensys Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a SenSys paper against the sensing, embedded, IoT, and on-device-AI literature — sweeping the right venue lanes after the SenSys/IPSN/IoTDI merger, proving each citation's venue via dblp/ACM DL against the MobiCom/NSDI/IPSN traps, distinguishing your mechanism from the nearest prior system, and self-citing blind-safely.
When should I use Sensys Related Work?
Sensys Related Work fits situations like: positioning a SenSys paper against the sensing; on-device-AI literature — sweeping the right venue lanes after the SenSys/IPSN/IoTDI merger; proving each citations venue via dblp/ACM DL against the MobiCom/NSDI/IPSN traps; distinguishing your mechanism from the nearest prior system.
How do I install Sensys Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-related-work -a claude-code`. Or copy the skill folder (SenSys-Skills/skills/sensys-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sensys-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Sensys Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-related-work -a codex`. Or copy the skill folder (SenSys-Skills/skills/sensys-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sensys-related-work in your project. Codex loads it when a task matches its description.
Can I use Sensys Related Work 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 sensys-related-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sensys-related-work, .gemini/skills/sensys-related-work, .github/skills/sensys-related-work and .opencode/skills/sensys-related-work in your project.
What does Sensys Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Sensys Related Work is instructions for the agent only.
Does Sensys Related Work 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 Sensys Related Work 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 Sensys Related Work use?
Sensys Related Work 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 Sensys Related Work use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Sensys Related Work?
Skills that share tags, products or a category with Sensys Related Work: Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Preprint Search on bioRxiv (LigphiDonk/Oh-my--paper, 739 stars) and Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sensys Related Work?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.