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
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
1---2name: mission-page-to-summary3description: 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.4---56# Mission Page → Summary78> An official mission page → a structured, accurate mission summary.910## Purpose1112Agency mission pages are authoritative but sprawling. This skill distills one into13a consistent summary card — objective, key dates, instruments, current status, and14headline results — sourced only from the official page, so it's safe to publish or15template across a mission catalog.1617## When it fires1819- Keyword triggers: `mission`, `spacecraft`, `mission summary`, `mission card`,20 `nasa mission`, `esa mission`21- File triggers: `content/missions/**`, `*.mission.md`22- Command triggers: `/mission-page-to-summary`2324## Inputs2526| Input | Required | Notes |27|-------|----------|-------|28| `page` | yes | Official mission/instrument page URL or text. |29| `format` | no | `card` (default) or `long`. |3031## Workflow32331. **Identify the mission** — name, agency, mission type. ✅ Check: official name captured.342. **Objective** — the mission's stated goal, in one or two sentences.353. **Timeline** — launch date, key milestones, end/extended status; only dates the page states.364. **Instruments/payload** — list with one-line purposes.375. **Status** — current operational state as the page reports it.386. **Key results** — notable findings, each attributable to the page.397. **Source line** — link the official page.4041## Output contract4243```json44{45 "name": "string",46 "agency": "string",47 "objective": "string",48 "timeline": [{ "date": "string", "event": "string" }],49 "instruments": [{ "name": "string", "purpose": "string" }],50 "status": "string",51 "key_results": ["string"],52 "source": "string — official URL"53}54```5556## Tools & MCP5758- Tools: `WebFetch`, `Read`.59- MCP dependencies: none required.6061## Quality bar6263- [ ] Every date/result is on the official page — no memory-filled gaps.64- [ ] Mission name and agency are correct and official.65- [ ] Status reflects the page, with the page's date noted if available.6667## Example6869Input: a NASA mission page URL → output a populated mission card whose every70timeline entry and result links back to that page.7172---7374Built on SIP — Starlight Intelligence Protocol75Substrate: starlightintelligence.org/protocol v1.1.076Layers used: [file-contract, attestation, sovereignty]77Vertical: starlight-agent-skills · portable capability layer
frankxai