# Liminality

> Use this tool when you need to break down complex requests into manageable sub-questions and route them to relevant tools for efficient processing. It solves problems of information overload and tool selection by providing a reusable route for similar requests. The tool takes in a complex request as input and outputs a set of grounded sub-questions with corresponding tool routes.

Canonical page: https://skillsregistry.net/skills/ai-physea-liminality  
JSON: https://api.skillsregistry.net/v1/skills/ai-physea-liminality

## Description

Breaks a hard question or decision into checkable sub-questions, grounds each to a real tool.

## Trust

- **Trust score (0–1):** 0.99
- **Verification tier:** verified
- **Last scanned:** 2026-09-28

## Facts

- **Version:** 1.0.0
- **Skill type:** atomic
- **Execution layer:** mcp-remote
- **Runtime environment:** api
- **Category:** other
- **Updated:** 2026-09-28

## Source

- **Source listing:** [MCP Registry](https://registry.modelcontextprotocol.io/v0/servers/ai.physea%2Fliminality)
- **Repository:** <https://github.com/jaybro2042-alt/liminality-mcp>

## Use it

MCP endpoint published by the skill: `https://liminality.physea.ai/mcp`

Resolve this record through the SkillsRegistry MCP server (no auth, read-only):

```
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp
```

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_skill",
    "arguments": {
      "slug": "ai-physea-liminality"
    }
  }
}
```

REST: `GET https://api.skillsregistry.net/v1/skills/ai-physea-liminality` · pull for local use: `GET https://api.skillsregistry.net/v1/skills/ai-physea-liminality/pull`

---
SkillsRegistry indexes agent skills from public registries and GitHub. Skills we have analysed are scanned with Circle-IR and scored on six dimensions; each listing states its scan coverage. More: https://skillsregistry.net/llms.txt