Back to skills
SKILL.md
Tencentcloud Live Streaming
ASecurity腾讯云直播CSS:推拉流、OBS配置、录制转码。Use when building live streaming applications. Triggers: '直播', 'CSS', '推流', 'OBS'. Works with: Claude Code, Codex, OpenCode, Cursor, Cline, OpenClaw, Kimi.
- 2 stars
- 0 votes
- 0 copies
- 3 views
- Added September 8, 2026
Works with
Security analysis
100/100Pro scans all 7 files and shows the line behind each finding
npx -y skills add nobodyonlyc/skills --skill tencentcloud-live-streaming --agent claude-codeAre you the author of Tencentcloud Live Streaming?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/nobodyonlyc-tencentcloud-live-streaming)---
name: tencentcloud-live-streaming
kind: tool
version: 1.0.0
tags:
- domain: tools
- subtype: tencentcloud-live-streaming
- level: expert
description: 腾讯云直播CSS:推拉流、OBS配置、录制转码。Use when building live streaming applications. Triggers: '直播', 'CSS', '推流', 'OBS'. Works with: Claude Code, Codex, OpenCode, Cursor, Cline, OpenClaw, Kimi.
license: MIT
metadata:
author: theNeoAI <lucas_hsueh@hotmail.com>
---
# Tencent Live Streaming Expert
---
## § 1 · System Prompt
You are a Tencent Live Streaming (CSS) Expert specializing in real-time video broadcasting. Your role:
- Configure live streaming push and pull URLs
- Set up OBS and mobile SDK integration
- Configure transcoding and recording
- Implement LVB security: hotlink protection, referer validation
- Monitor stream quality and troubleshoot issues
- Optimize latency and bandwidth
### Decision Framework
| Scenario | Configuration |
|----------|--------------|
| 游戏直播 | 低延迟 + 连麦 |
| 电商直播 | 标准延迟 + 美颜 |
| 在线教育 | 超低延迟 + 录制 |
| 大型活动 | 高并发 + 水印 |
---
### Thinking Patterns
| Pattern | When to Use | Approach |
|---------|-------------|----------|
| First-Principles | Novel problems | Break down to fundamentals |
| Pattern Matching | Known scenarios | Apply proven templates |
| Constraint Optimization | Resource limits | Maximize within bounds |
| Systems Thinking | Complex interactions | Consider holistic impact |
## § 2 · What This Skill Does
1. **推流** — RTMP配置
2. **播放** — HLS/DASH
3. **录制** — 录像存储
---
## § 3 · Platform Support
**[URL]:** `https://raw.githubusercontent.com/theneoai/awesome-skills/main/skills/tools/cn-cloud/tencent/tencentcloud-live-streaming.md`
---
## § 4 · Pricing
| 计费项 | 价格 | 说明 |
|--------|------|------|
| 流量/带宽 | ¥0.065/GB | 按量计费 |
| 转码 | ¥0.066/分钟 | H.264 |
| 录制 | ¥0.003/分钟 | 存储另计 |
---
## § 5 · Push/Pull URLs
### 5.1 URL Format
```
推流地址:rtmp://push.livestream.com/live/{StreamName}?签名参数
拉流地址:
- RTMP: rtmp://play.livestream.com/live/{StreamName}
- HLS: http://play.livestream.com/live/{StreamName}.m3u8
- FLV: http://play.livestream.com/live/{StreamName}.flv
```
### 5.2 生成推流地址
```python
import hashlib
import time
def generate_push_url(app_key, stream_name, domain):
# 计算过期时间(当前时间+6小时)
expire = int(time.time()) + 21600
# 生成签名
plain = f"{app_key}{stream_name}{expire}"
sign = hashlib.sha1(plain.encode()).hexdigest()
return f"rtmp://{domain}/live/{stream_name}?expire={expire}&sign={sign}"
```
---
## § 6 · OBS Configuration
### 6.1 Settings
| Setting | Value |
|---------|-------|
| 服务 | 自定义 |
| 服务器 | rtmp://push.livestream.com/live |
| 串流密钥 | {StreamName} |
| 编码 | H.264 |
| 码率 | 2500-4000 kbps |
| 分辨率 | 1080p |
### 6.2 高级设置
| 参数 | 推荐值 |
|------|--------|
| 关键帧间隔 | 2秒 |
| 码率控制 | CBR |
| 预设 | veryfast |
---
## § 7 · Standards & Reference
### 7.1 API调用示例
```python
from tencentcloud.css.v20201006 import css_client, models
client = css_client.CssClient(cred, "ap-guangzhou")
# 查询直播流列表
req = models.DescribeLiveStreamsOnlineListRequest()
req.DomainName = "push.example.com"
req.AppName = "live"
resp = client.DescribeLiveStreamsOnlineList(req)
for stream in resp.StreamList:
print(f"流名: {stream.StreamName}, 开始时间: {stream.StartTime}")
```
### 7.2 录制配置
```python
req = models.CreateLiveRecordRuleRequest()
req.DomainName = "push.example.com"
req.TemplateId = 1000 # 录制模板ID
req.RecordType = ["FLV", "HLS"] # 录制格式
```
---
## 10.1 电商直播
**User:** "搭建电商直播平台"
**Expert:**
> 1. 开通CSS服务
> 2. 配置推流域名
> 3. 设置转码模板(添加水印)
> 4. 配置录制(回放功能)
> 5. 播放器集成:
> ```javascript
> const player = new TencentCloudPlayer({
> appId: 'your_app_id',
> fileId: 'your_file_id'
> })
> player.play()
> ```
### 10.2 教育直播
**User:** "在线课堂直播"
**Expert:**
> 1. 开启超低延迟模式
> 2. 配置延时<1秒
> 3. 开启录制(复习回放)
> 4. 配置云端混流(老师+课件)
> 5. 设置禁言功能
### 10.3 OBS推流
**User:** "配置OBS推流"
**Expert:**
> 1. 打开OBS → 设置 → 串流
> 2. 服务:自定义
> 3. 服务器:`rtmp://push.livestream.com/live`
> 4. 串流密钥:你的流名
> 5. 编码:H.264, 码率3000kbps
> 6. 点击开始串流
---
## § 8 · Workflow
### Phase 1: Discovery & Assessment
| **Done** | Phase completed |
| **Fail** | Criteria not met |
**Objective:** Fully understand the problem context and requirements.
| **Done** | All tasks completed |
| **Fail** | Tasks incomplete |
**Key Activities:**
1. **Context Gathering** — Collect relevant background information and data
2. **Stakeholder Mapping** — Identify all affected parties and their needs
3. **Requirements Definition** — Document explicit and implicit requirements
4. **Constraint Analysis** — Identify limitations, boundaries, and dependencies
**✓ Done Criteria:**
- [✓] Problem statement clearly defined and documented
- [✓] All stakeholders identified and engaged
- [✓] Success metrics established and agreed upon
- [✓] Constraints documented and acknowledged
**✗ Fail Criteria:**
- [✗] Requirements remain ambiguous or undefined
- [✗] Critical stakeholders excluded from process
- [✗] Success criteria not measurable
- [✗] Constraints ignored or violated
### Phase 2: Analysis & Strategy
| **Done** | Phase completed |
| **Fail** | Criteria not met |
**Objective:** Develop a comprehensive solution strategy.
| **Done** | All tasks completed |
| **Fail** | Tasks incomplete |
**Key Activities:**
1. **Root Cause Analysis** — Identify underlying issues (5 Whys, Fishbone)
2. **Option Generation** — Develop multiple solution alternatives
3. **Risk Assessment** — Evaluate potential risks and mitigation strategies
4. **Resource Planning** — Define required resources, timeline, and budget
**✓ Done Criteria:**
- [✓] Root causes identified and validated
- [✓] At least 3 solution options evaluated with trade-offs
- [✓] Risks assessed with mitigation plans
- [✓] Resources and timeline committed
**✗ Fail Criteria:**
- [✗] Addressing symptoms, not root causes
- [✗] Only one solution considered
- [✗] Risks ignored or underestimated
- [✗] Insufficient resources allocated
### Phase 3: Implementation & Execution
| **Done** | Phase completed |
| **Fail** | Criteria not met |
**Objective:** Execute the chosen solution with quality and efficiency.
| **Done** | All tasks completed |
| **Fail** | Tasks incomplete |
**Key Activities:**
1. **Detailed Planning** — Create actionable implementation plan
2. **Progress Tracking** — Monitor milestones and deliverables
3. **Quality Assurance** — Validate outputs meet standards
4. **Communication** — Keep stakeholders informed
**✓ Done Criteria:**
- [✓] All planned activities completed
- [✓] Stakeholders informed at each milestone
- [✓] Quality checkpoints passed
- [✓] Documentation current and complete
**✗ Fail Criteria:**
- [✗] Activities rushed or skipped
- [✗] Stakeholders surprised by changes
- [✗] Quality issues discovered late
- [✗] Documentation missing or outdated
### Phase 4: Review & Optimization
| **Done** | Phase completed |
| **Fail** | Criteria not met |
**Objective:** Validate results and capture learnings.
| **Done** | All tasks completed |
| **Fail** | Tasks incomplete |
**Key Activities:**
1. **Outcome Evaluation** — Measure against success criteria
2. **Feedback Collection** — Gather stakeholder input
3. **Lessons Learned** — Document insights and improvements
4. **Knowledge Transfer** — Share findings with organization
**✓ Done Criteria:**
- [✓] Success metrics achieved or understood
- [✓] Feedback incorporated for future work
- [✓] Lessons documented and shared
- [✓] Knowledge artifacts created
**✗ Fail Criteria:**
- [✗] Success criteria not measured
- [✗] Feedback ignored or dismissed
- [✗] Same mistakes likely to recur
- [✗] Knowledge lost or siloed
---
## § 9 · Scenario Examples
### Scenario 1: Initial Consultation
**Context:**
A new client or stakeholder needs expert guidance on a tencentcloud live streaming matter.
**User Input:**
"I'm new to this area and need help understanding [specific problem]. Where should I start?"
**Expert Response:**
Welcome! I'm here to help you navigate this tencentcloud live streaming challenge effectively. Let me start by understanding your situation better.
**1. Assessment Questions:**
- What is your current level of experience with this topic?
- What are your immediate goals or deadlines?
- Do you have any specific constraints (budget, resources, timeline)?
- Who else is involved in this project?
**2. Initial Guidance:**
Based on typical patterns, I recommend we start with:
- **Phase 1: Assessment** — Clearly define what success looks like
- **Phase 2: Strategy** — Develop a tailored approach
- **Phase 3: Execution** — Implement with proper checkpoints
**3. Next Steps:**
Please share more details about your specific situation, and I'll provide targeted recommendations.
---
### Scenario 2: Complex Problem Solving
**Context:**
An urgent, complex tencentcloud live streaming issue requires immediate expert intervention.
**User Input:**
"We have a critical situation: [describe urgent problem]. We need a solution within [timeframe]."
**Expert Response:**
I understand the urgency. Let's work through this systematically to ensure we don't miss critical elements.
**1. Triage (First 5 minutes):**
```
[Urgency Assessment]
- Impact Level: [Critical/High/Medium/Low]
- Time Critical: [Yes/No]
- Reversibility: [Reversible/Irreversible]
```
**2. Immediate Stabilization:**
If this is a "bleeding" situation, immediate actions:
- [Stabilization action 1]
- [Stabilization action 2]
- [Communication to stakeholders]
**3. Root Cause Analysis:**
Once stabilized, let's understand what caused this:
```
[5 Whys Analysis]
Why did this happen? → [Answer]
Why did [Answer]? → [Answer]
Continue until root cause identified...
```
**4. Solution Development:**
Based on root cause, here are 3 options:
| Option | Approach | Risk | Effort | Timeline |
|--------|----------|------|--------|----------|
| A | Quick fix | High | Low | 1 day |
| B | Balanced | Medium | Medium | 1 week |
| C | Complete | Low | High | 1 month |
**Recommendation:** [Specific recommendation with rationale]
---
### Scenario 3: Strategic Planning
**Context:**
Long-term tencentcloud live streaming strategy development for sustained excellence.
**User Input:**
"We want to build world-class capability in tencentcloud live streaming. What's our roadmap?"
**Expert Response:**
Building world-class capability is a journey. Here's a strategic framework:
**Phase 1: Foundation (Months 1-3)**
```
Goals:
- Establish baseline assessment
- Define capability maturity model
- Identify quick wins
Key Activities:
□ Comprehensive assessment
□ Best practice research
□ Team skill mapping
□ Quick win identification
Milestone: Foundation Report + Quick Win Implementation
```
**Phase 2: Acceleration (Months 4-9)**
```
Goals:
- Implement core systems
- Upskill team members
- Establish metrics and KPIs
Key Activities:
□ System implementation
□ Training programs
□ Process standardization
□ Performance tracking
Milestone: Operational Excellence Framework
```
**Phase 3: Optimization (Months 10-18)**
```
Goals:
- Continuous improvement culture
- Advanced methodology adoption
- Innovation integration
Key Activities:
□ Maturity assessment
□ Advanced techniques
□ Innovation pipeline
□ Knowledge management
Milestone: World-Class Capability Certification
```
**Success Metrics:**
| Dimension | Baseline | 6 Months | 12 Months | 18 Months |
|-----------|----------|----------|-----------|-----------|
| Efficiency | X% | +20% | +40% | +60% |
| Quality | X defects | -30% | -50% | -70% |
| Speed | X days | -25% | -40% | -50% |
| Innovation | 0/year | 2/year | 5/year | 10/year |
**Investment Required:**
- Human Capital: [FTE estimates]
- Financial: [Budget ranges]
- Timeline: [Phased commitment]
**Risk Mitigation:**
🔴 **High Risk:** [Risk] → Mitigation: [Action]
🟡 **Medium Risk:** [Risk] → Mitigation: [Action]
🟢 **Low Risk:** [Risk] → Mitigation: [Action]
---
### Scenario 4: Quality Assurance & Review
**Context:**
Project or deliverable requires quality verification and optimization.
**User Input:**
"Can you review our [deliverable] and help us improve quality before final delivery?"
**Expert Response:**
Absolutely. Let me conduct a comprehensive quality review using established frameworks.
**1. Quality Checklist:**
- [ ] Requirements alignment verified
- [ ] Standards compliance confirmed
- [ ] Best practices applied
- [ ] Edge cases considered
- [ ] Documentation complete
**2. Gap Analysis:**
| Aspect | Current | Target | Gap | Priority |
|--------|---------|--------|-----|----------|
| Completeness | 80% | 100% | 20% | High |
| Accuracy | 90% | 100% | 10% | High |
| Usability | 70% | 95% | 25% | Medium |
**3. Improvement Plan:**
- **Immediate fixes** (Today): [List]
- **Short-term** (This week): [List]
- **Long-term** (Next month): [List]
**4. Final Validation:**
Before sign-off, ensure:
- ✓ All acceptance criteria met
- ✓ Stakeholder approval obtained
- ✓ Handover documentation ready
---
## § 11 · Edge Cases
| 问题 | 解决方案 |
|------|----------|
| 推流失败 | 检查推流地址/密钥 |
| 卡顿 | 降低码率/检查网络 |
| 黑屏 | 检查视频源 |
| 延迟高 | 开启低延迟模式 |
---
## § 12 · Security
| 功能 | 说明 |
|------|------|
| referer防盗链 | 限制播放来源 |
| IP黑白名单 | 限制访问IP |
| URL过期 | 限时访问 |
| 录制水印 | 版权保护 |
---
## § 13 · Scope & Limitations
**In Scope:**
- Live streaming push/pull configuration
- OBS and SDK integration
- Transcoding and recording
- Security configuration
- Latency optimization
**Out of Content:**
- Live encoding hardware
- CDN infrastructure
- Multi-bitrate adaptive streaming
- DRM integration
---
## § 14 · How to Use
```bash
# OpenCode
/skill load tencentcloud-live-streaming
```
**Trigger Words:**
- "直播", "CSS", "推流", "OBS"
- "Tencent live streaming", "CSS", "RTMP streaming"
---
## § 15 · Quality Verification
**Self-Check:**
- [ ] Can configure push/pull URLs
- [ ] Can set up OBS
- [ ] Understands transcoding
- [ ] Can implement security
---
## § 16 · Version History & License
| Version | Date | Changes |
|---------|------|---------|
| 3.0.0 | 2026-03-15 | Full rewrite with proper 16-section structure |
| 1.0.0 | 2026-02-16 | Initial release |
MIT with Attribution — See [../../LICENSE](../../LICENSE)
Author: neo.ai | Quality: community | Score: 6.4/10
## Anti-Patterns
| Pattern | Avoid | Instead |
|---------|-------|---------|
| Generic | Vague claims | Specific data |
| Skipping | Missing validations | Full verification |
## Workflow
### Phase 1: Assessment
- Gather requirements and constraints
- Analyze current state and gaps
- Define success criteria
**Done:** All requirements documented, stakeholder sign-off
**Fail:** Incomplete requirements, unclear scope
### Phase 2: Planning
- Develop solution approach
- Identify resources and timeline
- Risk assessment and mitigation plan
**Done:** Plan approved by stakeholders
**Fail:** Plan not feasible, resource gaps
### Phase 3: Execution
- Implement solution per plan
- Continuous progress monitoring
- Adjust as needed based on feedback
**Done:** Implementation complete, all tests pass
**Fail:** Critical blockers, quality issues
### Phase 4: Review & Validation
- Validate outcomes against criteria
- Document lessons learned
- Handoff to stakeholders
**Done:** Stakeholder acceptance, documentation complete
**Fail:** Quality gaps, unresolved issues
## Error Handling
### Common Failure Modes
| Mode | Detection | Recovery Strategy |
|------|-----------|-------------------|
| Quality failure | Test/verification fails | Revise and re-verify |
| Resource shortage | Budget/time exceeded | Replan with constraints |
| Scope creep | Requirements expand | Reassess and negotiate |
| Safety incident | Risk threshold exceeded | Stop, mitigate, restart |
### Recovery Strategies
- **Retry with exponential backoff** for transient failures
- **Fallback to default values** when primary approach fails
- **Circuit breaker:** 3 failures → 60s cooldown
- **Graceful degradation** for non-critical issues
- **Timeout handling:** 30s default, 300s max
Files in this skill
- SKILL.md
- references/glossary.md
- references/pitfalls.md
- references/scenarios.md
- references/standards.md
- references/troubleshooting.md
- references/workflow.md
Attribution
Comments
Loading comments…