القائمة
Guides the automated archival workflow of awesome links. Fetching links data, moving stale entries.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | check-links |
| description | Guides the automated archival workflow of awesome links. Fetching links data, moving stale entries. |
| license | CC0 |
| metadata | {"audience":"maintainers","internal":true,"disable-model-invocation":true} |
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.
uvgh CLI authenticated (gh auth status)scripts/check_links.py — Fetches metadata for all links in README.md and generates a Markdown report on stdout../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).
The report printed to stdout is your action plan. It contains these sections:
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.
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.
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.
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.
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.
The archive lives at docs/archive.md. Mirror the same section structure
as README.md (section > subsection). For each archived link:
README.mddocs/archive.mdIf the archive file does not exist yet, create it with:
# Awesome Wagtail Archive
> Archived projects from the main README that are no longer actively maintained.
## Apps
### Blogging/news
... archived items moved here ...
When finished, review the diff and commit:
git diff
git add -A
git commit -m "check-links: archive stale entries and update metadata" --trailer "Assisted-by: <Agent harness> (<Model name>)"