internal-links▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Guides internal linking strategy for SEO: crawlability, link equity distribution, and user navigation.
SEO On-Page: 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.
Scope (On-Page SEO)
- Internal links: Contextual links; descriptive anchor text; related posts; hub pages
- Breadcrumbs: Implement for large sites (e.g. ecommerce); see breadcrumb-generator
Initial Assessment
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:
- Site structure: Hub pages, pillar content, supporting pages
- Orphan pages: Pages with no or few internal links
- Priority pages: Pages that need more link equity
Best Practices
Link Structure
| 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 |
Anchor Text
| Principle | Guideline |
|---|---|
| Descriptive | Use anchor text that describes the target page |
| Variation | Avoid over-optimization; use natural variation |
| Keyword | Include target keyword when natural |
Placement
| Location | Use |
|---|---|
| First paragraph | Primary link to related content |
| Body | Contextual links throughout |
| Related/Recommended | End-of-article links |
| Navigation | Key site sections |
Common Issues
| 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 |
Output Format
- Internal link audit (if auditing)
- Link opportunities for key pages
- Anchor text recommendations
- Structure improvements
Related Skills
- article-page-generator: Related posts, contextual links, end-of-article recommendations
- website-structure: Plan page structure and hierarchy; informs internal linking
- site-crawlability: Internal links enable crawling
- url-structure: URL structure affects link patterns
- content-strategy: Topic clusters inform link structure; pillar <-> cluster; cluster <-> cluster
- breadcrumb-generator: Breadcrumbs are internal links; category hierarchy
How to use internal-links on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add internal-links
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches internal-links from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate internal-links. Access the skill through slash commands (e.g., /internal-links) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★35 reviews- ★★★★★Mei Harris· Dec 20, 2024
We added internal-links from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Arjun Gupta· Dec 16, 2024
I recommend internal-links for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Sofia Sharma· Dec 4, 2024
Useful defaults in internal-links — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Mei Zhang· Nov 11, 2024
internal-links reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sakura Liu· Oct 2, 2024
Registry listing for internal-links matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Rahul Santra· Sep 17, 2024
internal-links is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Arya Agarwal· Sep 5, 2024
internal-links is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Anika Ndlovu· Aug 24, 2024
Keeps context tight: internal-links is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Pratham Ware· Aug 8, 2024
Keeps context tight: internal-links is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yash Thakker· Jul 27, 2024
internal-links has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 35