web-ui-link

# Web UI Link Generator

Generate direct URLs to any page in the LimaCharlie web application at `https://app.limacharlie.io`.

---

## LimaCharlie Integration

> **Prerequisites**: Run `/init-lc` to initialize LimaCharlie context.

### API Access Pattern

All LimaCharlie API calls go through the `limacharlie-api-executor` sub-agent:

```
Task(
  subagent_type="lc-essentials:limacharlie-api-executor",
  model="sonnet",
  prompt="Execute LimaCharlie API call:
    - Function: <function-name>
    - Parameters: {<params>}
    - Return: RAW | <extraction instructions>
    - Script path: {skill_base_directory}/../../scripts/analyze-lc-result.sh"
)
```

### Critical Rules

| Rule | Wrong | Right |
|------|-------|-------|
| **MCP Access** | Call `mcp__*` directly | Use `limacharlie-api-executor` sub-agent |
| **OID** | Use org name | Use UUID (call `list_user_orgs` if needed) |

---

## When to Use

Invoke this skill when users:

- Ask for a **link to a LimaCharlie feature** (e.g., "link to the secrets page", "URL for D&R rules")
- Want to **open a specific page** (e.g., "open the detections dashboard", "go to sensors")
- Need to **navigate to a sensor page** (e.g., "show me the timeline for sensor X", "processes for DESKTOP-ABC")
- Ask **"where can I..."** questions about the web interface (e.g., "where can I configure outputs?")
- Request **browser/app links** to share with team members

Common trigger phrases:
- "link to...", "URL for...", "open...", "go to...", "navigate to..."
- "where is...", "where can I find...", "how do I access..."
- "browser link", "app link", "web UI"

## Base URL

All URLs use the base: `https://app.limacharlie.io`

## URL Reference

### Organization Routes (`/orgs/{oid}/*`)

These routes require an Organization ID (OID).

| Feature | Path | Aliases/Keywords |
|---------|------|------------------|
| Dashboard | `/orgs/{oid}/dashboard` | home, overview, main |
| Sensors | `/orgs/{oid}/sensors` | endpoints, agents, hosts, machines |
| Query Conso