Individual skill
3gpp-expert
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.
SKILL.md
Source commit ad4bf3bdb64993ffb08ef0022e504f0d68c0e084
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 227
- Repository last updated
- Aug 29, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
- devops Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
.github/FUNDING.ymlasset · 16 bytes.gitignoreasset · 7 bytes3gpp-expert.skillasset · 18,703 bytes3gpp_logo.svgasset · 6,152 bytes3killpp.jpegasset · 35,073 bytesLICENSEasset · 1,064 bytesREADME.mddoc · 4,419 bytesSKILL.mdcore · 12,526 bytesdocs/index.htmlasset · 229,305 bytesreferences/phy-layer.mddoc · 8,617 bytesreferences/releases.mddoc · 16,125 bytesreferences/working-groups.mddoc · 4,098 bytes
Read excerpt
# 3GPP Telecommunications Expert
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.
## How to Respond
**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.
**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.
**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.
**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.