When the user wants to optimize internal linking, fix orphan pages, or improve link structure. Also use when the user mentions "internal links," "internal linking," "anchor text," "link equity," "internal linking strategy," or "orphan pages." For IA, use website-structure.
npx skills add https://github.com/kostja94/marketing-skills --skill internal-links
Guides internal linking strategy for SEO: crawlability, link equity distribution, and user navigation.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site structure and key pages.
Identify:
| Principle | Guideline |
|-----------|-----------|
| Depth | Important pages within 3 clicks from homepage |
| Orphan pages | Avoid; ensure every page has at least one internal link; see site-crawlability for technical detection and crawl issues |
| Hub-to-spoke | Link from hub/pillar pages to cluster articles; topic cluster structure |
| Contextual | Place links in relevant body content, not just footers |
| Principle | Guideline |
|-----------|-----------|
| Descriptive | Use anchor text that describes the target page |
| Variation | Avoid over-optimization; use natural variation |
| Keyword | Include target keyword when natural |
| Location | Use |
|----------|-----|
| First paragraph | Primary link to related content |
| Body | Contextual links throughout |
| Related/Recommended | End-of-article links |
| Navigation | Key site sections |
| Issue | Fix |
|-------|-----|
| Orphan pages | Add internal links from hub pages or navigation; site-crawlability for technical audit |
| Too many links | Focus on most important; avoid link stuffing |
| Generic anchors | Use descriptive "learn more about X" instead of "click here" |
| Broken links | Audit and fix 404s; see site-crawlability for technical audit |
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take kostja94/internal-links from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.