comm-lit-review-claude-single
Skill2 starsChanged 6 months agoMITView on GitHub
Communications-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. Search Zotero, Obsidian, and local paper folders first when available, then search IEEE Xplore, ScienceDirect, ACM Digital Library, and broader web in that order.
We split this skill into the rules it gives an agent
33 rules. About 0 are common, 27 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈27
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Use this skill for communications-domain literature review when the topic is about:
- Distinctive: line 24
If the center of gravity is generic ML architecture research, pure control theory without communications literature, or software/API …
- Very specific: line 28
PAPER_LIBRARY: Check local PDFs in this order:
- Very specific: line 38
If — sources: is specified, only search the listed sources.
- Distinctive: line 39
If not specified, default to:
- Very specific: line 59
If all is specified, interpret it as the full default source set.
- Distinctive: line 75
If a source is unavailable, do not fail.
- Distinctive: line 90
prefer peer-reviewed journals and major conferences
- Distinctive: line 93
if both preprint and formal version exist, cite the formal version first
- Distinctive: line 97
if the user does not specify a year range, include both a short foundational set and a recent set
- Distinctive: line 152
start from Tier A
- Distinctive: line 155
only then broaden to full web search
- Very specific: line 157
if the user says only top venues, top journals only, or top conferences only, treat Tier A as a hard filter
- Distinctive: line 170
treat these as high-priority evidence because they reflect the user's existing library
- Distinctive: line 180
treat these notes as the user's processed understanding of the topic
- Very specific: line 184
Run this step if local is enabled.
- Distinctive: line 188
read the first pages of relevant PDFs
- Distinctive: line 190
use local hits to guide and de-duplicate later external search
- Distinctive: line 194
Use a layered search strategy.
- Distinctive: line 211
start from Tier A venues
- Distinctive: line 234
Do not collapse transport-layer rate control and PHY/MAC rate adaptation into one bucket without saying so explicitly.
- Distinctive: line 246
When useful, explicitly separate:
- Distinctive: line 255
If evidence is weak, say so instead of smoothing it over.
- Distinctive: line 259
Use a literature table with these columns:
- Distinctive: line 274
After the table, summarize in this order:
- Distinctive: line 290
Never fail because Zotero or Obsidian MCP is missing.
- Distinctive: line 291
Prefer user-owned sources first when available, but do not let them replace external validation.
- Distinctive: line 292
Prefer primary formal sources over summaries or tertiary commentary.
- Very specific: line 293
Prefer IEEE and ScienceDirect first, ACM second, and only then broader web search unless the user asks otherwise.
- Distinctive: line 294
Search venue tiers from top to broad within each database tier.
- Distinctive: line 295
Treat venue tiers as soft ranking by default and hard constraint only when the user explicitly asks for top-only search.
- Distinctive: line 296
Do not pretend a preprint is peer reviewed.
- Distinctive: line 297
If the topic spans multiple layers, say that the literature itself is split across layers.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Comm Lit Review Claude Single
Research topic: $ARGUMENTS
Purpose
Use this skill for communications-domain literature review when the topic is about:
- wireless communications
- cellular systems,
4G/5G/6G,NR,NTN - satellite,
LEO,GEO, integrated space-air-ground systems - Wi-Fi, WLAN, mesh, ad hoc, sidelink, V2X
- routing, scheduling, resource allocation, beamforming
- rate adaptation, link adaptation,
ACM,HARQ,CSIfeedback - transport protocols and congestion control in communication networks
- cross-layer optimization for communication systems
If the center of gravity is generic ML architecture research, pure control theory without communications literature, or software/API documentation rather than papers, fall back to a general literature skill.
Constants
- PAPER_LIBRARY: Check local PDFs in this order:
papers/in the current projectliterature/in the current project- Custom path specified by the user in
CLAUDE.mdunder## Paper Library
- MAX_LOCAL_PAPERS = 20: Maximum number of local PDFs to scan. If there are more, prioritize by filename and first-page relevance.
Source Selection
Parse $ARGUMENTS for a — sources: directive.
- If
— sources:is specified, only search the listed sources. - If not specified, default to:
zoteroobsidianlocalieeesciencedirectacmweb
Valid source values:
zoteroobsidianlocalieeesciencedirectacmweball
If all is specified, interpret it as the full default source set.
Retrieval Order
This is a knowledge-base-first skill. Search in this order unless the user overrides it:
ZoteroObsidian- local
papers/andliterature/ IEEE XploreScienceDirectACM Digital Library- broader web
Graceful degradation rules:
- If a source is unavailable, do not fail.
- Skip it silently.
- Continue to the next source.
External Search Policy
For external search:
- prefer
IEEE Xplorefirst - then
ScienceDirect - then
ACM - then broader web only when needed
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 preprint and formal version exist, cite the formal version first
Time-window policy:
- if the user does not specify a year range, include both a short foundational set and a recent set
- recommended split:
foundational: before 2022recent: 2022 to present
Venue Priority
Within each database tier, search venue tiers in this order.
Tier A
Journals:
IEEE Journal on Selected Areas in Communications (JSAC)IEEE/ACM Transactions on Networking (ToN)IEEE Transactions on Wireless Communications (TWC)IEEE Transactions on Communications (TCOM)
Conferences:
ACM SIGCOMMUSENIX NSDIACM MobiComACM CoNEXTIEEE INFOCOM
Tier B
Journals:
IEEE Transactions on Vehicular Technology (TVT)IEEE Wireless Communications Letters (WCL)IEEE Communications LettersComputer NetworksComputer CommunicationsAd Hoc NetworksPhysical Communication
Conferences:
IEEE ICCIEEE GLOBECOMIEEE WCNCIEEE PIMRCACM MobiHoc
Tier C
- other relevant IEEE journals and transactions
- other relevant Elsevier journals
- other clearly relevant ACM conferences and workshops
- topic-specific satellite, optical, vehicular, IoT, aerial, or edge communications venues
Usage rules:
- start from Tier A
- widen to Tier B if needed
- widen to Tier C if still sparse
- only then broaden to full web search
- by default this is a soft priority, not a hard whitelist
- if the user says
only top venues,top journals only, ortop conferences only, treat Tier A as a hard filter
Workflow
Step 0a: Search Zotero Library
Skip this step if Zotero MCP is not configured or zotero is not enabled.
If available:
- search by topic
- capture title, authors, year, venue
- pull user annotations, tags, or collections when present
- treat these as high-priority evidence because they reflect the user's existing library
Step 0b: Search Obsidian Vault
Skip this step if Obsidian MCP is not configured or obsidian is not enabled.
If available:
- search topic-related notes
- collect summaries, wikilinks, tags, and paper references
- treat these notes as the user's processed understanding of the topic
Step 0c: Scan Local Paper Library
Run this step if local is enabled.
- locate PDFs from
papers/**/*.pdfandliterature/**/*.pdf - de-duplicate against Zotero hits when possible
- read the first pages of relevant PDFs
- extract title, authors, year, problem, method, and relevance
- use local hits to guide and de-duplicate later external search
Step 1: Search External Primary Sources
Use a layered search strategy. For communications topics, avoid random blog posts or tertiary summaries.
Database ladder:
ieeexplore.ieee.orgsciencedirect.comdl.acm.org- broader web using primary publisher pages, official conference sites, DOI pages, and author-hosted copies of already-identified formal papers
Move to the next database tier only when:
- the higher-priority tier is too sparse
- the topic clearly publishes elsewhere
- the user explicitly asks for broader coverage
Within each database tier:
- start from Tier A venues
- widen to Tier B if needed
- widen to Tier C if still sparse
Step 2: Extract Paper-Level Facts
For each relevant paper, capture:
- Title
- Authors
- Year
- Venue
- Layer or system scope
- Scenario and assumptions
- Core method
- Main result or claim
- Limitation
- Relevance to the user's topic
- Source URL
- Source origin:
zotero,obsidian,local,ieee,sciencedirect,acm, orweb
Favor concrete numbers, assumptions, and problem definitions over generic paraphrases.
Do not collapse transport-layer rate control and PHY/MAC rate adaptation into one bucket without saying so explicitly.
Synthesis Rules
Group papers by technical axis rather than by search order. Common groupings:
PHY/MACadaptation- transport and congestion control
NTNand satellite resource management- cross-layer or learning-based control
- measurement and empirical studies
When useful, explicitly separate:
- foundational vs recent work
- formal publications vs preprints
- top-tier vs lower-tier venues
- single-link vs multi-user formulations
- simulation-only vs deployment-backed work
- user-owned sources vs newly surfaced external papers
If evidence is weak, say so instead of smoothing it over.
Output
Use a literature table with these columns:
| Paper | Venue | Year | Layer | Scenario | Method | Key Result | Limitation | Relevance | Source |
Source should indicate where the paper came from first:
zoteroobsidianlocalieeesciencedirectacmweb
After the table, summarize in this order:
- what the field is mostly trying to solve
- how papers cluster into
2-4approaches - what the user already had vs what was newly surfaced
- where the evidence is strong vs weak
- what research gap remains
End with Practical Takeaway:
- dominant current approach
- likely saturated direction
- promising open direction
Key Rules
- Never fail because Zotero or Obsidian MCP is missing.
- Prefer user-owned sources first when available, but do not let them replace external validation.
- Prefer primary formal sources over summaries or tertiary commentary.
- Prefer
IEEEandScienceDirectfirst,ACMsecond, and only then broader web search unless the user asks otherwise. - Search venue tiers from top to broad within each database tier.
- Treat venue tiers as soft ranking by default and hard constraint only when the user explicitly asks for top-only search.
- Do not pretend a preprint is peer reviewed.
- If the topic spans multiple layers, say that the literature itself is split across layers.
Other versions2 projects use a version of this.
Word for word · 2
- Chanw-research/claude-code-paper-writing★ 42100% same
- catalsqlb-cmd/Prism-H★ 16100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository84 other files it gives its agents.
- skills/rules/common/agents.mdAGENTS.md
- skills/rules/zh/agents.mdAGENTS.md
- ablation-plannerSkill
- alphaxivSkill
- analyze-resultsSkill
- arxivSkill
- auto-paper-improvement-loopSkill
- auto-review-loop-llmSkill
- auto-review-loop-minimaxSkill
- auto-review-loopSkill
- citation-auditSkill
- claims-draftingSkill
- deepxivSkill
- dse-loopSkill
- embodiment-descriptionSkill
- exa-searchSkill
- experiment-auditSkill
- experiment-bridgeSkill
- experiment-planSkill
- experiment-queueSkill
- feishu-notifySkill
- figure-descriptionSkill
- figure-specSkill
- formula-derivationSkill
- gemini-searchSkill
- grant-proposalSkill
- idea-creatorSkill
- idea-discovery-robotSkill
- idea-discoverySkill
- invention-structuringSkill
- jurisdiction-formatSkill
- kill-argumentSkill
- mermaid-diagramSkill
- meta-optimizeSkill
- monitor-experimentSkill
- novelty-checkSkill
- openalexSkill
- overleaf-syncSkill
- paper-claim-auditSkill
- paper-compileSkill
- paper-figureSkill
- paper-illustration-image2Skill
- paper-illustrationSkill
- paper-planSkill
- paper-posterSkill
- paper-slidesSkill
- paper-talkSkill
- paper-writeSkill
- paper-writingSkill
- patent-novelty-checkSkill
- patent-pipelineSkill
- patent-reviewSkill
- pixel-artSkill
- prior-art-searchSkill
- proof-checkerSkill
- proof-writerSkill
- qzcliSkill
- rebuttalSkill
- research-litSkill
- research-pipelineSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

