register-doc-sources

Updated Jan 31, 2026

Search Tags:#automation #documentation #config #cursor #register #urls #handles

Ready to run

npx skills add https://github.com/doesitscript/dotfile-vnext --skill register-doc-sources

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: register-doc-sources
Source: https://github.com/doesitscript/dotfile-vnext/tree/main/.cursor/skills/register-doc-sources
Command: npx skills add https://github.com/doesitscript/dotfile-vnext --skill register-doc-sources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Registers user-provided remote documentation URLs into the project's Cursor configuration so they are available as mapped @doc handles and processed for the current session.

Core Features & Use Cases

Merge new docs into existing Cursor config without removing existing entries.
Deduplicate by URL and process URLs immediately for the current run.
Generate kebab-case doc handles from URLs and provide @doc mappings for easy referencing.

Quick Start

Run the register-doc-sources skill to add your doc URLs to .cursor/config.json and process them for the current session.

Frequently Asked Questions about register-doc-sources

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add remote documentation URLs to Cursor config for indexing?▼

To add remote documentation URLs to Cursor config, register them to merge new entries into .cursor/config.json without deleting existing ones. The URLs are deduplicated and processed for immediate use in the current session.

What is the process for mapping @doc handles to documentation in Cursor?▼

Mapping @doc handles involves generating kebab-case identifiers from your registered remote documentation URLs. This creates easy-to-reference @doc mappings within your project Cursor configuration for immediate activation.

Can I merge new documentation sources without overwriting existing Cursor config entries?▼

You can merge new documentation sources without overwriting existing Cursor config entries. The registration process safely updates .cursor/config.json by adding new URLs and deduplicating them, preserving your previously mapped @doc handles.

Does registering documentation URLs in Cursor require an existing config file?▼

Registering documentation URLs in Cursor does not require an existing config file. The process can read or create .cursor/config.json as needed, ensuring your remote docs are mapped and available even in a fresh project setup.

Why are my newly registered documentation URLs not available in the current Cursor run?▼

Newly registered documentation URLs should be available immediately because the registration process processes URLs for the current run. If they are not, ensure the URLs were successfully merged and deduplicated into the .cursor/config.json file.