geo-infer-comms
Communication systems for geospatial coordination. Use when implementing spatial messaging, multi-channel notifications (email/SMS/push), event streaming, spatial message routing, or subscriber management for geographic broadcasts.
Best use case
geo-infer-comms is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Communication systems for geospatial coordination. Use when implementing spatial messaging, multi-channel notifications (email/SMS/push), event streaming, spatial message routing, or subscriber management for geographic broadcasts.
Teams using geo-infer-comms should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/GEO-INFER-COMMS/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How geo-infer-comms Compares
| Feature / Agent | geo-infer-comms | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Communication systems for geospatial coordination. Use when implementing spatial messaging, multi-channel notifications (email/SMS/push), event streaming, spatial message routing, or subscriber management for geographic broadcasts.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# GEO-INFER-COMMS
## Instructions
### Core Capabilities
- **Messaging**: Subscriber registry, spatial broadcast, geo-filtered delivery
- **Notifications**: Email, SMS, push channels (all functional — no placeholders)
- **Channels**: Multi-channel routing and priority management
- **Events**: Event streaming and spatial event processing
- **Spatial routing**: Location-aware message routing with coordinate bounds
- **Collaboration**: Real-time spatial collaboration tools
- **API security**: PyJWT primary, HMAC fallback for authentication
### Key Imports
```python
from geo_infer_comms.core.messaging import MessagingService
from geo_infer_comms.core.notifications import NotificationManager
from geo_infer_comms.core.channels import ChannelRouter
from geo_infer_comms.core.events import EventStream
from geo_infer_comms.core.spatial_routing import SpatialRouter
from geo_infer_comms.core.streaming import StreamProcessor
from geo_infer_comms.api.rest_api import CommsAPI
```
## Examples
```python
from geo_infer_comms.core.messaging import MessagingService
service = MessagingService()
service.register_subscriber("user_1", region_bounds=(-90, -180, 90, 180))
service.broadcast("Alert: flood detected", region="zone_a")
```
## Guidelines
- All 4 former placeholder blocks are resolved
- Auth uses PyJWT with HMAC fallback chain
- Test: `uv run python -m pytest GEO-INFER-COMMS/tests/ -v`
### Integrations
- **EMERGENCY** → Emergency notification broadcasting
- **IOT** → Sensor alert thresholds
- **PEP** → Stakeholder engagement notifications
- **CIV** → Community geographic broadcasts
- **OPS** → System alert delivery