dcs-srs
Provides gRPC methods for managing DCS Simple Radio Standalone (SRS) clients and transmitting synthesized audio.
Install
mkdir -p .claude/skills/dcs-srs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10781" && unzip -o skill.zip -d .claude/skills/dcs-srs && rm skill.zipInstalls to .claude/skills/dcs-srs
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Invoke DCS SRS (Simple Radio Standalone) gRPC methods. Service for text-to-speech radio transmissions and client management. Proto: dcs-grpc-wrapper/proto/srs/v0/srs.protoKey capabilities
- →Transmit radio messages
- →Get SRS client list
- →Configure radio frequency
How it works
It interfaces with the DCS gRPC wrapper to execute radio transmission and client management methods via MCP.
Inputs & outputs
When to use dcs-srs
- →Transmit radio message
- →Get SRS clients list
- →Configure radio frequency
About this skill
dcs-srs Skill
Invoke DCS SRS (Simple Radio Standalone) service gRPC methods for radio transmissions and client management.
Prerequisites
- AppHost started:
aspire startoraspire start --isolated dcs-grpc-wrapperresource is live and healthy.withMcpServer({ path: "/mcp/dcs-grpc", endpointName: "dcs-grpc" })is configured inapphost.ts- SRS server running and connected
- Proper frequency and coalition settings for SRS server configuration
Available Methods
Radio Transmission
- Transmit - Synthesize text-to-speech and transmit on SRS frequency
Client Management
- GetClients - Get list of SRS clients and their active frequencies
Quick Examples
CRITICAL — Tool Invocation: NEVER use
aspire mcp callin the terminal to invoke gRPC methods. Always use the MCP tool directly:
- Load deferred tool:
tool_search_tool_regexwith patternmcp_dcs-grpc-wrap- Call:
mcp_dcs-grpc-wrap_call_grpc_methodwith the JSON payload below
Transmit radio message (English):
{"method": "Transmit", "payload": {"ssml": "Check six position, bandits at twelve o clock", "plaintext": "Check six position, bandits at twelve o clock", "frequency": 251000000, "coalition": "COALITION_BLUE", "position": {"lat": 40.0, "lon": 0.0, "alt": 5000}}}
Transmit with SSML (prosody control):
{"method": "Transmit", "payload": {"ssml": "<prosody rate=\"0.9\">Roger, low fuel state</prosody>", "plaintext": "Roger, low fuel state", "frequency": 251000000, "coalition": "COALITION_BLUE", "position": {"lat": 40.0, "lon": 0.0, "alt": 5000}}}
Async transmission (non-blocking):
{"method": "Transmit", "payload": {"ssml": "Contact visual", "frequency": 251000000, "async": true, "coalition": "COALITION_BLUE", "position": {"lat": 40.0, "lon": 0.0, "alt": 5000}}}
Get SRS clients:
{"method": "GetClients", "payload": {}}
Notes
- Blocking vs Async: By default, Transmit blocks until transmission completes. Use
async:truefor non-blocking calls - Frequencies: Use Hz format (e.g., 251000000 for 251.00 MHz)
- SSML Support: Use SSML tags for prosody control (rate, pitch, volume, etc.)
- Position: Required for line-of-sight and distance calculations
- Coalition: Only Blue and Red supported; others fallback to Spectator
References
When not to use it
- →Direct terminal invocation
Prerequisites
Limitations
- →Only Blue and Red coalitions supported
How it compares
It provides a structured tool-based interface for gRPC methods instead of manual terminal commands.
Compared to similar skills
dcs-srs side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| dcs-srs (this skill) | 0 | 4mo | No flags | Intermediate |
| telegram-bot-builder | 106 | 6mo | Review | Intermediate |
| mcp-integration | 21 | 8mo | Review | Intermediate |
| n8n-workflow-patterns | 16 | 2mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by deadl1f7
View all by deadl1f7 →You might also like
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
mcp-integration
anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
n8n-workflow-patterns
czlonkowski
Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.
n8n-code-javascript
czlonkowski
Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.
n8n-expression-syntax
czlonkowski
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.
n8n-node-configuration
czlonkowski
Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node_essentials and get_node_info, or learning common configuration patterns by node type.