Agent 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".

majiayu000534★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill specstory-link-trail --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Version: 1.0.0
Declared author: SpecStory, Inc.
Allowed tools: BashRead
Path: skills/analysis/specstory-link-trail/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 S

What's inside
Steps it walks through
  1. How It Works
  2. Why Track Links?
  3. Usage
  4. Slash Command
  5. Direct Script Usage
  6. Output
  7. Present Results to User
  8. Example Response
  9. Notes
Ships with 1 file
  • metadata.json
Commands it runs
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 | \
Sessions from a date range
python skills/specstory-link-trail/parse_webfetch.py .specstory/history/2026-01-2*.md | \
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the specstory-link-trail 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".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill specstory-link-trail --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.