pi-share

Parse pi-share session transcripts from URLs or gists into structured conversation history.

6|1|Updated Nov 23, 2023
One-click install
npx skills add https://github.com/gmcabrita/dotfiles --skill pi-share-gmcabrita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pi-share
Source: https://github.com/gmcabrita/dotfiles/tree/main/.agents/skills/pi-share
Command: npx skills add https://github.com/gmcabrita/dotfiles --skill pi-share-gmcabrita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

pi-share automates loading and decoding session transcripts from pi-share URLs and GitHub gists, turning embedded data into usable conversation history.

Core Features & Use Cases

  • Decode base64-embedded session data from session.html.
  • Extract and structure human/assistant turn history for analysis.
  • Support fetching by URL, gist ID, or shorthand IDs for quick review.

Quick Start

Provide a pi-share URL or gist ID to fetch and display the decoded session data.

Frequently Asked Questions about pi-share

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

FAQPage Schema
How do I parse pi-share session transcripts from a URL?

To parse pi-share session transcripts, provide a valid URL from shittycodingagent.ai, buildwithpi.ai, buildwithpi.com, or pi.dev. The skill fetches the session.html, decodes the embedded base64 data, and structures the conversation history for analysis.

Can I extract conversation history from a GitHub gist ID?

Yes, you can extract conversation history by providing a direct GitHub gist ID. The skill fetches the gist content, decodes the base64-encoded session data, and outputs standardized human and assistant turn entries.

What is base64-encoded session data in pi-share transcripts?

Base64-encoded session data is the embedded payload within session.html files that stores the raw conversation history. The skill decodes this base64 format to produce readable, structured conversation transcripts suitable for downstream analysis.

Does this session parser work with buildwithpi.ai and pi.dev links?

Yes, the session parser works with buildwithpi.ai, buildwithpi.com, pi.dev, and shittycodingagent.ai links. It accepts these pi-share URLs directly to extract and decode the embedded session data into a standardized format.

What is the best way to structure base64 session data for analysis?

The best way to structure base64 session data is to decode it into standardized entries and headers. This skill automates that process, returning a consistent conversation history data structure with optional summaries for downstream processing.

Why does my pi-share URL fail to load conversation history?

Loading conversation history fails when the provided pi-share URL does not contain valid base64-encoded session data in the session.html. Ensure the URL points to a supported domain or a valid direct gist ID for successful parsing.