fullstory-async-methods

Implement safe asynchronous calls for the fullstory-async-methods API.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/rcmaples/btx --skill fullstory-async-methods
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fullstory-async-methods
Source: https://github.com/rcmaples/btx/tree/main/.claude/skills/fullstory-async-methods
Command: npx skills add https://github.com/rcmaples/btx --skill fullstory-async-methods

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to implementing Fullstory's asynchronous methods in web apps, ensuring non-blocking initialization and robust error handling.

Core Features & Use Cases

  • Safe async patterns: Use timeout wrappers, try/catch blocks, and sequencing to avoid blocking app startup.
  • Session URL handling: Retrieve session URLs without breaking the user experience and attach them to reports or logs.
  • Observability and resilience: Implement observeAsync patterns with cleanup and fallback paths for degraded environments.

Quick Start

Use the fullstory-async-methods skill to configure a safe getSessionAsync call with a timeout, then proceed with app startup and log results.

Frequently Asked Questions about fullstory-async-methods

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

FAQPage Schema
How do I safely implement Fullstory getSessionAsync without blocking app startup?

Retrieve the session URL by configuring a safe getSessionAsync call with a timeout wrapper. This ensures the asynchronous retrieval process does not block app startup and allows you to attach the resulting URL to logs or error reports.

What is the best way to handle Fullstory setIdentityAsync and trackEventAsync in JavaScript?

Handle setIdentityAsync and trackEventAsync by awaiting them inside try/catch blocks with proper sequencing. This approach enforces robust error reporting and prevents unhandled promise rejections from disrupting the web app's user experience.

Why does wiring observeAsync require cleanup in degraded environments?

Wiring observeAsync requires cleanup to maintain observability and resilience in degraded environments. Implementing proper cleanup and fallback paths ensures graceful degradation when the asynchronous API encounters errors or timeouts.

How do I add timeouts to Fullstory async methods to prevent blocking UX?

Add timeouts to Fullstory async methods by wrapping calls like getSessionAsync in timeout functions combined with try/catch error handling. This enforces sequencing and graceful degradation, ensuring reliable analytics behavior without blocking UX.

Can I use Promise-based error handling for Fullstory's asynchronous API methods?

Yes, you can use Promise-based error handling for Fullstory's asynchronous API methods. Implementing try/catch blocks around awaited promises ensures robust error reporting and prevents startup failures during session retrieval and event tracking.