remove-study

Removes a study directory and synchronizes catalogs, proposal metadata, and references.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Retiring a study by hand leaves broken catalog entries, stale proposal-registry rows, and dead links across the site. This Skill runs the repository's removal script so the study directory, catalog JSON, README rows, references, and pipeline metadata are all updated together. ## Core Features & Use Cases - Complete study removal: Deletes the full Studies/<Slug>/ or Applications/<Slug>/ directory and removes its catalog entry from JSON, README, and the rebuilt index. - Metadata cleanup: Clears the slug from proposal-registry.json, presentation-pipeline.json, and companion-pipeline.json, including metadata-only cleanup when the directory was already deleted. - Reference maintenance: For published studies, removes the References README row, MANIFEST block, and by-tag citations while preserving citations to other studies. - Use Case: An Ongoing placeholder study is abandoned; run the script with --dry-run to preview, then --yes to delete the directory, catalog row, and registry entry in one step. ## Quick Start Ask the assistant to remove the study with slug 'The-Ontology-of-Coexistence' using the remove-study script, starting with a dry run to preview the changes.

Frequently Asked Questions about remove-study

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

FAQPage Schema
How do I remove a study from the Studies catalog?

Run `python Scripts/_remove_study.py <Slug>` from the repo root, using the slug without extension. The script deletes the study directory and updates the catalog JSON, Studies README, rebuilt index, and proposal registry in one operation.

How can I preview study removal before deleting files?

Use the `--dry-run` flag: `python Scripts/_remove_study.py <Slug> --dry-run`. This previews every deletion and metadata change without modifying anything, and `--yes` skips the interactive confirmation when you proceed.

Can I remove an Ongoing placeholder study that has no published PDF?

Yes, Ongoing placeholders are supported. The script removes the placeholder's directory, its italic catalog row, and its proposal-registry entry, without touching the References files that only apply to published studies.

What happens if the study directory was already deleted manually?

The script supports metadata-only cleanup. Run it with the same slug using `--dry-run` then `--yes`; it removes the surviving entries in proposal-registry.json and the pipeline JSON files without rewriting reference catalogs.

Why does CI fail after removing a study?

CI rejects any remaining Markdown links to the retired slug and unknown Start here slugs. Remove or retarget cross-links in the same PR, update INDEX_TEMPLATE if needed, then run _finalize_study_artifacts.py and _check_references.py.

When should I not use the whole-study removal script?

Do not use it to delete individual companion notes or decks while keeping the parent study. For that, use the remove-study-companions skill; _remove_study.py is exclusively for retiring the entire study and all its companions.