specstory-link-trail

Parse SpecStory history files to track WebFetch URLs by session.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/zapabob/Skills --skill specstory-link-trail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specstory-link-trail
Source: https://github.com/zapabob/Skills/tree/main/registry/skills/specstory-link-trail/variants/cursor
Command: npx skills add https://github.com/zapabob/Skills --skill specstory-link-trail

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you keep track of all the URLs your AI assistant fetches during coding sessions, providing a clear audit trail of external resources accessed.

Core Features & Use Cases

  • URL Tracking: Automatically logs all URLs fetched using the WebFetch tool.
  • Session Grouping: Organizes fetched URLs by the SpecStory session they occurred in.
  • Success/Failure Reporting: Differentiates between successful and failed fetches, including error codes for failures.
  • Use Case: After an AI-assisted debugging session, you can easily review all the documentation pages, API references, or Stack Overflow threads the AI visited to resolve the issue.

Quick Start

Show me all the URLs I visited during my last coding session.

Frequently Asked Questions about specstory-link-trail

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

FAQPage Schema
How do I track URLs fetched by WebFetch during AI coding sessions?

You can track URLs fetched by WebFetch during AI coding sessions by parsing SpecStory history files to extract URLs, status codes, and context, grouping them by session.

How do I audit external resources accessed during SpecStory sessions?

Auditing external resources accessed during SpecStory sessions involves parsing history files to extract fetched URLs and grouping them by session to differentiate between successful and failed fetches.

Can I see error codes for failed WebFetch requests in my coding history?

Yes, you can see error codes for failed WebFetch requests because the URL tracking process differentiates between successful and failed fetches, including specific error codes for failures.

Do I need Python 3 to parse SpecStory history files for URL tracking?

Yes, you need Python 3 and its standard libraries for file parsing and JSON handling to successfully extract and group fetched URLs from SpecStory history files.

What is the best way to review documentation pages visited by an AI assistant?

The best way to review documentation pages visited by an AI assistant is to generate an audit trail that parses history files and organizes fetched URLs by the specific coding session.

How are fetched URLs grouped when tracking AI coding session history?

Fetched URLs are grouped by the specific SpecStory session they occurred in, allowing you to easily review external resources accessed during distinct coding tasks.