zbofrvo/common-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

init: common-skills v1

Browse Source
This commit is contained in:
Team
2026-03-26 21:00:51 +08:00
commit 264dacf157
16 changed files with 859 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/docs-rag/SKILL.md
+78
View File
@@ -0,0 +1,78 @@
---
name: docs-rag
description: >
3GPP technical specification document retrieval and index management. Use when
the user asks about 3GPP specs, Release 19 features, mission critical services,
ambient IoT, ISAC, UAV/drone support, network sharing, SNPN interconnect,
traffic steering/split, or any question answered by the local docs/ directory.
Also use when the user wants to update, rebuild, or refresh the docs index,
or when new documents have been added to the docs/ directory.
---
# 3GPP Docs RAG Skill
Lightweight retrieval-augmented generation over the local `docs/` directory of
3GPP Release 19 specifications and study reports.
## Directory Layout
```
.kiro/skills/docs-rag/
├── SKILL.md ← this file
├── data/
│ └── index.json ← document index (spec, title, keywords, summary, file path)
└── evals/
└── evals.json ← evaluation cases
scripts/
└── build_index.py ← index builder / updater
```
## Maintaining the Index
**Full rebuild** (after adding many new docs):
```bash
python scripts/build_index.py
```
**Incremental update** (add new docs or refresh changed ones):
```bash
python scripts/build_index.py --update
```
The script scans `docs/` for `.docx` / `.doc` files, extracts the scope section
and header metadata, and writes `data/index.json`. Unchanged files (same mtime)
are skipped in `--update` mode.
## How to Answer Queries
1. Read `.kiro/skills/docs-rag/data/index.json`.
2. Match the user's query against `keywords` and `summary` fields.
3. If the summary is sufficient, answer directly from it.
4. If deeper detail is needed, read the actual file at the `file` path.
## Document Index Summary
| Spec | Title | Key Topics |
|------|-------|------------|
| TS 22.280 | Mission Critical Services Common Requirements | MCPTT, MCData, MCVideo, public safety |
| TS 22.369 | Service Requirements for Ambient IoT | battery-less IoT, energy harvesting |
| TR 22.837 | Integrated Sensing and Communication (ISAC) | NR sensing, V2X, UAV, smart city |
| TR 22.840 | Study on Ambient Power-enabled IoT | ambient IoT, 5G service requirements |
| TR 22.841 | Traffic Steer/Switch/Split over Dual 3GPP Access | multi-access, PLMN, satellite NR |
| TR 22.843 | UAV Phase 3 | drone, flight management, UTM, QoS |
| TR 22.848 | Interconnect of SNPN | private network, SNPN, PLMN interconnect |
| TR 22.851 | Network Sharing Feasibility Study | NG-RAN sharing, mobility, charging |
## Retrieval Rules
- **Keyword match**: scan `keywords` array for overlap with user query terms.
- **Semantic match**: if no keyword hit, check `summary` for conceptual relevance.
- **Multi-doc**: return all relevant docs when the query spans multiple topics.
- **No match**: say so clearly rather than hallucinating.
## Answer Format
Always cite the spec number and version:
> According to **3GPP TR 22.843 V19.2.0**, the 5G system supports UAV flight path
> recommendation and inflight monitoring based on network QoS information.
skills/docs-rag/data/index.json
+171
View File
@@ -0,0 +1,171 @@
{
"description": "3GPP technical specifications and study reports index",
"documents": [
{
"id": "22280-j50",
"file": "docs/22280-j50/22280-j50.doc",
"spec": "3GPP TS 22.280 V19.5.0",
"type": "Technical Specification",
"title": "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Mission Critical Services Common Requirements (MCCoRe); Stage 1 (Release 19)",
"release": "Release 19",
"keywords": [
"MCPTT",
"MCData",
"MCVideo",
"mission critical",
"public safety",
"maritime"
],
"summary": "The present document provides the service requirements that are common across two or more mission critical services, that is MCPTT, MCData and MCVideo. The mission critical services make use of capabilities included in Group Communications System Enablers and Proximity Services, with additional requirements specific to the MCPTT Service as specified in 3GPP TS 22.179 [1], MCVideo Service as specified in 3GPP TS 22.281 [2], and MCData Service as specified in 3GPP TS 22.282 [3]. The mission critical services can be used for public safety applications and maritime safety applications and also for",
"_mtime": 1774526763.1365554
},
{
"id": "22369-j20",
"file": "docs/22369-j20/22369-j20.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"ambient IoT",
"energy harvesting",
"battery-less",
"ambient power",
"IoT"
],
"summary": "The present document describes service and performance requirements for ambient power-enabled Internet of Things (i.e. Ambient IoT) . In the context of the present document, Ambient IoT device is an IoT device powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g. using a capacitor) and the energy is provided through the harvesting of radio waves, light, motion, heat, or any other power source that could be seen suitable. An A mbient IoT device has low complexity, small size and lower capabilities and lower power consumption than previously defi",
"_mtime": 1774526763.4285553
},
{
"id": "22837-j40",
"file": "docs/22837-j40/22837-j40.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"sensing",
"V2X",
"UAV",
"smart city",
"smart home",
"healthcare",
"maritime",
"NR",
"E-UTRA",
"5G"
],
"summary": "The present document describes use cases and potential requirements for enhancement of the 5G system to provide sensing services addressing different target verticals/applications, e.g. autonomous/assisted driving, V2X, UAVs, 3D map reconstruction, smart city, smart home, factories, healthcare, maritime sector. Use cases focus on NR-based sensing, while some use cases might make use of information already available in EPC and E-UTRA (e.g. cell/UE measurements, location updates). This study will not lead to impacts on EPC and E-UTRA. Some use cases could also include non-3GPP type sensors (e.g.",
"_mtime": 1774526764.1485553
},
{
"id": "22840-j00",
"file": "docs/22840-j00/22840-j00.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"ambient IoT",
"energy harvesting",
"battery-less",
"ambient power",
"5G",
"IoT"
],
"summary": "The present document provides Stage 1 potential 5G service requirements for ambient power-enabled Internet of Things (i.e., Ambient IoT). In the context of the present document, an Ambient power-enabled IoT device is an IoT device powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g., using a capacitor) and the energy is provided through the harvesting of radio waves, light, motion, heat, or any other suitable power source. An ambient IoT device is expected to have low er complexity, small er size and reduced capabilities and lower power consum",
"_mtime": 1774526766.1005547
},
{
"id": "22841-j00",
"file": "docs/22841-j00/22841-j00.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"PLMN",
"NPN",
"satellite",
"GEO",
"MEO",
"LEO",
"NR",
"E-UTRA",
"5G",
"5GS"
],
"summary": "The scope of this TR is to document use cases, gap analysis and potential service requirements related to 5GS support of enhanced mechanisms for steering, split ting and switch ing of user data , pertaining to a UE data session, across two 3GPP networks. The following scenarios are covered, where only one single PLMN subscription is assumed : Single PLMN; PLMN and NPN ; two PLMNs. The two 3GPP networks may use same or different RAT, i.e. NR plus NR or E-UTRA, where NR RAT can be terrestrial or satellite NR access (including different staellite orbits, e.g., GEO/MEO/LEO). For the PLMN plus PLMN",
"_mtime": 1774526766.9005547
},
{
"id": "22843-j20",
"file": "docs/22843-j20/22843-j20.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"UAV",
"5G",
"QoS",
"security"
],
"summary": "The present document provides additional use cases of UAV and identifies potential requirements to improve 5G system’s support of UAV applications, UAV operations and management, including: Provide additional information to the UAV operator/USS to execute pre-flight preparations and inflight operation (e.g, flight mission application, flight path recommendation, flight monitoring and control); Use 5G system to support enhancing the UAV flight/route management based on network capacity and QoS information along the planned route; Use 5G system to further enhance the safety and security of UAV o",
"_mtime": 1774526761.9005556
},
{
"id": "22848-j00",
"file": "docs/22848-j00/22848-j00.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"PLMN",
"NPN",
"SNPN",
"interconnect"
],
"summary": "The present document describes use cases and aspec t s rela t ed t o interconnect of SNPNs as well as Scalable SNPN Interconnect with dynamic connections . Potential service requirements are derived for these use cases and are consolidated in a dedicated chapter. The report ends with recommendations regarding the continuation of the work. NOTE: T here is no requirement for a PLMN to enhance their interconnect with SNPNs or operate an identity provider.",
"_mtime": 1774526762.3485556
},
{
"id": "22851-j10",
"file": "docs/22851-j10/22851-j10.docx",
"spec": "",
"type": "",
"title": "",
"release": "Release 1",
"keywords": [
"interconnect",
"network sharing",
"NG-RAN",
"mobility",
"charging",
"5G",
"security"
],
"summary": "The present document investigates use cases and potential new requirements related to 3GPP system enhanced support of specific 5G network sharing deployment scenarios , in particular where there is no direct interconnection between the shared NG-RAN and participating operators’ core networks. It includes the following aspects: - Mobility and service continuity, e.g., when moving from a non-shared 4G/5G network to a shared 5G network and vice versa, with focus on CN aspects. - Potential security requirements. - Charging requirements (e.g. , based on traffic differentiation in specific network s",
"_mtime": 1774526762.6245556
},
{
"id": "22890-j00",
"file": "docs/22890-j00/22890-j00.doc",
"spec": "3GPP TR 22.890 V19.0.0",
"type": "Technical Report",
"title": "Study on Supporting of Railway Smart Station Services",
"release": "Release 19",
"keywords": [
"railway",
"smart station",
"station monitoring",
"passenger services",
"railway IoT",
"5G railway"
],
"summary": "The present document analyses use cases of smart railway station such as station operation monitoring and control, passenger supporting services and evolution use cases of business and performance applications currently included in TR22.989 in order to derive potential requirements.",
"_mtime": 1774528383.0923867
}
]
}
skills/docs-rag/evals/evals.json
+30
View File
@@ -0,0 +1,30 @@
{
"skill_name": "docs-rag",
"evals": [
{
"id": 1,
"prompt": "What are the 3GPP Release 19 requirements for UAV flight path management?",
"expected_output": "References TR 22.843 and describes 5G system support for UAV flight path recommendation, inflight monitoring/control, and route management based on network capacity and QoS."
},
{
"id": 2,
"prompt": "What is Ambient IoT and what specs cover it?",
"expected_output": "Identifies TS 22.369 and TR 22.840 as the relevant specs. Explains that Ambient IoT devices are battery-less or limited-energy-storage IoT devices powered by energy harvesting (radio waves, light, motion, heat)."
},
{
"id": 3,
"prompt": "Which 3GPP spec covers ISAC — Integrated Sensing and Communication?",
"expected_output": "Identifies TR 22.837 V19.4.0 and describes its scope: use cases and requirements for 5G sensing services targeting autonomous driving, V2X, UAVs, smart city, healthcare, and maritime sectors."
},
{
"id": 4,
"prompt": "What does 3GPP say about SNPN interconnect with PLMNs?",
"expected_output": "References TR 22.848 and explains it covers SNPN interconnect use cases and scalable SNPN interconnect with dynamic connections, noting PLMNs are not required to enhance interconnect with SNPNs."
},
{
"id": 5,
"prompt": "What are the mission critical service requirements in Release 19?",
"expected_output": "References TS 22.280 V19.5.0 and describes common requirements for MCPTT, MCData, and MCVideo, covering public safety, group communications, proximity services, and commercial applications."
}
]
}