Mission page to summary

Skill frankxai/starlight-agent-skills/skills/research/mission-page-to-summary

Portable Starlight substrate skills for agent runtimes, SIS, ACOS, and cross-agent workflow activation.

Install

npx -y skills add frankxai/starlight-agent-skills --skill mission-page-to-summary

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.7 KB, 562 tokens by cl100k_base, as published. Nobody here has run it

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

Input	Required	Notes
`page`	yes	Official mission/instrument page URL or text.
`format`	no	`card` (default) or `long`.

Workflow

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