spec-bridge-walk

Analyze page connections by producing numbered observations with optional link graphs.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/float-ritual-stack/floatty --skill spec-bridge-walk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-bridge-walk
Source: https://github.com/float-ritual-stack/floatty/tree/main/apps/outline-explorer/src/lib/skills/spec-bridge-walk
Command: npx skills add https://github.com/float-ritual-stack/floatty --skill spec-bridge-walk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridge Walk provides a structured way to analyze and present connections between pages by generating numbered observations and optional link graphs, improving clarity and traceability.

Core Features & Use Cases

  • SectionLabel (label, color?, icon?) — section header. Use color:"purple", icon:"Compass".
  • ObservationCard (number, title, body, severity?: "surprising"|"structural"|"gap"|"thread"|"meta", links?: string[]) — expandable numbered observation. links are wikilink targets.
  • LinkGraph (nodes: [{id, label, color?, weight?, center?, ring?, type?}], edges: [[fromId, toId]]) — SVG radial graph showing page neighborhoods.
  • Paragraph (content) — body text.
  • BlockRef (title, page?, blockId?) — clickable wikilink reference.
  • WalkChip (page, reason?) — walk suggestion chip.
  • Use cases: content auditing, knowledge graph exploration, and complex documentation reviews.

Quick Start

Invoke Bridge Walk to produce numbered observations with cross-references and optional link graph for a given page.

Frequently Asked Questions about spec-bridge-walk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate numbered observations for analyzing connections between pages?

To generate numbered observations for page connections, invoke the structured bridge-walk analysis to produce expandable cards with titles, bodies, severity types, and cross-referenced wikilinks. This structured approach improves clarity and traceability when analyzing relationships across page neighborhoods.

What is the best way to visualize page neighborhoods in a knowledge graph?

The best way to visualize page neighborhoods in a knowledge graph is by generating an SVG radial link graph with nodes and edges. This visualization displays connections between pages using colored nodes with optional weights, rings, and center markers to aid content exploration.

How do I structure content audits using wikilinks and cross-references?

Structure content audits using wikilinks by generating numbered observation cards with severity classifications like surprising, structural, gap, thread, or meta. Each card includes clickable cross-references to target pages, enabling traceable documentation reviews across connected content neighborhoods.

Can I add walk suggestions and clickable references to my knowledge graph exploration?

Yes, you can add walk suggestions and clickable references to knowledge graph exploration by using suggestion chips with page targets and optional reasons, alongside clickable block references. These components guide users through related content neighborhoods during structural analysis.

Does bridge-walk analysis require any external dependencies or scripts?

No, bridge-walk analysis requires no external dependencies to function. The implementation operates independently with optional scripts, references, or assets directories added as needed, requiring only a YAML frontmatter entry for name and description to begin generating structured observations.

When should I not use a structured observation approach for documentation review?

You should avoid using structured observation approaches for simple, linear documentation that lacks inter-page connections or complex relationships. This method is designed for content auditing and knowledge graph exploration where analyzing page neighborhoods and cross-references provides meaningful structural insights.