lunar-missions-expert

Specialized skill for tracking lunar mission timelines, manifests, and mission status within the LORS framework.

⭐3stars🔀1forks📁View on GitHub🕐Updated Jan 1, 2026⬇️1downloads

When & Why to Use This Skill

The Lunar Missions Expert skill is a specialized tool designed to track and manage comprehensive lunar mission data within the LORS framework. It excels at organizing mission timelines, payload manifests, and status updates by cross-referencing data across missions, rovers, and landers. By ensuring data integrity and providing source attribution to official reports like NASA CLPS, it serves as a centralized intelligence hub for lunar exploration documentation and space mission tracking.

Use Cases

  • Payload Manifest Mapping: Creating detailed associations between payload IDs, lander units, and specific missions to track every item delivered to the lunar surface.
  • Mission Timeline & Status Tracking: Maintaining an accurate chronological log of launch dates, target landing sites, and real-time status transitions for lunar expeditions.
  • Cross-Referential Data Integrity: Automatically verifying and linking technical specifications between rovers, landers, and mission files to ensure a consistent and navigable knowledge base.
  • Source-Verified Documentation: Linking mission updates and manifest changes to official NASA CLPS reports or provider press releases for high-fidelity record keeping.
namelunar-missions-expert
descriptionSpecialized skill for tracking lunar mission timelines, manifests, and mission status within the LORS framework.

Lunar Missions Expert Skill

Domain Knowledge

  • File: LUNAR_MISSIONS.MD (Index)
  • Primary Data Sources:
    • missions/ (individual mission files with YAML metadata)
    • rovers/ (rover details)
    • landers/ (lander details)
  • Metadata Format: YAML blocks with fields: mission_id, lander_id, payload_ids, launch_date, status, target_site.

Instructions

  1. Manifest Data Collection: Create detailed mappings of payload IDs to lander IDs and mission IDs, capturing all items delivered to the surface.
  2. Timeline Data Tracking: Maintain an accurate log of launch dates, target landing sites, and actual landing coordinates.
  3. Outcome Documentation: Collect and document mission success metrics and status transitions.
  4. Source Attribution: Link entries to official mission reports, NASA CLPS updates, or provider press releases to verify status change and manifest items.
  5. Cross-Referential Integrity: Always verify if lander_id or payload_ids have corresponding files in landers/ or rovers/. If so, ensure the Markdown body contains relative links (e.g., [Lander Name](../landers/FILE.MD)) to those files.