script-registry

Maintain a registry of R Markdown script inputs, outputs, and paper targets.

148|30|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/aspi6246/Claude-Code-Skills-for-Academics --skill script-registry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: script-registry
Source: https://github.com/aspi6246/Claude-Code-Skills-for-Academics/tree/main/script-registry
Command: npx skills add https://github.com/aspi6246/Claude-Code-Skills-for-Academics --skill script-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents research workflows from drifting by making every Code/*.Rmd script’s inputs, outputs, and paper targets explicit so you can find the right script and update it safely.

Core Features & Use Cases

  • Single source of truth: Maintains a per-script registry YAML block (purpose, inputs, outputs, paper_target, notes) and derives a centralized Code/REGISTRY.md view.
  • Dependency-aware discovery: Lets you answer “which script makes X” and quickly locate overlap by purpose/keywords/output filenames and paper targets.
  • Drift detection with guardrails: Flags undeclared inputs/outputs and unused registry entries by comparing YAML metadata to actual I/O calls, without auto-editing.
  • Workflow integration: Supports new script creation, registry refresh (“update registry”), and safe retirement by moving scripts into Code/_Archive/.

Quick Start

Run the builder to refresh Code/REGISTRY.md after editing the registry block for your Code/*.Rmd, then use “which script makes X” to confirm downstream impact.

Frequently Asked Questions about script-registry

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

FAQPage Schema
How do I track R Markdown script dependencies to prevent research pipeline drift?▼

To track R Markdown script dependencies, maintain a per-script registry YAML block declaring inputs, outputs, and paper targets, then run the builder to synchronize a centralized REGISTRY.md view and flag drift.

What is the best way to find which R Markdown script produces a specific output file?▼

Finding which R Markdown script produces a specific output file requires querying a centralized REGISTRY.md index, which maps declared script inputs, outputs, and paper targets for dependency-aware discovery.

How do I document data lineage for research workflows using R Markdown?▼

Document data lineage for research workflows by adding a registry YAML frontmatter block to R Markdown scripts specifying purpose, inputs, outputs, and paper targets, then compiling the metadata into REGISTRY.md.

Can I detect undeclared inputs or outputs in my R Markdown research scripts?▼

Yes, you can detect undeclared inputs or outputs by comparing the actual I/O calls in R Markdown scripts against the declared registry YAML metadata, which flags mismatches without auto-editing the code.

How do I safely archive R Markdown scripts without breaking downstream research targets?▼

To safely archive R Markdown scripts without breaking downstream research targets, check the registry dependencies first, then move the retired scripts into the Code/_Archive/ directory and refresh REGISTRY.md.

Does this script registry approach work for managing multiple paper tables and figures?▼

Yes, this script registry approach works for managing multiple paper tables and figures by explicitly mapping each R Markdown script's output to its corresponding paper_target within the registry YAML metadata.