Xpersona
I

Information Services

CLAWHUB · Unverified

Unified information services hub combining location, weather, and time capabilities. Multi-source geolocation (GPS/IP/WiFi), fixed-point weather forecasts, a... Skill: Information Services Owner: johnsmithfan Summary: Unified information services hub combining location, weather, and time capabilities. Multi-source geolocation (GPS/IP/WiFi), fixed-point weather forecasts, a... Tags: latest:1.0.0 Version history: v1.0.0 | 2026-04-26T17:27:17.176Z | user v3.0.0 major rebuild: department-aligned merge, English-only, SKILL.md index-only, method-patterns.md + prompts/ folder Archi

62
Rank
84
Safety
996
Downloads

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 996 downloads reported by the source. Last updated 10/11/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Install and run

Setup complexity: low.

clawhub skill install s17ar8yxm9wh64zhr7mr0xemcn84gs16:information-services
  1. Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
  2. Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-johnsmithfan-information-services/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

21,884 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: "Information Services"
slug: "information-services"
version: "1.0.0"
language: en
description: |
  Unified information services hub combining location, weather, and time capabilities.
  Multi-source geolocation (GPS/IP/WiFi), fixed-point weather forecasts, and multi-source
  time reporting with confidence scoring. Single entry point for all location-aware services.
license: MIT
triggers:
  - location
  - weather
  - time
  - GPS coordinates
  - forecast
  - current time
  - where am i
  - what time is it
  - weather forecast
interface:
  inputs:
    type: object
    schema:
      type: object
      properties:
        service:
          type: string
          enum: [location, weather, time, all]
          description: Which service to query
        location:
          type: string
          description: City name or coordinates (lat,lon)
        method:
          type: string
          description: Specific method (gps, system, ip, wifi, cellular)
  outputs:
    type: object
    schema:
      type: object
      properties:
        service_type:
          type: string
          description: location | weather | time
        data:
          type: object
          description: Service-specific result data
        confidence:
          type: number
          description: Confidence score 0-1
  errors:
    - code: LOC_UNAVAILABLE
      message: No location source available
    - code: WEATHER_FAILED
      message: Weather API request failed
    - code: TIME_FAILED
      message: Time source unavailable
    - code: NO_CREDENTIALS
      message: Required API credentials missing
quality:
  idempotent: true
metadata:
  category: information
  standardized: true
---

# Information Services v1.0.0

> Index & Quick Reference. Full specifications in [references/](references/).

## Quick Reference

### Role
Unified hub for location, weather, and time services. Routes requests to the appropriate subsystem based on service type.

### Department
Information

## Section Index

- [Location Service](references/location.md)
- [Weather Service](references/weather.md)
- [Time Service](references/time.md)
- [Coordination Logic](references/method-patterns.md#coordination)

## Services

| Service | Capabilities | Source Skills |
|---------|-------------|---------------|
| **Location** | GPS, system, IP, WiFi, cellular triangulation | multi-source-locate |
| **Weather** | Current conditions, forecast, multi-source fusion | locate-weather |
| **Time** | System clock, NTP, web API, confidence scoring | multi-source-time |

## Prompts

- [01-implement-method.md](prompts/01-implement-method.md)
- [02-robustness-checks.md](prompts/02-robustness-checks.md)
- [03-test-cases.md](prompts/03-test-cases.md)
- [04-documentation.md](prompts/04-documentation.md)
- [05-workflow-execution.md](prompts/05-workflow-execution.md)

---

*See [references/](references/) for detailed service specifications.*

_meta.json

{
  "ownerId": "kn7c9ynzajdkfj65cxt4wb6ysx82d4zh",
  "slug": "information-services",
  "version": "1.0.0",
  "publishedAt": 1777224437176
}

references/location.md

# Location Service — Detailed Specifications

> Part of information-services skill.

---

## 1. Supported Methods

| Method | Accuracy | Use Case | API Key Required |
|--------|----------|----------|-----------------|
| **GPS** | 3-10m | Outdoor, navigation | No |
| **System** | 10m–1km | Indoor/outdoor, OS-managed | No |
| **IP** | 1-50km | City-level, quick detection | No |
| **WiFi** | 10-100m | Indoor, urban environments | Optional |
| **Cellular** | 100m-3km | Rural, GPS-denied | Optional |
| **Triangulated** | Weighted centroid | Multi-method fusion | No |

## 2. Triangulation Algorithm

When multiple methods return results:
1. Collect coordinates from each successful method
2. Weight by inverse variance (accuracy-based weighting)
3. Compute weighted centroid as final position
4. Estimate combined accuracy from residual dispersion
5. Report confidence score (0–100%)

### Output Format
```json
{
  "latitude": 39.9042,
  "longitude": 116.4074,
  "accuracy_meters": 15,
  "confidence": 0.92,
  "method": "triangulated",
  "sources": {
    "gps": {"lat": 39.9045, "lon": 116.4071, "accuracy": 5, "weight": 0.6},
    "wifi": {"lat": 39.9039, "lon": 116.4078, "accuracy": 30, "weight": 0.3},
    "ip": {"lat": 39.9042, "lon": 116.4074, "accuracy": 5000, "weight": 0.1}
  },
  "timestamp": "2026-04-26T10:30:00Z"
}
```

## 3. Command Interface

```bash
# Get location using all available methods
python scripts/locate.py

# Use specific method(s)
python scripts/locate.py --method gps
python scripts/locate.py --method system,ip,wifi

# Output format
python scripts/locate.py --format json
python scripts/locate.py --format text
```

## 4. Optional API Keys

For enhanced accuracy, configure in environment:
```bash
export GOOGLE_GEOLOCATION_API_KEY="your-key"
export MLS_API_KEY="your-key"
export UNWIRED_API_KEY="your-key"
```

## 5. Platform Notes

- **Windows:** GeoCoordinateWatcher via PowerShell (WiFi + IP + GPS fusion)
- **macOS:** CoreLocation via locationd daemon
- **Linux:** GeoClue2 via D-Bus (Wi-Fi + cell fusion)

references/method-patterns.md

# Information Services -- Method Patterns & Coordination

> Overview document for information-services skill. Service-specific details in [location.md](location.md), [weather.md](weather.md), [time.md](time.md).

---

## 1. Trigger Scenarios

| Category | Triggers |
|----------|----------|
| Location | "where am I", "my coordinates", "get location", "GPS" |
| Weather | "weather", "forecast", "temperature", "rain" |
| Time | "what time is it", "current time", "time check" |
| Combined | "weather and time", "location and forecast" |
| Emergency | "emergency location", "SOS coordinates" |

## 2. Core Identity

**Role:** Unified information services hub. Single entry point for all location, weather, and time queries.

**Behavior:**
- Route to appropriate subsystem based on service type
- Use triangulation when multiple sources available
- Report confidence score for all results
- Graceful degradation when sources unavailable

## 3. Coordination Logic

### Request Routing

```
User query → Parse intent → Route to service → Execute → Score confidence → Return
```

### Intent → Service Mapping

| Intent Keywords | Service |
|----------------|---------|
| "where", "location", "coordinates", "GPS" | location |
| "weather", "forecast", "rain", "temperature" | weather |
| "time", "clock", "date", "when" | time |
| Multiple / none | all (sequential) |

### Fallback Chains

**Location:**
GPS → System → IP → WiFi → Cellular → Error(LOC_UNAVAILABLE)

**Weather:**
Primary API → Backup API → IP-location-based → Error(WEATHER_FAILED)

**Time:**
System → NTP → Web API → Error(TIME_FAILED)

## 4. Quality Metrics

| Metric | Target |
|--------|--------|
| Location accuracy | < 100m for triangulated |
| Weather freshness | < 30 min cache |
| Time accuracy | < 1s from NTP |
| Confidence scoring | ≥ 0.80 for all results |
| Fallback success rate | > 95% |

## 5. Constraints

- No persistent storage of location data
- No credential logging in output
- Rate-limit compliance for all external APIs
- Privacy: do not log coordinates without user request

references/time.md

# Time Service — Detailed Specifications

> Part of information-services skill.

---

## 1. Trigger Scenarios

| Scenario | Example Phrase |
|----------|----------------|
| Current time | "What time is it?" |
| Time check | "Report current time with confidence" |
| Timezone conversion | "What time is it in London?" |
| Precise time | "Accurate time via NTP" |

## 2. Multi-Source Time Fusion

### Source Priority

| Priority | Source | Accuracy | Latency |
|----------|--------|----------|---------|
| 1 | System clock | OS-dependent | Instant |
| 2 | NTP | ±10ms | 50-200ms |
| 3 | Web API (worldtimeapi, etc.) | ±500ms | 100-500ms |

### Workflow

1. Query system clock (instant, baseline)
2. If precision needed, query NTP server
3. If NTP fails, query web time API
4. Combine with confidence scoring
5. Return unified result

### Confidence Scoring

| Source | Base Confidence | Notes |
|--------|----------------|-------|
| System clock | 0.85 | OS-synced, may drift |
| NTP | 0.98 | Stratum-synchronized |
| Web API | 0.92 | Server-dependent |

### Output Format

```json
{
  "datetime": "2026-04-26T22:47:00+08:00",
  "timestamp": 1743084420,
  "timezone": "Asia/Hong_Kong",
  "sources": ["system", "ntp"],
  "confidence": 0.96,
  "accuracy_ms": 15
}
```

## 3. Voice Output (Optional)

When TTS is available and requested, optionally announce time in natural language:
- "It's 10:47 PM, Saturday, April 26th."
- Timezone-aware natural speech formatting

Sponsored

Ads related to Information Services and adjacent AI workflows.