wanshuiyin/Auto-claude-code-research-in-sleep / skills/skills-codex/comm-lit-review
comm-lit-review
VerifiedCommunications-domain literature review with Claude-style knowledge-base-first retrieval. Use when the task is about communications, wireless, networking, satellite/NTN, Wi-Fi, cellular, transport protocols, congestion control, routing, scheduling, MAC/PHY, rate adaptation, channel estimation, beamforming, or communication-system research and the user wants papers, related work, a survey, or a landscape summary.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.8 KB |
| references/domain-taxonomy.md | markdown | 1.4 KB |
| references/output-template.md | markdown | 983 B |
| references/source-policy.md | markdown | 3.0 KB |
| references/venue-tiering.md | markdown | 3.0 KB |
references/source-policy.md
View on GitHub# Source Policy
## Default priority
1. `IEEE Xplore`
2. `ScienceDirect`
3. `ACM Digital Library`
4. Domain-appropriate primary venues and broader web only when the first three are insufficient
5. Preprints only when necessary
## Database intent
- `IEEE Xplore`: best default for wireless, communications, PHY/MAC, networking, signal processing, NTN, and protocol work.
- `ScienceDirect`: useful for communications journals, Computer Networks, Ad Hoc Networks, Physical Communication, and systems papers published through Elsevier venues.
- `ACM Digital Library`: important second-line source for networking systems, transport protocols, mobile systems, and Internet measurement once the first two tiers are exhausted.
## When to widen beyond IEEE, ScienceDirect, and ACM
Widen only if one of these is true:
- the topic is heavily systems-oriented and canonical papers live in ACM or USENIX venues
- the recent frontier has not yet appeared in the three preferred databases
- the user explicitly asks for a broader sweep
When widening, prefer:
- `dl.acm.org`
- official conference pages
- publisher DOI pages
- authors' public PDFs that correspond to already-identified formal papers
- carefully targeted web search rather than open-ended browsing
## Search layering
Always layer the search in two dimensions:
1. **database layer**
- IEEE
- ScienceDirect
- ACM
- broader web
2. **venue layer within each database**
- top journals and top conferences
- mainstream strong venues
- all other relevant formal venues
Do not jump straight to broad web search if the topic can still be served by a higher database or venue tier.
## Venue policy
Follow [venue-tiering.md](venue-tiering.md).
The default behavior is:
- look for Tier A papers first
- expand to Tier B if the set is too small
- expand to Tier C if the topic is niche or the user wants broader coverage
If the user explicitly asks for `top venues only`, `top journals only`, or `top conferences only`, treat Tier A as a hard filter rather than a ranking hint.
## Publication policy
- Prefer peer-reviewed journals and major conferences.
- Label workshop papers as `workshop`.
- Label arXiv-only or author-hosted versions as `preprint`.
- If both a preprint and formal version exist, cite the formal version first.
## Time-window policy
If the user does not specify a year range:
- include a short foundational set
- include a recent set
- separate them explicitly in the synthesis
Recommended default split:
- `foundational`: before 2022
- `recent`: 2022 to present
## Search-query guidance
Build queries from:
- system name: `LEO`, `NTN`, `Wi-Fi 7`, `NR sidelink`
- technical problem: `rate adaptation`, `congestion control`, `beam hopping`
- layer name: `PHY`, `MAC`, `transport`, `cross-layer`
- method family if relevant: `RL`, `learning-based`, `optimization`, `prediction`
Avoid overly broad queries such as:
- `wireless AI`
- `satellite network paper`
Prefer tighter queries such as:
- `LEO satellite congestion control IEEE`
- `NTN rate adaptation IEEE Xplore`
- `Wi-Fi rate adaptation ScienceDirect`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |