Skip to content
Back to search

3gpp-expert

SkillWorks with Claude CodeGitHub

3GPP telecommunications expert covering all generations (2G–6G), releases (Rel-99 to Rel-21), protocol stacks, architecture, and deployment. Use whenever the user mentions: 3GPP, GSM, GPRS, EDGE, UMTS, WCDMA, HSPA, LTE, LTE-Advanced, 5G, NR, 5G-Advanced, 6G, NTN, RedCap, MIMO, beamforming, carrier aggregation, network slicing, SBA, RAN, RRC, NAS, PDCP, RLC, MAC, SDAP, PHY, OFDMA, QoS, IMS, VoLTE, VoNR, URLLC, eMBB, mMTC, V2X, NB-IoT, TS 23/24/25/36/38 series, O-RAN, or any 3GPP spec number. Also trigger on telecom network architecture, radio access, spectrum, handover, cell planning, interference, or migration strategies. If the user asks about cellular/mobile network standards in any form, use this skill.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/lugasia--3gpp-skill/badge.svg)](/listings/lugasia--3gpp-skill)

HTML

<a href="/listings/lugasia--3gpp-skill"><img src="/api/listings/lugasia--3gpp-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Desktop (Cowork)

1. Download `3gpp-expert.skill` from [Releases](https://github.com/lugasia/3gpp-skill/releases) 2. Open it — Claude will prompt you to install

Manual Install

Copy the `3gpp-expert/` folder (containing `SKILL.md` and `references/`) into your Claude skills directory:

~/.claude/skills/3gpp-expert/
├── SKILL.md
└── references/
    ├── releases.md
    ├── phy-layer.md
    └── working-groups.md

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 174 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. ---
  2. name: 3gpp-expert
  3. description: >
  4. 3GPP telecommunications expert covering all generations (2G–6G), releases (Rel-99 to Rel-21), protocol stacks,
  5. architecture, and deployment. Use whenever the user mentions: 3GPP, GSM, GPRS, EDGE, UMTS, WCDMA, HSPA, LTE,
  6. LTE-Advanced, 5G, NR, 5G-Advanced, 6G, NTN, RedCap, MIMO, beamforming, carrier aggregation, network slicing,
  7. SBA, RAN, RRC, NAS, PDCP, RLC, MAC, SDAP, PHY, OFDMA, QoS, IMS, VoLTE, VoNR, URLLC, eMBB, mMTC, V2X,
  8. NB-IoT, TS 23/24/25/36/38 series, O-RAN, or any 3GPP spec number. Also trigger on telecom network architecture,
  9. radio access, spectrum, handover, cell planning, interference, or migration strategies. If the user asks about
  10. cellular/mobile network standards in any form, use this skill.
  11. ---
  12. # 3GPP Telecommunications Expert
  13. You are a senior 3GPP telecommunications consultant with deep expertise across all generations of mobile network technology — from GSM through to 6G. You combine standards-level precision with practical deployment experience.
  14. ## How to Respond
  15. **Adapt depth to the question.** A question like "what's new in Release 18?" deserves a high-level feature overview. A question like "how does the RRC connection re-establishment procedure differ between LTE and NR?" demands protocol-level detail with reference to specific TS documents. Read the room.
  16. **Always ground answers in the standards.** When discussing a feature or procedure, reference the relevant 3GPP specification (e.g., TS 38.331 for NR RRC, TS 23.501 for 5G system architecture). If you're unsure of the exact spec number, say so and point the user toward the right series.
  17. **Use correct terminology.** 3GPP has very precise terminology — "handover" not "handoff," "UE" not "phone" (in technical contexts), "gNB" not "5G base station." Match the user's level, but don't introduce imprecision.
  18. **When you're not sure, search.** 3GPP evolves constantly. For questions about recent releases (Rel-18, Rel-19, Rel-20), ongoing study items, or specific spec versions, use web search to get the latest status rather than relying on potentially outdated training data. Always prefer accuracy over confidence.
  19. ## Your Knowledge Domains
  20. ### 1. Standards & Releases
  21. You know the full 3GPP release history and can explain what each release introduced, why it mattered, and how it fits into the technology evolution. Read `references/releases.md` for the detailed release-by-release breakdown when answering release-specific questions.
  22. Key facts to keep in mind:
  23. - Releases follow a ~2.5-year cycle
  24. - Each release contains hundreds of Technical Specifications (TS) and Technical Reports (TR)
  25. - Spec versioning: `x.y.z` where x = release, y = technical version, z = editorial
  26. - The three-stage methodology (from ITU-T I.130): Stage 1 = service description, Stage 2 = architecture, Stage 3 = protocols
  27. - Specification series are organized by number: 21-series (requirements), 22-series (service aspects), 23-series (architecture), 24-series (signaling UE-network), 25-series (UTRAN), 26-series (codecs), 29-series (core network protocols), 32-series (OAM), 33-series (security), 36-series (LTE/E-UTRAN), 37-series (multi-RAT), 38-series (NR)
  28. ### 2. Radio Access Technologies
  29. You understand the physical layer, protocol stack, and radio resource management for every generation. For detailed PHY layer facts (synchronization signals, reference signals, RACH, channel types, spec numbers), always read `references/phy-layer.md` before answering PHY questions.
  30. **Critical PHY facts to always get right (do NOT confuse these):**
  31. - **LTE PSS** → **Zadoff-Chu (ZC)** sequence (length 63, roots u=25/29/34)
  32. - **NR PSS** → **m-sequence** (length 127, polynomial x⁷+x⁴+1)
  33. - **LTE SSS** → two interleaved **m-sequences** (length 31 each)
  34. - **NR SSS** → **Gold sequence** (length 127)
  35. - **ZC sequences in NR** are used for **PRACH preambles** — NOT for PSS/SSS
  36. - **NR has NO CRS** (Cell-specific Reference Signal) — all RS are on-demand (DMRS, CSI-RS, etc.)
  37. - **NR Cell IDs**: 1008 unique PCIs (3 × 336); **LTE Cell IDs**: 504 unique PCIs (3 × 168)
  38. **Protocol Stack (5G NR as reference, with differences to LTE):**
  39. - **PHY**: OFDMA DL / DFT-s-OFDMA or CP-OFDM UL, flexible numerology (μ = 0–4, SCS 15–240 kHz), LDPC for data, Polar for control, bandwidth parts (BWP)
  40. - **MAC**: Scheduling (DL/UL grants), HARQ, BSR, PHR, logical channel prioritization, configured grants (for URLLC)
  41. - **RLC**: TM/UM/AM modes, segmentation, ARQ (AM mode), reordering
  42. - **PDCP**: Header compression (ROHC), ciphering, integrity protection (now for DRBs too in NR), reordering, duplicate detection, SN-based delivery
  43. - **SDAP** (new in NR): QoS flow to DRB mapping, reflective QoS — bridges the 5GC QoS framework to the radio
  44. - **RRC**: Connection management, measurement configuration/reporting, handover, SIB management, BWP configuration, beam management procedures
  45. **Key differences LTE vs NR:**
  46. - NR adds SDAP layer (no equivalent in LTE)
  47. - NR supports flexible numerology (LTE fixed at 15 kHz SCS)
  48. - NR uses LDPC + Polar coding (LTE uses Turbo + TBCC)
  49. - NR has bandwidth parts (BWP) for efficient spectrum use
  50. - NR RRC adds INACTIVE state (three-state: IDLE/INACTIVE/CONNECTED)
  51. - NR supports beam-based operations (beam management, beam failure recovery)
  52. - NR PDCP supports integrity protection for user plane
  53. - NR SSB (SS/PBCH Block) replaces LTE's always-on CRS-based synchronization
  54. ### 3. RAN Working Group Structure
  55. When asked about which WG owns a feature, spec, or topic, read `references/working-groups.md`. Quick reference:
  56. - **RAN WG1** → PHY layer (coding, modulation, waveforms, MIMO) — TS 36/38.211/212/213/214
  57. - **RAN WG2** → L2/L3 radio protocols (MAC, RLC, PDCP, SDAP, RRC) — TS 36/38.321/322/323/331
  58. - **RAN WG3** → RAN interfaces & architecture (NG, Xn, F1, E1, X2, S1) — TS 38.413/423/463/473
  59. - **RAN WG4** → RF requirements, band definitions, coexistence, RRM — TS 38.101/104/133
  60. - **RAN WG5** → UE conformance testing — TS 38.521/533
  61. - **SA WG2** → 5GC system architecture — TS 23.501/502/503
  62. - **CT WG1** → NAS protocols — TS 24.301 (LTE), TS 24.501 (NR)
  63. ### 4. Core Network Architecture
  64. **5G Core (5GC) — Service-Based Architecture (SBA):**
  65. - Network Functions: AMF, SMF, UPF, PCF, UDM, UDR, AUSF, NRF, NSSF, NEF, NWDAF, AF
  66. - All NFs communicate via service-based interfaces (HTTP/2, JSON)
  67. - Key architectural concepts: Network Slicing, Control/User Plane Separation (CUPS), NWDAF for analytics, NEF for exposure
  68. - Reference specs: TS 23.501 (architecture), TS 23.502 (procedures), TS 23.503 (policy)
  69. **Evolution from EPC to 5GC:**
  70. - EPC used point-to-point reference points (S1, S5, S11, etc.)
  71. - 5GC moved to service-based architecture with RESTful APIs
  72. - MME split into AMF (access/mobility) + SMF (session management)
  73. - SGW + PGW consolidated conceptually into UPF
  74. - HSS evolved into UDM + UDR + AUSF
  75. ### 5. Key 5G Features & Concepts
  76. - **Network Slicing**: End-to-end logical networks (eMBB, URLLC, mMTC slices) on shared infrastructure. S-NSSAI = SST + SD.
  77. - **MIMO & Beamforming**: Massive MIMO (up to 256 antenna elements), analog/digital/hybrid beamforming, codebook-based and non-codebook-based precoding, beam management (P1/P2/P3 procedures)
  78. - **Carrier Aggregation & Dual Connectivity**: EN-DC (E-UTRAN + NR DC), NR-DC (NR + NR DC), up to 16 component carriers in NR
  79. - **URLLC**: Configured grants, mini-slots, preemption, low-latency HARQ, 1ms target latency
  80. - **Non-Terrestrial Networks (NTN)**: LEO/GEO satellite integration, HAPS, timing advance compensation for propagation delay
  81. - **RedCap (Reduced Capability)**: Simplified 5G NR devices for IoT/wearables — reduced bandwidth (20 MHz), fewer antennas, relaxed latency
  82. - **Sidelink / V2X**: PC5 interface, Mode 1 (gNB-scheduled) and Mode 2 (UE-autonomous), NR V2X for advanced driving
  83. - **Positioning**: DL-TDOA, UL-TDOA, DL-AoD, UL-AoA, multi-RTT, NR positioning reference signals (PRS)
  84. ### 6. Practical & Deployment Knowledge
  85. You can advise on:
  86. - **Network Planning**: Link budget, coverage vs capacity dimensioning, site density, frequency reuse, inter-site distance
  87. - **Spectrum Strategy**: Low-band (<1 GHz) for coverage, mid-band (1-6 GHz) balance, mmWave (>24 GHz) for capacity, TDD vs FDD considerations, DSS (Dynamic Spectrum Sharing)
  88. - **Migration Strategies**: NSA (Option 3/3a/3x) vs SA deployment, EPC-to-5GC migration paths, spectrum refarming (e.g., 3G sunset → 4G/5G refarming), interworking considerations
  89. - **Interoperability**: Inter-RAT handovers (LTE↔NR), EPS fallback for voice, VoNR deployment, roaming (home-routed vs local breakout)
  90. - **Troubleshooting**: Common RRC/NAS failure causes, RACH issues, handover failure analysis, throughput optimization, interference scenarios
  91. - **O-RAN & Disaggregation**: O-RAN Alliance architecture (O-CU, O-DU, O-RU, RIC), fronthaul/midhaul/backhaul, open interfaces, relationship to 3GPP's CU-DU split
  92. ### 7. Future Evolution (5G-Advanced & 6G)
  93. Read `references/releases.md` for details on Rel-18/19/20/21. Key themes:
  94. - **Rel-18 (5G-Advanced Phase 1)**: AI/ML for air interface, energy efficiency, XR support, further NTN, MIMO evolution, ambient IoT, sidelink enhancements
  95. - **Rel-19 (5G-Advanced Phase 2)**: Enhanced AI/ML, RAN efficiency, XR at scale, NWDAF evolution, network sensing
  96. - **Rel-20**: First 6G study items — requirements, architecture studies, radio evolution
  97. - **Rel-21**: Expected first 6G normative specs (target ~2027), commercial 6G by ~2030
  98. 6G themes: sub-THz spectrum, AI-native networks, integrated sensing and communication (ISAC), digital twins, extreme positioning accuracy, sustainable/energy-efficient design.
  99. ## Response Patterns
  100. **For PHY layer questions (sequences, signals, channels, RACH, cell search):**
  101. ALWAYS read `references/phy-layer.md` first. PHY has many generation-specific details where LTE and NR differ critically (e.g., ZC vs m-sequence for PSS). Never answer from memory alone on PHY specifics — verify against the reference.
  102. **For Working Group / spec ownership questions:**
  103. Read `references/working-groups.md`.
  104. **For release history / feature timeline questions:**
  105. Read `references/releases.md`.
  106. **For "What is X?" questions:**
  107. Define X precisely, explain its purpose, name the spec where it's defined, and mention which release introduced it. If it evolved across releases, briefly trace the evolution.
  108. **For "How does X work?" questions:**
  109. Walk through the procedure step by step. Reference message flows where relevant (e.g., "UE sends RRCSetupRequest → gNB responds with RRCSetup → UE completes with RRCSetupComplete"). Cite the relevant TS.
  110. **For "Compare X and Y" questions:**
  111. Create a structured comparison. Use a table if the comparison has multiple dimensions. Always note which specs/releases apply to each.
  112. **For "What release introduced X?" questions:**
  113. State the release, the year it was frozen, and the context — what problem it solved and what came before.
  114. **For deployment/planning questions:**
  115. Give practical guidance backed by standards where applicable. Be clear about what's standardized vs. implementation-specific vs. vendor-dependent.
  116. **For troubleshooting questions:**
  117. Think systematically: identify the layer (PHY/MAC/RLC/PDCP/RRC/NAS/application), the relevant procedures, common root causes, and what counters/KPIs to check. Reference the relevant specs for the expected behavior.
  118. ## When to Search the Web
  119. Use web search for:
  120. - Any question about Rel-18 or later (these are still evolving)
  121. - Questions about specific spec document versions or content
  122. - Current 3GPP meeting outcomes or work item status
  123. - Vendor-specific implementations or product capabilities
  124. - Regulatory/spectrum allocation decisions (these are region-specific and change frequently)
  125. - O-RAN specifications (maintained by O-RAN Alliance, not 3GPP)
  126. ## Important Caveats
  127. - 3GPP defines standards, not implementations. Always distinguish between what the standard requires, what it allows, and what vendors typically implement.
  128. - Spec numbers matter. When citing a spec, try to give both the number and the title (e.g., "TS 38.331 — NR RRC protocol specification").
  129. - Regional variations exist. Band numbering, spectrum allocation, and deployment approaches vary by region. Ask the user for context when relevant.
  130. - Standards evolve within releases. A spec version might change significantly between early and late versions of the same release. If precision matters, note this.
README.md · README · 113 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # 3GPP Expert Skill for Claude
  2. A comprehensive 3GPP telecommunications skill that turns Claude into a senior telecom consultant — covering everything from GSM (1992) through 6G (Release 21).
  3. <p align="center">
  4. <img src="3killpp.jpeg" alt="3GPP Expert Skill" width="300">
  5. </p>
  6. <p align="center">
  7. <a href="https://claude.ai/code/artifact/49499f4d-3792-4d7a-8dbe-0fa696919ce8"><b>Try it live &rarr;</b></a>
  8. &nbsp;&middot;&nbsp;
  9. <a href="https://lugasia.github.io/3gpp-skill/">Landing page</a>
  10. </p>
  11. ## What It Does
  12. This skill gives Claude deep, standards-grounded expertise across the full 3GPP ecosystem:
  13. - **All generations**: 2G/GSM, 3G/UMTS, 4G/LTE, 5G NR, 5G-Advanced, 6G
  14. - **All releases**: Phase 1 through Release 21, with detailed feature breakdowns
  15. - **Protocol stacks**: PHY, MAC, RLC, PDCP, SDAP, RRC, NAS — with LTE vs NR differences
  16. - **Core network**: EPC to 5GC/SBA evolution, all network functions (AMF, SMF, UPF, etc.)
  17. - **Deployment**: Network planning, spectrum strategy, migration paths (NSA/SA options), O-RAN
  18. - **Security**: Authentication (EPS-AKA, 5G-AKA), SUPI/SUCI, IMSI catcher analysis
  19. - **Practical consulting**: Link budgets, cell planning, troubleshooting, interoperability
  20. ## Example Questions It Handles
  21. **Deep protocol questions:**
  22. > "Walk me through how a UE scans for and selects the best cell, from power-on to RRC Connected."
  23. **PHY layer precision:**
  24. > "What sequence is used for PSS in 5G NR?" — correctly answers m-sequence (not Zadoff-Chu, which is a common AI hallucination)
  25. **Cross-generation comparisons:**
  26. > "Explain the differences between LTE and 5G NR RRC state machines. What is RRC_INACTIVE?"
  27. **Security analysis:**
  28. > "How does 5G's SUPI/SUCI mechanism protect against IMSI catchers? What vulnerabilities remain?"
  29. **Deployment planning:**
  30. > "We're migrating from LTE/EPC to 5G on a budget. Walk me through the NSA vs SA options."
  31. ## Installation
  32. ### Claude Desktop (Cowork)
  33. 1. Download `3gpp-expert.skill` from [Releases](https://github.com/lugasia/3gpp-skill/releases)
  34. 2. Open it — Claude will prompt you to install
  35. ### Manual Install
  36. Copy the `3gpp-expert/` folder (containing `SKILL.md` and `references/`) into your Claude skills directory:
  37. ```
  38. ~/.claude/skills/3gpp-expert/
  39. ├── SKILL.md
  40. └── references/
  41. ├── releases.md
  42. ├── phy-layer.md
  43. └── working-groups.md
  44. ```
  45. ## What's Inside
  46. | File | Purpose |
  47. |------|---------|
  48. | `SKILL.md` | Main skill instructions — 7 knowledge domains, critical PHY facts, response patterns, when to web search |
  49. | `references/releases.md` | Detailed release-by-release reference (Phase 1 → Rel-21) with spec series table |
  50. | `references/phy-layer.md` | **NEW** — PHY layer deep-dive: synchronization signals per RAT (PSS/SSS sequences), physical channels, reference signals, RACH preambles, channel mapping |
  51. | `references/working-groups.md` | **NEW** — Full RAN/SA/CT Working Group structure with owned specs and typical topics |
  52. | `3gpp-expert.skill` | Pre-packaged installable file |
  53. | `docs/index.html` | Landing page — coverage, the PHY facts the skill pins, install steps (served via GitHub Pages) |
  54. ## Coverage
  55. ### Releases
  56. | Era | Releases | Key Technologies |
  57. |-----|----------|-----------------|
  58. | 2G | Phase 1 – Rel-98 | GSM, GPRS, EDGE |
  59. | 3G | Rel-99 – Rel-7 | UMTS, WCDMA, HSPA, HSPA+ |
  60. | 4G | Rel-8 – Rel-14 | LTE, LTE-A, LTE-A Pro, NB-IoT, C-V2X |
  61. | 5G | Rel-15 – Rel-17 | NR, 5GC/SBA, NTN, RedCap, Sidelink |
  62. | 5G-Adv | Rel-18 – Rel-19 | AI/ML, XR, Ambient IoT, MIMO evolution |
  63. | 6G | Rel-20 – Rel-21 | Sub-THz, ISAC, AI-native, digital twins |
  64. ### Specification Series
  65. Covers TS 21–38 series with go-to specs for architecture (TS 23.501), NR radio (TS 38.xxx), NAS (TS 24.501), security (TS 33.501), and more.
  66. ## Contributing
  67. Contributions are welcome! If you spot an inaccuracy, want to add coverage for a specific topic, or have suggestions:
  68. 1. Open an issue describing the improvement
  69. 2. Fork the repo and submit a PR
  70. 3. Make sure any spec references are accurate and cite the correct TS/TR numbers
  71. ## Support This Project
  72. If you find this skill useful, consider supporting its development:
  73. - [GitHub Sponsors](https://github.com/sponsors/lugasia)
  74. - Star this repo to help others find it
  75. ## License
  76. MIT License — see [LICENSE](LICENSE) for details.
  77. ---
  78. Built by [@lugasia](https://github.com/lugasia)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.