infranodus/embodied-navigation
Transfer embodied movement principles (Vipassana equanimous scanning, Systema adaptive fluidity, contemporary dance tensegrity, EightOS confluence) to navigate work, relationships, projects, strategy, and everyday situations. Uses InfraNodus MCP tools to map situations as networks and apply body-informed intelligence to their structure. Trigger when someone is stuck, in conflict, negotiating, blocked, fixated, overwhelmed, or facing rigidity — or asks for "embodied advice", "fluid approach", "organic strategy", "adaptive strategy", "how would the body handle this". Also trigger on phrases like "I'm stuck", "standoff", "tense situation", "can't move forward". Apply proactively when situations exhibit excessive force, single-point fixation, or neglect of peripheral dynamics.
npx skills add https://github.com/infranodus/skills --skill embodied-navigation
Transfer principles from embodied movement practices to navigate any complex situation. The body has been shaped by evolution to handle uncertainty, conflict, flow, and transformation — its intelligence applies far beyond the physical.
Before applying embodied principles, make the situation *physical* — represent it as a network so you can see its topology, tensions, and gaps. This is analogous to scanning the body before moving.
Use InfraNodus MCP tools:
optimize_text_structure — get the full structural diagnosis (diversity score, clusters, gaps, main concepts, gateways). This is the primary tool — always start here when analyzing text, URL, or conversation.generate_topical_clusters — identify the main clusters of activity/attentiongenerate_content_gaps — find neglected connections between clustersdevelop_latent_topics — surface what's been overlookeddevelop_conceptual_bridges — find low-betweenness-to-degree-ratio nodes (the "joints" where small movements create large shifts)Without InfraNodus: Ask the user to describe the key elements, tensions, and relationships. Mentally map them as clusters and connections. Identify where attention is concentrated and where it's absent.
Read the network's structure the way you'd read a body:
| Network Pattern | Body Equivalent | Diagnosis |
|---|---|---|
| High-BC node dominance | Chronic tension point | Fixation — attention locked on one thing |
| Dense single cluster | Contracted muscle group | Rigidity — over-engaged, needs release |
| Many disconnected clusters | Scattered body awareness | Dispersed — needs grounding or bridging |
| Balanced clusters with bridges | Healthy tensegrity | Flow state — maintain and develop |
| Empty gaps between clusters | Numb zones, blind spots | Neglected areas holding generative potential |
| Peripheral isolated nodes | Extremities losing circulation | Overlooked resources or perspectives |
Select and combine principles based on what the situation needs. The principles below are organized by source practice but should be mixed fluidly.
Core: Instead of fixating on the point of tension, pass through it with observation — then move attention evenly across the whole field.
Application protocol:
generate_content_gaps and develop_latent_topics to find the "numb zones." Spend deliberate time with these. They often hold the most generative potential precisely because they've been overlooked.When to use: Obsessive thinking about a problem. Interpersonal fixation. Analysis paralysis caused by over-attending to one variable. Emotional reactivity. Any situation where attention is unevenly distributed.
Signature move: "What would it feel like to simply observe this without needing to solve it — and then give the same quality of attention to everything else in the picture?"
Core: Don't oppose force directly. Let the incoming energy arrive, absorb it, read its direction, then redirect it using its own momentum.
Application protocol:
develop_conceptual_bridges to find the pivot points — low-betweenness-to-degree-ratio nodes where small adjustments redirect large flows.generate_topical_clusters to see what momentum already exists.When to use: Conflict situations. Competitive dynamics. Negotiations. Receiving criticism or opposition. Strategic positioning. Any situation where direct force creates escalation.
Signature move: "Where is the energy in this situation already going — and how can I ride or redirect it rather than fighting against it?"
Core: When stuck, don't try to solve the stuck point directly. Shift the tension elsewhere and observe what changes. Sculpt the situation through aesthetic movement of force across the whole structure.
Application protocol:
Rigidity in any of these dimensions creates stagnation. Variation creates life.
When to use: Creative blocks. Project bottlenecks. Stagnant relationships or processes. When direct problem-solving keeps returning to the same point. When the situation feels "ugly" or "stuck" without a clear analytical reason.
Signature move: "Instead of solving this stuck point, what happens if I move the tension somewhere else and watch how the whole structure responds?"
Core: Integrate your flow into the existing flow to create a temporary shared form, which can then transform or dissipate. Navigate through assimilation → redirection → transformation.
Application protocol:
optimize_text_structure to understand the current state. If the network is biased, assimilate into the dominant cluster's language and frame before introducing new elements. If diversified, assimilate into smaller clusters first.When to use: Entering new environments (new job, new market, new social group). Leading change in organizations. Negotiating between multiple stakeholders. Any situation requiring influence without direct authority. Strategic transformation of existing structures.
Signature move: "How do I enter this flow without disrupting it, and from inside, where is the natural direction it can be redirected?"
For complex situations requiring multiple principles, use this phased approach:
Map the situation using optimize_text_structure (or mental mapping). Pass through all clusters without dwelling. Give equal attention to peripheral nodes. Identify where attention is fixated and where it's absent. Dissolve any interpretation chains that have already solidified.
Use generate_content_gaps and develop_latent_topics. Spend deliberate time with the neglected zones. These gaps hold generative potential. They're also where existing tensions can be released — the empty space the system needs to move into.
When stuck points are identified, don't attack them directly. Use develop_conceptual_bridges to find the joints (low BC-to-degree ratio nodes). Shift tension to these pivot points. Vary approach dynamically across speed, amplitude, force, intent, and scale. Observe aesthetic quality of the resulting movement.
Enter through the periphery. Assimilate into the network's existing structure and language. Use existing energy and momentum. Redirect gradually through conceptual bridges. Let transformation emerge organically rather than forcing outcomes. Accept dissipation as a valid result.
| Situation | Primary Principle | Supporting Principles |
|---|---|---|
| Fixation / obsessive thinking | Equanimous Scanning | Gap Attention |
| Conflict / opposition | Adaptive Fluidity | Tension Redistribution |
| Creative block / stagnation | Tension Redistribution | Equanimous Scanning |
| Entering new environment | Confluence | Adaptive Fluidity |
| Leading change | Confluence | All others as needed |
| Negotiation | Adaptive Fluidity | Confluence |
| Overwhelm / scattered | Equanimous Scanning | Confluence (grounding) |
| Strategic positioning | Confluence | Adaptive Fluidity |
| Relationship navigation | Equanimous Scanning | Tension Redistribution |
| Decision under uncertainty | Equanimous Scanning | Tension Redistribution |
Cognitive fixation on "important" nodes mirrors physical tension fixation — both create rigidity. Distributed attention across the network structure enables the same adaptive fluidity that makes embodied movement intelligent. The body already knows how to navigate complexity. The skill is learning to apply that knowledge beyond the body.
Take infranodus/embodied-navigation from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.