Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
specstoryai avatar

Specstory Link Trail

  • 238 installs
  • 31 repo stars
  • Updated January 31, 2026
  • specstoryai/agent-skills

Use specstory-link-trail for development tasks

About

specstory-link-trail: A skill for development. This provides functionality for development workflows.

  • specstory-link-trail

Specstory Link Trail by the numbers

  • 238 all-time installs (skills.sh)
  • +4 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #1,585 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/specstoryai/agent-skills --skill specstory-link-trail

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs238
repo stars31
Last updatedJanuary 31, 2026
Repositoryspecstoryai/agent-skills

What it does

Use specstory-link-trail for development tasks

Files

SKILL.mdMarkdownGitHub ↗

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 saysScript behavior
/specstory-link-trailAll sessions in history
/specstory-link-trail todayToday's sessions only
/specstory-link-trail last sessionMost recent session
/specstory-link-trail 2026-01-22Sessions from specific date
/specstory-link-trail *.mdCustom 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

Related skills

Backend & APIsbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.