va-session

Resolve the current VibeAround session ID from route state and agent metadata.

511|53|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/jazzenchen/VibeAround --skill va-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: va-session
Source: https://github.com/jazzenchen/VibeAround/tree/main/src/skills/va-session
Command: npx skills add https://github.com/jazzenchen/VibeAround --skill va-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the need to easily retrieve the current VibeAround session ID for integration with other skills and for user query fulfillment.

Core Features & Use Cases

  • Session ID Resolution: Provides the unique identifier for the active VibeAround session.
  • Contextual Integration: Allows other skills and users to access the necessary session context for further operations.
  • Use Case: When a user needs to know their session ID for handover purposes or for other skills that rely on session context, this skill can provide it.

Quick Start

Query the current session ID with the command "What is my VibeAround session ID?"

Frequently Asked Questions about va-session

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

FAQPage Schema
How do I retrieve my VibeAround session ID for skill integration?

To retrieve your VibeAround session ID, query the current session context using a command like "What is my VibeAround session ID?". The skill resolves the active session identifier for contextual operations.

When do I need to resolve a session ID for contextual information?

You need to resolve a session ID when maintaining session context across different skills or fulfilling user queries that require handover to other operations relying on the active VibeAround session.

How does session ID resolution work across different skills?

Session ID resolution works by accessing VibeAround route state and agent metadata to provide a unique identifier. This allows other skills to access the necessary session context for further operations.

Can I use this session resolver without VibeAround route state access?

No, resolving the current VibeAround session ID requires access to VibeAround route state and agent metadata to successfully provide the unique session context identifier.

What's the best way to maintain session context across user queries?

The best way to maintain session context is by resolving the active VibeAround session ID. This unique identifier allows different skills to access and operate within the same session context.