agentleFS
Starlight-IntelligenceStarlight-Intelligence/starlight-agent-skills/skills/research/mission-page-to-summary/SKILL.md

mission-page-to-summary

Skill1 starsChanged 4 months agoMITView on GitHub

Turn an official mission page (NASA/ESA/JPL spacecraft, instrument, or mission site) into a clean, accurate summary — objective, timeline, instruments, status, and key results. Use when summarizing a space mission, building a mission card, or asked to 'explain this mission' from an agency page.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Mission Page → Summary

An official mission page → a structured, accurate mission summary.

Purpose

Agency mission pages are authoritative but sprawling. This skill distills one into a consistent summary card — objective, key dates, instruments, current status, and headline results — sourced only from the official page, so it's safe to publish or template across a mission catalog.

When it fires

  • Keyword triggers: mission, spacecraft, mission summary, mission card, nasa mission, esa mission
  • File triggers: content/missions/**, *.mission.md
  • Command triggers: /mission-page-to-summary

Inputs

InputRequiredNotes
pageyesOfficial mission/instrument page URL or text.
formatnocard (default) or long.

Workflow

  1. Identify the mission — name, agency, mission type. ✅ Check: official name captured.
  2. Objective — the mission's stated goal, in one or two sentences.
  3. Timeline — launch date, key milestones, end/extended status; only dates the page states.
  4. Instruments/payload — list with one-line purposes.
  5. Status — current operational state as the page reports it.
  6. Key results — notable findings, each attributable to the page.
  7. Source line — link the official page.

Output contract

{
  "name": "string",
  "agency": "string",
  "objective": "string",
  "timeline": [{ "date": "string", "event": "string" }],
  "instruments": [{ "name": "string", "purpose": "string" }],
  "status": "string",
  "key_results": ["string"],
  "source": "string — official URL"
}

Tools & MCP

  • Tools: WebFetch, Read.
  • MCP dependencies: none required.

Quality bar

  • Every date/result is on the official page — no memory-filled gaps.
  • Mission name and agency are correct and official.
  • Status reflects the page, with the page's date noted if available.

Example

Input: a NASA mission page URL → output a populated mission card whose every timeline entry and result links back to that page.


Built on SIP — Starlight Intelligence Protocol Substrate: starlightintelligence.org/protocol v1.1.0 Layers used: [file-contract, attestation, sovereignty] Vertical: starlight-agent-skills · portable capability layer

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.