relocate-study-companion

Renames or moves study companion notes and decks while updating Markdown links.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/raghavamohan/AnalyticMadhyasthDarshan --skill relocate-study-companion-raghavamohan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: relocate-study-companion
Source: https://github.com/raghavamohan/AnalyticMadhyasthDarshan/tree/main/.cursor/skills/relocate-study-companion
Command: npx skills add https://github.com/raghavamohan/AnalyticMadhyasthDarshan --skill relocate-study-companion-raghavamohan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Renaming or moving a technical note, deck, or Presenter's Companion between studies breaks relative Markdown links, image references, and deck associations. This Skill automates the relocation so owned paths and inbound links stay consistent without manual edits. ## Core Features & Use Cases - Rename or Move Companions: Rename a note or deck in place, or move it to another existing study, using Scripts/_relocate_study_companion.py with dry-run preview before any writes. - Link Repair: Rebase relative Markdown image and document links and repair inbound links to moved paths, while shared figures stay in their original location. - Deck Chain Handling: Move a deck together with its declared slides, notes paths, and linked Presenter's Companion chain while retaining stable deck IDs. - Use Case: You want to move Deck.pptx from Source-Study to Target-Study and rename it Teaching.pptx; run the script with --dry-run, review the plan, then rerun with --yes and regenerate affected PDFs and decks. ## Quick Start Ask the assistant to rename or move a study companion file, for example to move Deck.pptx from one study to another with a dry-run preview first.

Frequently Asked Questions about relocate-study-companion

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

FAQPage Schema
How do I rename or move a study companion file?

Run Scripts/_relocate_study_companion.py with the source study and file, plus --to-name for a rename or --to-study for a move. Start with --dry-run to review the full plan, then repeat with --yes to apply the changes.

How do I move a deck and its Presenter's Companion to another study?

Move the owning deck with --to-study; the script includes the deck's declared slides, notes paths, and linked Presenter's Companion chain automatically. A presenter-only rename stays beside its deck and cannot move between studies alone.

Does moving a note break existing Markdown links?

No. The script rebases relative Markdown image and document links and repairs inbound links to moved paths. Shared figures remain in place, and changed canonical Markdown receives a current Edited-on timestamp.

What happens if the target filename already exists?

Occupied or unsafe targets fail before any writes occur. The dry-run output shows the complete plan so you can resolve conflicts before committing the move.

When should I use rename-study instead of this skill?

Use rename-study for a whole-study slug or title rename. This skill is only for renaming or moving individual companion files such as notes, decks, and Presenter's Companions within or between existing studies.