Agent Session Monitor
higress-group/higress
Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage.
A skill your agent uses when auditing a site's internal link graph for dead-end pages, suggesting related-content links to add to thin or standalone pages, or reviewing CMS templates that produce…
Install Dead End Pages
$ npx skills add thedaviddias/Front-End-Checklist --skill dead-end-pages -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist dead-end-pages --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dead-end-pages .claude/skills/dead-end-pages && rm -rf skills-srcUse ~/.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/
Install the "dead-end-pages" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/dead-end-pages into .claude/skills/dead-end-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dead-end-pages", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/dead-end-pagesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill dead-end-pages -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist dead-end-pages --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/dead-end-pages .agents/skills/dead-end-pages && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dead-end-pages" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/dead-end-pages into .agents/skills/dead-end-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dead-end-pages", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill dead-end-pages -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist dead-end-pages --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/dead-end-pages .cursor/skills/dead-end-pages && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dead-end-pages" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/dead-end-pages into .cursor/skills/dead-end-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dead-end-pages", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/dead-end-pages--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill dead-end-pages -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist dead-end-pages --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/dead-end-pages .gemini/skills/dead-end-pages && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dead-end-pages" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/dead-end-pages into .gemini/skills/dead-end-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dead-end-pages", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist dead-end-pagesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill dead-end-pages -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/dead-end-pages .github/skills/dead-end-pages && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dead-end-pages" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/dead-end-pages into .github/skills/dead-end-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dead-end-pages", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill dead-end-pages -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist dead-end-pages --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/dead-end-pages .opencode/skills/dead-end-pages && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dead-end-pages" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/dead-end-pages into .opencode/skills/dead-end-pages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dead-end-pages", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dead-end-pages- GitHub stars
- 74k
- Token cost
- ~683 tokens
- SKILL.md length
- 360 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing a site's internal link graph for dead-end pages, suggesting related-content links to add to thin or standalone pages, or reviewing CMS templates that produce…
- Works in 6 steps: Identify all pages flagged as dead ends… → For each dead-end page, identify 2–5… → Add contextual inline links within the… → …
- Auditing a sites internal link graph for dead-end pages
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Dead End Pages is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing a site's internal link graph for dead-end pages, suggesting related-content links to add to thin or standalone pages, or reviewing CMS templates that produce link-free content pages.
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Data & Analytics. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Auditing a sites internal link graph for dead-end pages
- Suggesting related-content links to add to thin
- Standalone pages
- Reviewing CMS templates that produce link-free content pages
Example prompts
- “/dead-end-pages”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Identify all pages flagged as dead ends (no or minimal outgoing internal links in body content).
- For each dead-end page, identify 2–5 topically related pages on the site.
- Add contextual inline links within the body content — not just in headers or footers.
- Example: A blog post about CSS Grid should link to related posts on Flexbox and responsive design.
- Add a "Related articles" or "See also" section at the bottom if inline links are not practical.
- Re-crawl after changes to verify the links appear in the rendered DOM.
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. 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
No scripts in the folder and no shell commands in SKILL.md.
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):
frontendchecklist.io
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
Dead End Pages loads about 683 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 360 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 360 words, ~683 tokens.
Download SKILL.mdSave it as
.claude/skills/dead-end-pages/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- dead-end-pages
- description
- Use when auditing a site's internal link graph for dead-end pages, suggesting related-content links to add to thin or standalone pages, or reviewing CMS templates that produce link-free content pages.
- metadata.category
- seo
- metadata.priority
- medium
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/seo/dead-end-pages
Add outgoing links to dead-end pages
Googlebot follows links to discover and re-crawl pages. A page with no outgoing internal links stops the crawler from reaching the rest of your site from that point and leaves users with nowhere logical to go, increasing bounce rate.
Quick Reference
- Every page should link to at least 2–3 contextually relevant internal pages to aid navigation and crawling
- Pages with zero outgoing links trap crawlers and users, forming dead ends in your site's link graph
- Contextual inline links (within body content) pass more value than footer or navigation links alone
Check
For each page, count the number of <a href> links pointing to other pages on the same domain (exclude navigation/header/footer if they are templated identically across all pages). Flag any page with zero or fewer than two unique internal links in the main content body (<main> or <article> element).
Fix
- Identify all pages flagged as dead ends (no or minimal outgoing internal links in body content).
- For each dead-end page, identify 2–5 topically related pages on the site.
- Add contextual inline links within the body content — not just in headers or footers.
- Example: A blog post about CSS Grid should link to related posts on Flexbox and responsive design.
- Add a "Related articles" or "See also" section at the bottom if inline links are not practical.
- Re-crawl after changes to verify the links appear in the rendered DOM.
Show full SKILL.md (119 more words)Show less
Explain
Internal links are the edges of your site's graph. Crawlers navigate by following links; a page with no outgoing links is a node with no edges leading forward. This prevents Googlebot from discovering linked pages during a crawl initiated from that dead end, and it signals to users that there is nothing more to explore.
Code Review
Parse the <main> or <article> element of each rendered page. Count <a href> tags pointing to same-domain URLs. Flag pages with fewer than 2 such links. Exclude navigation, header, and footer elements that are shared across all pages, as these do not count as contextual internal links.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/dead-end-pages
© thedaviddias, MIT. 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 (references) in skills/dead-end-pages of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Dead End Pages 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dead End Pages this skillthedaviddias/Front-End-Checklist | 74k | — | ~683 | Automated safety check: Pass | MIT | |
| Agent Session Monitorhigress-group/higress | 9.5k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Chart Visualizationstophobia/deerflow2.0-enhanced | 822 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Tufte Chartgnurio/tufte-vdqi-plugin | 309 | — | ~2.1k | Automated safety check: Pass | None | |
| Mvizmatsonj/mviz | 227 | — | ~11k | Automated safety check: Pass | None | |
| Dataviz Design GuidanceQwenLM/qwen-code | 28k | — | ~514 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Chart Visualization
stophobia/deerflow2.0-enhanced
This skill should be used when the user wants to visualize data.
Tufte Chart
gnurio/tufte-vdqi-plugin
Render a real, publication-ready data graphic (SVG or HTML) that obeys Tufte's principles — minimal ink, range-frame axes, direct labels, honest proportions.
Mviz
matsonj/mviz
A chart & report builder for AI. An agent skill from matsonj/mviz.
Dataviz Design Guidance
QwenLM/qwen-code
Guides chart, dashboard and map design: pick the simplest form for the question, state the finding in the title, and check palettes with a local validator.
Chart Visualization
Citrus-bit/Anaxa
A skill your agent uses whenever the user wants a chart, graph, plot, dashboard visual, or asks to visualize structured numbers, trends, comparisons, proportions, distributions, correlations…
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Categories
Questions about Dead End Pages
What does Dead End Pages do?
A skill your agent uses when auditing a site's internal link graph for dead-end pages, suggesting related-content links to add to thin or standalone pages, or reviewing CMS templates that produce…. Dead End Pages is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing a site's internal link graph for dead-end pages, suggesting related-content links to add to thin or standalone pages, or reviewing CMS templates that produce link-free content pages.
When should I use Dead End Pages?
Dead End Pages fits situations like: auditing a sites internal link graph for dead-end pages; suggesting related-content links to add to thin; standalone pages; reviewing CMS templates that produce link-free content pages.
How do I install Dead End Pages in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill dead-end-pages -a claude-code`. Or copy the skill folder (skills/dead-end-pages in thedaviddias/Front-End-Checklist) into .claude/skills/dead-end-pages in your project. Claude Code loads it when a task matches its description.
How do I install Dead End Pages in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill dead-end-pages -a codex`. Or copy the skill folder (skills/dead-end-pages in thedaviddias/Front-End-Checklist) into .agents/skills/dead-end-pages in your project. Codex loads it when a task matches its description.
Can I use Dead End Pages 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 thedaviddias/Front-End-Checklist --skill dead-end-pages -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dead-end-pages, .gemini/skills/dead-end-pages, .github/skills/dead-end-pages and .opencode/skills/dead-end-pages in your project.
What does Dead End Pages need to run?
SKILL.md names no scripts, command-line tools or credentials: Dead End Pages is instructions for the agent only.
Does Dead End Pages access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Dead End Pages 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. Review the folder before installing.
What licence does Dead End Pages use?
Dead End Pages is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Dead End Pages use?
About 683 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Dead End Pages?
Skills that share tags, products or a category with Dead End Pages: Agent Session Monitor (higress-group/higress, 9.5k stars), Chart Visualization (stophobia/deerflow2.0-enhanced, 822 stars), Tufte Chart (gnurio/tufte-vdqi-plugin, 309 stars) and Mviz (matsonj/mviz, 227 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dead End Pages?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.