lychee

Included with Lifetime

$97 forever

Check for broken links with lychee — fast Rust link checker for Markdown, HTML, and codebases. Use when validating URLs or finding dead links.

Web Dev

What this skill does


# Lychee

Fast link checker written in Rust. Finds broken URLs and mail addresses in Markdown, HTML, and other text formats.

## Basic Usage

Check an entire project:

```bash
lychee .                          # Recursively check all supported files
                                  # Exit 0 = all OK, non-zero = failures found
```

Check a single file or URL:

```bash
lychee README.md                  # Single file
lychee 'docs/**/*.md'             # Glob (quote to prevent shell expansion)
lychee https://example.com        # Website URL
```

## CI-Friendly Output

Disable the progress bar for scripts and CI:

```bash
lychee --no-progress .
```

## Configuration Options

Include mail addresses and fragment anchors:

```bash
lychee --include-mail --include-fragments .
```

Exclude URLs or paths (regex patterns, repeatable):

```bash
lychee --exclude '^https://github\.com/' \
       --exclude-path 'node_modules' \
       .
```

Remap URL patterns:

```bash
lychee --remap 'https://old.com https://new.com' README.md
```

## Debugging

- `lychee --dump README.md` — list extracted links without checking them
- `lychee -vvv` — verbose retry details
- `--suggest` — propose replacements via web archive

## Rules

- Set `GITHUB_TOKEN` env var to avoid GitHub rate limits
- Use `--exclude-all-private` to skip private IPs and loopback
- Create `lychee.toml` for persistent project settings
- Use `--cache .` for faster repeated checks
- Use `-f json` or `-f markdown` for structured output

Files: 1

Size: 1.7 KB

Complexity: 10/100

Category: Web Dev

Source: https://github.com/knoopx/pi/tree/main/agent/skills/tools/lychee

Related in Web Dev

generating-lwc-components

Included

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.

Web Devscripts

document-processor-api

Included

Process documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.

Web Devscripts

nutrient-document-processing

Included

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.

Web Devscripts

accelint-nextjs-best-practices

Included

Next.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.

Web Devscripts