smithery/official-moondao

lunar-missions-expert

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

Installation

$ npx skills add smithery/official-moondao --skill lunar-missions-expert

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/official-moondao.

npx skills add smithery/official-moondao

Browse all from smithery/official-moondao

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,339 B
  • docs SUMMARY.md 141 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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: missionid, landerid, payloadids, launchdate, 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 landerid or payloadids 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.