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".
Best use case
specstory-link-trail is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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".
Teams using specstory-link-trail should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/specstory-link-trail/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How specstory-link-trail Compares
| Feature / Agent | specstory-link-trail | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 ```bash # 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
specstory-yak
Analyze your SpecStory AI coding sessions in .specstory/history for yak shaving - when your initial goal got derailed into rabbit holes. Run when user says "analyze my yak shaving", "check for rabbit holes", "how distracted was I", or "yak shave score".
specstory-session-summary
Summarize recent SpecStory AI coding sessions in standup format. Use when the user wants to review sessions from .specstory/history, prepare for standups, track work progress, or understand what was accomplished.
specstory-project-stats
Fetch project statistics from SpecStory Cloud. Run when user says "get project stats", "show SpecStory stats", "project statistics", "how many sessions", or "SpecStory metrics".
specstory-organize
Organize SpecStory AI coding sessions in .specstory/history into year/month folders. Run when user says "organize my history", "clean up specstory", "sort my sessions", or "organize specstory files".
specstory-guard
Install a pre-commit hook that scans .specstory/history for secrets before commits. Run when user says "set up secret scanning", "install specstory guard", "protect my history", or "check for secrets".
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.
system-environment-configuration
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.
pentaphase-orchestrator
Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.
landscape-discovery-audit
Phase 1 of the pentaphase structural-overhaul protocol. Inventories assets, maps current flow, identifies friction, and defines value metrics for any substrate. Use when the user invokes phase 1 of an overhaul, requests a baseline audit, asks to "discover the landscape" of a system, or wants to understand current state before redesigning. Produces phase-1-landscape-report.md.
governance-evolution-protocol
Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.
dimension-surfacing
Surfaces the parallel domain dimensions implicit in a dense or minimal prompt. Use when a user prompt is small on the surface but plainly implies multiple independent domains needing different expertise; when explicitly invoked by the coliseum-orchestrator skill as Phase 1; or when the user asks "what dimensions does this prompt encode" or "what axes does this break into." Produces a named dimension set where each dimension is independently executable and not a paraphrase of another.