möbius-path-filtering
Non-orientable topological filtering that eliminates self-revisiting paths
npx skills add majiayu000/claude-skill-registry --skill m-bius-path-filtering --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Möbius Path Filtering ## Core Concept A Möbius filter is a **non-orientable topological constraint** that eliminates paths where traversal would require "doubling back" or revisiting a configuration from a different orientation. In navigator terms: some paths appear valid locally but are invalid globally because they would require the navigator to traverse the same logical position in two different ways simultaneously—geometrically impossible on a Möbius surface. This constraint is checked **before** path compilation, preventing invalid Navigators from ever being cached. ## Why Möbius Filtering? ### The Problem Consider a nested structure: ```julia data = Dict( "a" => [1, 2, 3], "b" => Dict( "c" => [4, 5, 6], "a" => [7, 8, 9] # Same key name, different context! ) ) ``` A naive path like `[ALL_KEYS, ALL_VALUES, ALL]` might: 1. Navigate to key "a" → [1, 2, 3] 2. Navigate to key "b" → {...} 3. Navigate to nested "a" → [7, 8, 9] But what if we then try to **transform all "a" keys**? The path becomes ambiguous: - Is "a" referring to the top-level key or the nested key? - Can we transform both simultaneously? - What if the nested "a" contains a reference back to the top-level "a"? On a
- Core Concept
- Why Möbius Filtering?
- The Problem
- The Solution
- Architecture
- Möbius Invariant
- Filtering Algorithm
- Orientation Mapping
- API
- Validation Functions
- Integration with Specter Navigator
- Performance
- Non-Backtracking Property
- Eliminates Invalid Paths Before Compilation
What does the möbius-path-filtering skill do?
Non-orientable topological filtering that eliminates self-revisiting paths
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill m-bius-path-filtering --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.