Agent skill

Check Links

by wagtail in wagtail/awesome-wagtail

Guides the automated archival workflow of awesome links. An agent skill from wagtail/awesome-wagtail.

CC0-1.0Auto-check passed

Install Check Links

skills CLI
$ npx skills add wagtail/awesome-wagtail --skill check-links -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wagtail/awesome-wagtail check-links --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wagtail/awesome-wagtail.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/check-links .claude/skills/check-links && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
check-links
GitHub stars
2.2k
Token cost
~898 tokens
SKILL.md length
417 words
Files
2 (incl. scripts)
Skills in repo
1
Repo updated
First seen
Licence
CC0-1.0

At a glance

Guides the automated archival workflow of awesome links. An agent skill from wagtail/awesome-wagtail.

  • Works in 4 steps: Run the link checker → Read the report → Create or update the archive file → …
  • SKILL.md covers Overview, Requirements, Available scripts and Workflow
  • Runs Python scripts from its folder; calls git and gh

What it does

Check Links is an agent skill from wagtail/awesome-wagtail. Guides the automated archival workflow of awesome links. Fetching links data, moving stale entries.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/check_links.py`).

It works with GitHub. The repository describes itself as: A curated list of awesome packages, articles, and other cool resources from the Wagtail community. The licence is CC0-1.0.

Example prompts

  • “Use the check-links skill to guide the automated archival workflow of awesome links. An agent skill from wagtail/awesome-wagtail”
  • “/check-links”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Run the link checker
  2. Read the report
  3. Create or update the archive file
  4. Commit changes

What it can do on your machine

Read from SKILL.md and the folder at commit 70a72b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.astral.sh

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Check Links loads about 898 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 417 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~898

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from wagtail/awesome-wagtail at commit 70a72b5, republished under its CC0-1.0 licence (© wagtail). 417 words, ~898 tokens.

Download SKILL.mdSave it as .claude/skills/check-links/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
check-links
description
Guides the automated archival workflow of awesome links. Fetching links data, moving stale entries.
license
CC0
metadata.audience
maintainers
metadata.internal
true
metadata.disable-model-invocation
true

Overview

Analyze and maintain links in the README. Fetches metadata for each link, detects stale entries, auto-updates GitHub repo titles and descriptions, and produces a structured report for archival decisions.

Requirements

  • Python 3.12+ with uv
  • gh CLI authenticated (gh auth status)
  • Network access for HTTP requests (httpx)

Available scripts

  • scripts/check_links.py — Fetches metadata for all links in README.md and generates a Markdown report on stdout.

Workflow

bash
./scripts/check_links.py --dry-run

Always run with --dry-run first to preview changes without modifying the README. Re-run without --dry-run to auto-update GitHub repo titles and descriptions when you're ready.

Add --verbose to see progress and API call details on stderr.

The database is stored at .awesome-wagtail.duckdb by default. Subsequent runs reuse cached data (24 h for GitHub, 30 d for web pages).

2. Read the report

The report printed to stdout is your action plan. It contains these sections:

Auto-Archive Candidates (GitHub)

Repos that are archived on GitHub or have not been pushed to in over 24 months. These should be moved to docs/archive.md and removed from README.md.

Needs Review — 12–24 months (GitHub)

Repos with no commits in 12–24 months. For each entry, check whether the repo's GitHub page or its entry in README.md mentions "archived", "deprecated", or "unmaintained". If so, move to archive. If the repo is still active despite infrequent commits, leave it in place.

Repo link titles that differ from the project name found in the repo's README heading. Review the list — many README headings contain badge markup or instructions rather than a clean project name. Only update titles that are clearly better.

Show full SKILL.md (151 more words)Show less

Repo descriptions that differ from GitHub's project description. In most cases the GitHub description is shorter and more accurate. Apply these updates to README.md.

Auto-Archive Candidates (web pages)

Pages that have not been updated in over 5 years (based on HTTP Last-Modified headers, <meta> tags, or schema.org data). Move these to docs/archive.md.

Title Mismatches (web pages)

Page titles in README.md that differ from the actual <h1> or <title> of the page. Review and update if the fetched title is a better description of the link.

3. Create or update the archive file

The archive lives at docs/archive.md. Mirror the same section structure as README.md (section > subsection). For each archived link:

  1. Remove the line from README.md
  2. Add the line under the matching section in docs/archive.md

If the archive file does not exist yet, create it with:

markdown
# Awesome Wagtail Archive

> Archived projects from the main README that are no longer actively maintained.

## Apps

### Blogging/news

... archived items moved here ...
4. Commit changes

When finished, review the diff and commit:

bash
git diff
git add -A
git commit -m "check-links: archive stale entries and update metadata" --trailer "Assisted-by: <Agent harness> (<Model name>)"

© wagtail, CC0-1.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in .agents/skills/check-links of wagtail/awesome-wagtail.

  • SKILL.md
  • scripts/check_links.py

Open the folder on GitHubat commit 70a72b5

Compare with similar skills

Check Links next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Check Links compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Check Links this skillwagtail/awesome-wagtail2.2k—~898Automated safety check: PassCC0-1.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Diagnosing Superpowers Sessionsobra/superpowers297k3 repos~1.7kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    297k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed
  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated yesterday
    Research & ScienceAuto-check: notes

Works with

Questions about Check Links

What does Check Links do?

Guides the automated archival workflow of awesome links. An agent skill from wagtail/awesome-wagtail. Check Links is an agent skill from wagtail/awesome-wagtail. Guides the automated archival workflow of awesome links.

How do I install Check Links in Claude Code?

Run `npx skills add wagtail/awesome-wagtail --skill check-links -a claude-code`. Or copy the skill folder (.agents/skills/check-links in wagtail/awesome-wagtail) into .claude/skills/check-links in your project. Claude Code loads it when a task matches its description.

How do I install Check Links in Codex?

Run `npx skills add wagtail/awesome-wagtail --skill check-links -a codex`. Or copy the skill folder (.agents/skills/check-links in wagtail/awesome-wagtail) into .agents/skills/check-links in your project. Codex loads it when a task matches its description.

Can I use Check Links in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wagtail/awesome-wagtail --skill check-links -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/check-links, .gemini/skills/check-links, .github/skills/check-links and .opencode/skills/check-links in your project.

What does Check Links need to run?

Going by SKILL.md and its folder, Check Links needs Python for the scripts in its folder and the command-line tools its instructions call (git and gh). Our summary lists: Python 3.

Does Check Links access the network?

SKILL.md names 1 domain. As links in the text: docs.astral.sh. This is read from the text; nothing was executed.

Is Check Links safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Check Links use?

Check Links is published under the CC0-1.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Check Links use?

About 898 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Check Links?

Skills that share tags, products or a category with Check Links: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars) and Diagnosing Superpowers Sessions (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Check Links?

wagtail (a GitHub organization) maintains it in wagtail/awesome-wagtail, which has 2,191 GitHub stars. The repository was last updated on June 16, 2026.

Source: wagtail/awesome-wagtail on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.