refine-studies-index

Review and update the Studies landing page through its generator script and catalog sources.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a generated landing page consistent is hard: the HTML is built from a Python template, prose is shared with a README, and catalog descriptions live in JSON registries. This Skill guides reviews and edits of the Studies index so every change is made at the correct source of truth and verified with the right rebuild and test commands. ## Core Features & Use Cases - Structured editorial review: Walks the page section by section (hero, navigation, Start here path, catalog, contribution flow) with concrete editorial checks on voice, status labels, and comparison framing. - Source-of-truth editing: Directs changes to Scripts/_build_studies_index.py, Studies/README.md, and proposal-registry.json instead of hand-editing generated HTML or catalog JSON. - Rebuild and verification workflow: Provides the exact commands to rebuild the index, finalize artifacts, verify output, and run glossary, reader, and CI-related tests. - Use Case: When updating a study's catalog description or refreshing the landing page copy, follow this Skill to edit the right files, regenerate artifacts, and confirm README, catalog JSON, and generated HTML stay synchronized. ## Quick Start Review the Studies landing page and report prioritized improvements without editing any files.

Frequently Asked Questions about refine-studies-index

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

FAQPage Schema
How do I update a generated landing page without editing the HTML directly?

Edit the HTML/CSS/JavaScript shell inside the generator script's template (Scripts/_build_studies_index.py INDEX_TEMPLATE), then rerun the build script to regenerate Studies/index.html. Never hand-edit the generated HTML file.

How do I change a study's catalog description stored in JSON?

Load the study's row with the catalog helper module, update the description field, and call write_studies_catalog. Do not hand-edit catalog JSON files; ongoing-study descriptions live in proposal-registry.json instead.

Should I regenerate PDFs when only landing page copy changes?

No. Do not refresh a study's Edited on timestamp or regenerate its PDF when only landing-page prose or catalog-card wording changes. PDF regeneration follows the normal study workflow only when the study markdown itself changes.

What checks should run after rebuilding a static site index?

Run the index builder, artifact finalizer, and index verifier, then compile-check the build script and inspect git diff and status. Also confirm navigation targets exist, status labels are correct, and README tables agree with catalog JSON.

Can landing page changes be committed directly to the main branch?

No. Create a feature branch before changing any file under Studies/, and use a normal feature PR for landing-page and root-catalog changes. Apply a study-specific label only if files under a study directory also change.