Skip to content
Development
Skill

/specstory-link-trail

Track all URLs fetched during SpecStory AI coding sessions. Run when user says "show my link trail", "what URLs did I visit", "list fetched links", or "show web fetches".

From plugin
agent-skills
356 skills

Claude Code

$ npx -y skills add specstoryai/agent-skills --skill specstory-link-trail --agent claude-code

SKILL.md

specstory-link-trail.SKILL.md
name: specstory-link-trail
description: Track all URLs fetched during SpecStory AI coding sessions. Run when user says "show my link trail", "what URLs did I visit", "list fetched links", or "show web fetches".
license: Apache-2.0
metadata:
  author: SpecStory, Inc.
  version: "1.0.0"
  argument-hint: "[history-file-or-pattern]"
allowed-tools: Bash, Read

SpecStory Link Trail

Reviews your `.specstory/history` sessions and creates a summary of all URLs that were fetched via WebFetch tool calls. Useful for auditing external resources accessed during development.

How It Works

1. **Parses** SpecStory history files for WebFetch tool calls 2. **Extracts** URLs, status codes, and context 3. **Groups** by session with timestamps 4. **Separates** successful fetches from failures 5. **Deduplicates** repeated URLs with fetch counts

Why Track Links?

During AI-assisted coding, your assistant fetches documentation, APIs, and resources on your behalf. Link Trail helps you:

  • Audit what external resources were accessed
  • Find that documentation page you saw earlier
  • Review failed fetches that might need retry
  • Understand your research patterns

Usage

Slash Command

| User says | Script behavior | |-----------|-----------------| | `/specstory-link-trail` | All sessions in history | | `/specstory-link-trail today` | Today's sessions only | | `/specstory-link-trail last session` | Most recent session | | `/specstory-link-trail 2026-01-22` | Sessions from specific date | | `/specstory-link-trail *.md` | Custom glob pattern |

Direct Script Usage

# All sessions
python skills/specstory-link-trail/parse_webfetch.py .specstory/history/*.md | \
  python skills/specstory-link-trail/generate_report.py -

# Specific session
python skills/specstory-link-trail/parse_webfetch.py .specstory/history/2026-01-22*.md | \
  python skills/specstory-link-trail/generate_report.py -

# Sessions from a date range
python skills/specstory-link-trail/parse_webfetch.py .specstory/history/2026-01-2*.md | \
  python skills/specstory-link-trail/generate_report.py -

Output

Link Trail Report
=================

Sessions analyzed: 5
Total URLs fetched: 23 (18 successful, 5 failed)

Session: fix-authentication-bug (2026-01-22)
--------------------------------------------
Successful fetches:
  - https://docs.github.com/en/rest/authentication (×2)
  - https://jwt.io/introduction
  - https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401

Failed fetches:
  - https://internal.company.com/api/docs (403 Forbidden)

Session: add-caching-layer (2026-01-21)
---------------------------------------
Successful fetches:
  - https://redis.io/docs/latest/commands
  - https://docs.python.org/3/library/functools.html#functools.lru_cache
  - https://stackoverflow.com/questions/... (×3)

Summary by Domain
-----------------
  github.com: 5 fetches
  stackoverflow.com: 4 fetches
  docs.python.org: 3 fetches
  redis.io: 2 fetches
  (9 other domains): 9 fetches

Present Results to User

The script output IS the report. Present it directly without additional commentary, but you may:

1. **Highlight key findings** - Most frequently accessed domains, any failed fetches 2. **Offer follow-ups** - "Want me to retry the failed fetches?" or "Need details on any of these?"

Example Response

Here's your link trail from recent sessions:

[script output here]

I noticed 5 failed fetches - mostly internal URLs that require authentication.
The most accessed domain was github.com (5 fetches), mostly for their REST API docs.

Would you like me to:
- Retry any of the failed fetches?
- Open any of these links?
- Filter to a specific session?

Notes

  • Uses streaming parsing for large history files
  • URLs are extracted from WebFetch tool calls in the history
  • Fetch counts show when the same URL was accessed multiple times
  • Failed fetches include the HTTP status code when available
Read more
@specstoryai
Ships withagent-skills

A collection of AI agent skills for working with SpecStory session histories. Built for developers who want Claude Code (or similar AI coding assistants) to help analyze, organize, and extract insights from their AI-assisted coding sessions.

Stars on GitHub

Momentum

stars in total
35
Star history of specstoryai/agent-skills on GitHub, a chart by star-history.com

Other skills on agent-skills.

specstory-guard

specstory-guard

Install a pre-commit hook that scans .specstory/history for secrets before commits. Run when user says "set up secret scanning",…

specstory-yak

specstory-yak

Analyze your SpecStory AI coding sessions in .specstory/history for yak shaving - when your initial goal got derailed into rabbit…

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills10d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc11d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react1d252k
@facebook@facebookInstall Skill

Questions about specstory-link-trail.

Which coding agents can use specstory-link-trail?
specstory-link-trail installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.