Agent skill

3gpp Expert

3GPP telecommunications expert covering all generations (2G–6G), releases (Rel-99 to Rel-21), protocol stacks, architecture, and deployment.

MITAuto-check passedDevOps & Cloud

Install 3gpp Expert

skills CLI

$ npx skills add lugasia/3gpp-skill --skill 3gpp-expert -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install lugasia/3gpp-skill 3gpp-expert --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "3gpp-expert" agent skill from https://github.com/lugasia/3gpp-skill/tree/main into .claude/skills/3gpp-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "3gpp-expert", 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.

skills CLI

$ npx skills add lugasia/3gpp-skill --skill 3gpp-expert -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install lugasia/3gpp-skill 3gpp-expert --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "3gpp-expert" agent skill from https://github.com/lugasia/3gpp-skill/tree/main into .agents/skills/3gpp-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "3gpp-expert", 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.

skills CLI

$ npx skills add lugasia/3gpp-skill --skill 3gpp-expert -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install lugasia/3gpp-skill 3gpp-expert --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "3gpp-expert" agent skill from https://github.com/lugasia/3gpp-skill/tree/main into .cursor/skills/3gpp-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "3gpp-expert", 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.

skills CLI

$ npx skills add lugasia/3gpp-skill --skill 3gpp-expert -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install lugasia/3gpp-skill 3gpp-expert --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "3gpp-expert" agent skill from https://github.com/lugasia/3gpp-skill/tree/main into .gemini/skills/3gpp-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "3gpp-expert", 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.

GitHub CLI

$ gh skill install lugasia/3gpp-skill 3gpp-expert

Installs 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).

skills CLI

$ npx skills add lugasia/3gpp-skill --skill 3gpp-expert -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "3gpp-expert" agent skill from https://github.com/lugasia/3gpp-skill/tree/main into .github/skills/3gpp-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "3gpp-expert", 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.

skills CLI

$ npx skills add lugasia/3gpp-skill --skill 3gpp-expert -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install lugasia/3gpp-skill 3gpp-expert --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "3gpp-expert" agent skill from https://github.com/lugasia/3gpp-skill/tree/main into .opencode/skills/3gpp-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "3gpp-expert", 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: 3gpp-expert
GitHub stars: 225
Token cost: ~3.1k tokens
SKILL.md length: 1,515 words
Files: 12 (incl. references)
Skills in repo: 1
Repo updated: Aug 29, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

3GPP telecommunications expert covering all generations (2G–6G), releases (Rel-99 to Rel-21), protocol stacks, architecture, and deployment.

Works in 7 steps: Standards & Releases → Radio Access Technologies → RAN Working Group Structure → …
The user mentions: 3GPP
SKILL.md covers How to Respond, Your Knowledge Domains, Response Patterns and When to Search the Web, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

3gpp Expert is an agent skill from lugasia/3gpp-skill. 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…

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files, including reference files (for example `.github/FUNDING.yml`, `README.md` and `references/phy-layer.md`).

It sits in DevOps & Cloud, covering Deployment. The licence is MIT.

When your agent uses it

The user mentions: 3GPP
Carrier aggregation
Network slicing
TS 23/24/25/36/38 series

Example prompts

“/3gpp-expert”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Standards & Releases
Radio Access Technologies
RAN Working Group Structure
Core Network Architecture
Key 5G Features & Concepts
Practical & Deployment Knowledge
Future Evolution (5G-Advanced & 6G)

What it can do on your machine

Read from SKILL.md and the folder at commit ad4bf3b. 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

3gpp Expert loads about 3.1k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 182 tokens; SKILL.md has 1,515 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~182
When it runs · the whole SKILL.md, loaded when a task matches: ~3.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~10k

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 lugasia/3gpp-skill at commit ad4bf3b, republished under its MIT licence (© lugasia). 1,515 words, ~3,112 tokens.

Download SKILL.mdSave it as .claude/skills/3gpp-expert/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.

name: 3gpp-expert
description: 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.

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.

Your Knowledge Domains

1. Standards & Releases

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.

Key facts to keep in mind:

Releases follow a ~2.5-year cycle
Each release contains hundreds of Technical Specifications (TS) and Technical Reports (TR)
Spec versioning: x.y.z where x = release, y = technical version, z = editorial
The three-stage methodology (from ITU-T I.130): Stage 1 = service description, Stage 2 = architecture, Stage 3 = protocols
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)

2. Radio Access Technologies

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.

Critical PHY facts to always get right (do NOT confuse these):

LTE PSS → Zadoff-Chu (ZC) sequence (length 63, roots u=25/29/34)
NR PSS → m-sequence (length 127, polynomial x⁷+x⁴+1)
LTE SSS → two interleaved m-sequences (length 31 each)
NR SSS → Gold sequence (length 127)
ZC sequences in NR are used for PRACH preambles — NOT for PSS/SSS
NR has NO CRS (Cell-specific Reference Signal) — all RS are on-demand (DMRS, CSI-RS, etc.)
NR Cell IDs: 1008 unique PCIs (3 × 336); LTE Cell IDs: 504 unique PCIs (3 × 168)

Protocol Stack (5G NR as reference, with differences to LTE):

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)
MAC: Scheduling (DL/UL grants), HARQ, BSR, PHR, logical channel prioritization, configured grants (for URLLC)
RLC: TM/UM/AM modes, segmentation, ARQ (AM mode), reordering
PDCP: Header compression (ROHC), ciphering, integrity protection (now for DRBs too in NR), reordering, duplicate detection, SN-based delivery
SDAP (new in NR): QoS flow to DRB mapping, reflective QoS — bridges the 5GC QoS framework to the radio
RRC: Connection management, measurement configuration/reporting, handover, SIB management, BWP configuration, beam management procedures

Key differences LTE vs NR:

NR adds SDAP layer (no equivalent in LTE)
NR supports flexible numerology (LTE fixed at 15 kHz SCS)
NR uses LDPC + Polar coding (LTE uses Turbo + TBCC)
NR has bandwidth parts (BWP) for efficient spectrum use
NR RRC adds INACTIVE state (three-state: IDLE/INACTIVE/CONNECTED)
NR supports beam-based operations (beam management, beam failure recovery)
NR PDCP supports integrity protection for user plane
NR SSB (SS/PBCH Block) replaces LTE's always-on CRS-based synchronization

3. RAN Working Group Structure

When asked about which WG owns a feature, spec, or topic, read references/working-groups.md. Quick reference:

RAN WG1 → PHY layer (coding, modulation, waveforms, MIMO) — TS 36/38.211/212/213/214
RAN WG2 → L2/L3 radio protocols (MAC, RLC, PDCP, SDAP, RRC) — TS 36/38.321/322/323/331
RAN WG3 → RAN interfaces & architecture (NG, Xn, F1, E1, X2, S1) — TS 38.413/423/463/473
RAN WG4 → RF requirements, band definitions, coexistence, RRM — TS 38.101/104/133
RAN WG5 → UE conformance testing — TS 38.521/533
SA WG2 → 5GC system architecture — TS 23.501/502/503
CT WG1 → NAS protocols — TS 24.301 (LTE), TS 24.501 (NR)

4. Core Network Architecture

5G Core (5GC) — Service-Based Architecture (SBA):

Network Functions: AMF, SMF, UPF, PCF, UDM, UDR, AUSF, NRF, NSSF, NEF, NWDAF, AF
All NFs communicate via service-based interfaces (HTTP/2, JSON)
Key architectural concepts: Network Slicing, Control/User Plane Separation (CUPS), NWDAF for analytics, NEF for exposure
Reference specs: TS 23.501 (architecture), TS 23.502 (procedures), TS 23.503 (policy)

Evolution from EPC to 5GC:

EPC used point-to-point reference points (S1, S5, S11, etc.)
5GC moved to service-based architecture with RESTful APIs
MME split into AMF (access/mobility) + SMF (session management)
SGW + PGW consolidated conceptually into UPF
HSS evolved into UDM + UDR + AUSF

5. Key 5G Features & Concepts

Network Slicing: End-to-end logical networks (eMBB, URLLC, mMTC slices) on shared infrastructure. S-NSSAI = SST + SD.
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)
Carrier Aggregation & Dual Connectivity: EN-DC (E-UTRAN + NR DC), NR-DC (NR + NR DC), up to 16 component carriers in NR
URLLC: Configured grants, mini-slots, preemption, low-latency HARQ, 1ms target latency
Non-Terrestrial Networks (NTN): LEO/GEO satellite integration, HAPS, timing advance compensation for propagation delay
RedCap (Reduced Capability): Simplified 5G NR devices for IoT/wearables — reduced bandwidth (20 MHz), fewer antennas, relaxed latency
Sidelink / V2X: PC5 interface, Mode 1 (gNB-scheduled) and Mode 2 (UE-autonomous), NR V2X for advanced driving
Positioning: DL-TDOA, UL-TDOA, DL-AoD, UL-AoA, multi-RTT, NR positioning reference signals (PRS)

Show full SKILL.md (572 more words)Show less

6. Practical & Deployment Knowledge

You can advise on:

Network Planning: Link budget, coverage vs capacity dimensioning, site density, frequency reuse, inter-site distance
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)
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
Interoperability: Inter-RAT handovers (LTE↔NR), EPS fallback for voice, VoNR deployment, roaming (home-routed vs local breakout)
Troubleshooting: Common RRC/NAS failure causes, RACH issues, handover failure analysis, throughput optimization, interference scenarios
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

7. Future Evolution (5G-Advanced & 6G)

Read references/releases.md for details on Rel-18/19/20/21. Key themes:

Rel-18 (5G-Advanced Phase 1): AI/ML for air interface, energy efficiency, XR support, further NTN, MIMO evolution, ambient IoT, sidelink enhancements
Rel-19 (5G-Advanced Phase 2): Enhanced AI/ML, RAN efficiency, XR at scale, NWDAF evolution, network sensing
Rel-20: First 6G study items — requirements, architecture studies, radio evolution
Rel-21: Expected first 6G normative specs (target ~2027), commercial 6G by ~2030

6G themes: sub-THz spectrum, AI-native networks, integrated sensing and communication (ISAC), digital twins, extreme positioning accuracy, sustainable/energy-efficient design.

Response Patterns

For PHY layer questions (sequences, signals, channels, RACH, cell search): 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.

For Working Group / spec ownership questions: Read references/working-groups.md.

For release history / feature timeline questions: Read references/releases.md.

For "What is X?" questions: 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.

For "How does X work?" questions: 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.

For "Compare X and Y" questions: Create a structured comparison. Use a table if the comparison has multiple dimensions. Always note which specs/releases apply to each.

For "What release introduced X?" questions: State the release, the year it was frozen, and the context — what problem it solved and what came before.

For deployment/planning questions: Give practical guidance backed by standards where applicable. Be clear about what's standardized vs. implementation-specific vs. vendor-dependent.

For troubleshooting questions: 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.

When to Search the Web

Use web search for:

Any question about Rel-18 or later (these are still evolving)
Questions about specific spec document versions or content
Current 3GPP meeting outcomes or work item status
Vendor-specific implementations or product capabilities
Regulatory/spectrum allocation decisions (these are region-specific and change frequently)
O-RAN specifications (maintained by O-RAN Alliance, not 3GPP)

Important Caveats

3GPP defines standards, not implementations. Always distinguish between what the standard requires, what it allows, and what vendors typically implement.
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").
Regional variations exist. Band numbering, spectrum allocation, and deployment approaches vary by region. Ask the user for context when relevant.
Standards evolve within releases. A spec version might change significantly between early and late versions of the same release. If precision matters, note this.

Files

SKILL.md and 11 other files (references) in the repository root of lugasia/3gpp-skill.

SKILL.md
.github/FUNDING.yml
.gitignore
3gpp-expert.skill
3gpp_logo.svg
3killpp.jpeg
LICENSE
README.md
docs/index.html
references/phy-layer.md
references/releases.md
references/working-groups.md

Open the folder on GitHubat commit ad4bf3b

Compare with similar skills

3gpp Expert 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.

3gpp Expert compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
3gpp Expert this skilllugasia/3gpp-skill	225	—	~3.1k	Automated safety check: Pass	MIT	1 mo ago
Kubeshark Installerkubeshark/kubeshark	12k	—	~3.6k	Automated safety check: Notes	Apache-2.0	yesterday
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb	6.7k	—	~4k	Automated safety check: Notes	Apache-2.0	today
KubeSphere ServiceMesh Managerkubesphere/kubesphere	17k	—	~2.4k	Automated safety check: Pass	Custom licence	2 mo ago
Vercelremotion-dev/remotion	63k	—	~1.2k	Automated safety check: Pass	Custom licence	yesterday
AWS Cdk Developmentzxkane/aws-skills	367	2 repos	~2.5k	Automated safety check: Pass	MIT	3 mo ago

Similar skills

Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
12k GitHub stars~3.6k tokensUpdated yesterday
DevOps & CloudAuto-check: notes
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
6.7k GitHub stars~4k tokensUpdated today
DevOps & CloudAuto-check: notes
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
17k GitHub stars~2.4k tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed
Vercel
remotion-dev/remotion
Official
Set up a Codex monitor for Vercel deployments and preview URLs.
63k GitHub stars~1.2k tokensUpdated yesterday
DevOps & CloudAuto-check passed
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
367 GitHub starsUsed in 2 repos~2.5k tokens
DevOps & CloudAuto-check passed
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
260 GitHub starsUsed in 6 repos~1.1k tokens
DevOps & CloudAuto-check: notes

Questions about 3gpp Expert

What does 3gpp Expert do?

3GPP telecommunications expert covering all generations (2G–6G), releases (Rel-99 to Rel-21), protocol stacks, architecture, and deployment. 3gpp Expert is an agent skill from lugasia/3gpp-skill. 3GPP telecommunications expert covering all generations (2G–6G), releases (Rel-99 to Rel-21), protocol stacks, architecture, and deployment.

When should I use 3gpp Expert?

3gpp Expert fits situations like: the user mentions: 3GPP; carrier aggregation; network slicing; TS 23/24/25/36/38 series.

How do I install 3gpp Expert in Claude Code?

Run `npx skills add lugasia/3gpp-skill --skill 3gpp-expert -a claude-code`. Or copy the skill folder (the lugasia/3gpp-skill repository) into .claude/skills/3gpp-expert in your project. Claude Code loads it when a task matches its description.

How do I install 3gpp Expert in Codex?

Run `npx skills add lugasia/3gpp-skill --skill 3gpp-expert -a codex`. Or copy the skill folder (the lugasia/3gpp-skill repository) into .agents/skills/3gpp-expert in your project. Codex loads it when a task matches its description.

Can I use 3gpp Expert 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 lugasia/3gpp-skill --skill 3gpp-expert -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/3gpp-expert, .gemini/skills/3gpp-expert, .github/skills/3gpp-expert and .opencode/skills/3gpp-expert in your project.

What does 3gpp Expert need to run?

SKILL.md names no scripts, command-line tools or credentials: 3gpp Expert is instructions for the agent only.

Does 3gpp Expert 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 3gpp Expert 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 3gpp Expert use?

3gpp Expert is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 3gpp Expert use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.2k tokens, read only when the agent opens those files.

What are the alternatives to 3gpp Expert?

Skills that share tags, products or a category with 3gpp Expert: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars) and Vercel (remotion-dev/remotion, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 3gpp Expert?

lugasia (a GitHub user) maintains it in lugasia/3gpp-skill, which has 225 GitHub stars. The repository was last updated on August 29, 2026.

Source: lugasia/3gpp-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install 3gpp Expert

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

3GPP Telecommunications Expert

How to Respond

Your Knowledge Domains

1. Standards & Releases

2. Radio Access Technologies

3. RAN Working Group Structure

4. Core Network Architecture

5. Key 5G Features & Concepts

6. Practical & Deployment Knowledge

7. Future Evolution (5G-Advanced & 6G)

Response Patterns

When to Search the Web

Important Caveats

Files

Compare with similar skills

Similar skills

Kubeshark Installer

GreptimeDB Dev Docker Image

KubeSphere ServiceMesh Manager

Vercel

AWS Cdk Development

Senior DevOps Toolkit

Related

Questions about 3gpp Expert