skills.rest
ElNiak
ElNiakCOMMUNITY
Explore all skills by this author →
𝕏@CyberElNiakGitHub

ivy-lsp-walkthrough

Demonstrate formal protocol testing with Ivy LSP navigation and MCP verification.

Updated Feb 25, 2026
Search Tags:#mcp#code navigation#formal verification#quic#lsp#protocol testing#ivy
One-click install
npx skills add https://github.com/ElNiak/panther-ivy-plugin --skill ivy-lsp-walkthrough
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ivy-lsp-walkthrough
Source: https://github.com/ElNiak/panther-ivy-plugin/tree/main/plugins/panther-ivy-plugin/skills/ivy-lsp-walkthrough
Command: npx skills add https://github.com/ElNiak/panther-ivy-plugin --skill ivy-lsp-walkthrough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided, end-to-end demonstration of how to use the Ivy Language Server Protocol (LSP) for code navigation and the MCP tool for formal verification and analysis within the PANTHER-Ivy tester framework.

Core Features & Use Cases

  • Semantic Code Navigation: Utilize LSP features like documentSymbol, workspaceSymbol, goToDefinition, findReferences, and hover to understand complex protocol specifications.
  • Formal Verification & Analysis: Employ MCP tools such as ivy_coverage, ivy_lint, and ivy_verify to ensure protocol compliance and identify gaps.
  • Use Case: You need to add a new requirement to a formal protocol specification (like QUIC) and ensure it's correctly implemented and verifiable. This Skill walks you through finding relevant code, understanding its structure, identifying coverage gaps, writing the new monitor, and verifying its correctness and traceability.

Quick Start

Use the ivy-lsp-walkthrough skill to add an RFC requirement to the QUIC protocol specification.

Frequently Asked Questions about ivy-lsp-walkthrough

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

FAQPage Schema
How do I add a new RFC requirement to a formal protocol specification like QUIC?▼

Ivy LSP enables semantic code navigation for formal protocol testing by providing features like documentSymbol, workspaceSymbol, goToDefinition, findReferences, and hover to understand complex specifications.

How do I identify coverage gaps in Ivy protocol testing?▼

You identify coverage gaps in Ivy protocol testing by employing the ivy_coverage MCP tool to analyze formal specifications, ensuring protocol compliance and highlighting untested areas.

How do I verify formal specifications in Ivy?▼

Yes, you can use LSP features like goToDefinition and findReferences for Ivy code navigation, allowing you to find relevant code and understand its structure before writing new protocol monitors.

Do I need the ivy-tools MCP server for protocol linting and verification?▼

Yes, the ivy-tools MCP server is required to perform protocol linting, coverage analysis, and formal verification alongside the Ivy LSP for end-to-end protocol testing workflows.

What is the best way to ensure traceability when updating formal protocol specifications?▼

The best way to ensure traceability when updating formal protocol specifications is using MCP tools to verify correctness and coverage after using LSP to navigate and implement the new monitors.

Related Skills

Explore More Software Engineering Skills→
ElNiakElNiak

workflow-reference

Translate RFC normative language into formal Ivy constructs and run verification.

Community
Advanced
encero-systemsencero-systems
92

review-scope

Review code changes against defined scopes and documentation.

Official
Advanced
ElNiakElNiak

nct-methodology

Guide the 10-step NCT workflow for formal protocol testing with Ivy.

Community
Advanced
leogodin217leogodin217
60

eval-sprint

Evaluate sprint specifications for flaws using adversarial review and LSP tools.

Community
Advanced