manage-studies

Orchestrates study lifecycle operations including registration, status transitions, rendering, and PR validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing a catalog of Markdown-based studies involves many coordinated steps—registration, PDF rendering, Draft/Released transitions, companion decks and notes, catalog synchronization, and CI validation—and doing any of them out of order produces stale artifacts or failed checks. This Skill routes each study lifecycle task to the correct focused skill or script and enforces the shared finishing workflow. ## Core Features & Use Cases - Lifecycle Routing: Maps each task (add, rename, retire, restore, status change, companion management) to its dedicated skill and lifecycle script such as _add_study.py or _set_study_status.py. - Artifact Finalization: Runs _finalize_study_artifacts.py to synchronize catalog entries, companion inventories, search shards, and offline manifests after rendering. - Pre-Review Validation: Commits changes, then validates the committed HEAD with _validate_study_change.py, _verify_studies_index.py, and _verify_companion_outputs.py before opening a labeled PR. - Use Case: When moving a study from Draft to Released, use this Skill to regenerate the PDF without the watermark, refresh the catalog and search artifacts, run reference checks, and open a status-change PR that passes CI verification. ## Quick Start Ask the assistant to transition the study with slug MyStudy from Draft to Released and prepare the validated pull request.

Frequently Asked Questions about manage-studies

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

FAQPage Schema
How do I move a study from Draft to Released status?

Use the set-study-status skill or `_set_study_status.py` with an explicit target state, then regenerate the study PDF with `_regenerate_pdf.py <Slug>` to remove the watermark. Finish with `_finalize_study_artifacts.py --study <Slug>` and the PR validation scripts.

How do I register a new study in the catalog?

Use the add-study skill or `_add_study.py` to create the catalog entry and first draft. Canonical sources live at `Studies/<Slug>/<Slug>.md` or `Applications/<Slug>/<Slug>.md`, and first drafts require an approved proposal issue for validation.

When do I need to regenerate study PDFs after edits?

Regenerate with `_regenerate_pdf.py <Slug>` whenever the canonical Markdown, its status, or an embedded figure changes. Companion-only changes, catalog copy edits, and unused adjacent files do not require a PDF render.

Why does a new technical note not appear in search or offline manifests?

Search and offline discovery use `git ls-files`, so untracked notes are invisible to those builders. Stage the new note with `git add` before running discovery builders, then confirm its entry in `companion-artifacts.json` and the offline manifest.

Can I publish a study directly instead of opening a PR?

No. Normal work ends with a ready-for-review PR; after merge, `publish-site.yml` builds and promotes a coherent release. Do not run the standalone R2 publisher or patch public pointers independently.