Space Signpost logo

Space Signpost

Community
jgsystemsconsulting
space-signpost

Signpost (not a knowledge pack) for the ECSS European space standards: the E-ST-10 system engineering family, the discipline standards a reader commonly mis-cites (radiation is E-ST-10-12, not a RAM standard; software is E-ST-40, not E-ST-70), the M-branch project management standards, the Q-branch product assurance standards, and the sustainability and system documents, with designation, edition, owner, status, and catalogue URL only. Contains no source content. Free process paths are existing NASA packs in this catalogue, named by slug, and are not ECSS clause substitutes. Several needs have no in-repo pack.

Overview

Publisherjgsystemsconsulting
Repositoryjgs-se-knowledge-packs
Skill namespace-signpost
Stars
121
Forks
1
Bundled files
1
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by jgsystemsconsulting on GitHub. Read the source before you install it.

Installation

Install the Space Signpost AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs/tree/main/packs/space-signpost
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs.git /tmp/jgs-se-knowledge-packs
mkdir -p .claude/skills
cp -r /tmp/jgs-se-knowledge-packs/packs/space-signpost .claude/skills/space-signpost
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Space Signpost in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Space Signpost on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Space Signpost is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

ECSS Space Standards: Signpost (pointers only)

This is a signpost, not a knowledge pack. It carries no standards-body content: no reproduced clauses, no normative text, no synthesised summaries of the standards. ECSS documents are free to download after registration on ecss.nl, and ESA holds the copyright with no redistribution grant (ECSS-P-00C clause 5.8), so they are Excluded under this repo's docs/SOURCE-VETTING.md and cannot be reconstituted into a redistributable pack. What this skill does: tell you which document you want, which edition is current, who owns it, and which existing NASA pack covers the process topic. A NASA pack is not the ECSS clause set.

When to use

You are working on a European space programme and need to identify or cite the governing ECSS document: which standard covers system engineering, which covers software, which covers dependability, and which free NASA pack covers the process topic. ECSS rows route you to the catalogue. NASA rows route you to an in-repo pack. Several needs have no in-repo pack, and those rows send you to the catalogue only.

Prerequisites: none, plain Markdown.

How to use

Find your document below. The Status column says whether it can be packaged:

  • Excluded: free personal download after registration on ecss.nl; ESA copyright; no redistribution grant. Cannot be packaged here. Buy or download from the owner after registering.
  • Open: an in-repo NASA pack covers the process topic. The Designation cell names the slug, and the Status cell reads Open. The pack is US Government work, public domain in the US (17 U.S.C. § 105). It is not the ECSS clause set.

Editions were confirmed on ecss.nl product pages on 2026-10-14. E-ST-10-12C is radiation methods, not RAM. E-ST-40C Rev.1 is software. E-ST-70C is ground systems and operations. Do not quote a date this file does not print. Where a public URL slug disagrees with the page title, the Title cell says so and the URL is copied as fetched. A reader who needs a designation not listed here goes to https://ecss.nl/standards/active-standards/ .

System engineering (E-ST-10 family)

DesignationTitleEditionOwnerStatusURL
ECSS-E-ST-10C Rev.1System engineering general requirements. Free process ground: nasa-se-handbook, nasa-npr-7123, depth nasa-se-expanded. NASA SE Engine and life cycle, not the ECSS clause set.Rev.1, 15 February 2017ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-10c-rev-1-system-engineering-general-requirements-15-february-2017/
ECSS-E-ST-10-02C Rev.1Verification. Free process ground: nasa-se-handbook, nasa-npr-7123. No ECSS verification programme DRDs, and NASA does not publish this as a standalone verification standard.Rev.1, 1 February 2018ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-10-02c-rev-1-verification-1-february-2018/
ECSS-E-ST-10-06CTechnical requirements specification. Free process ground: nasa-se-handbook and requirements-writing. Not an ECSS-format technical specification standard.Issue C, 6 March 2009ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-10-06c-technical-requirements-specification/
ECSS-E-ST-10-24C Rev.1Interface management. Free process ground: nasa-se-handbook, handbook-level, not an ECSS interface control standard.Rev.1, 15 November 2024ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-10-24c-rev-1-interface-management-15-november-2024/
ECSS-E-ST-10-04C Rev.1Space environment. No in-repo pack. Catalogue URL only.Rev.1, 15 June 2020ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-10-04c-rev-1-space-environment-15-june-2020/
ECSS-E-ST-10-12CMethods for the calculation of radiation received and its effects, and a policy for design margins. Not a RAM methods standard. RAM is Q-ST-30. No in-repo pack.Issue C, 15 November 2008; Corr.1 22 February 2017ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-10-12c-methods-for-the-calculation-of-radiation-received-and-its-effects-and-a-policy-for-design-margins/

Discipline engineering, not the RAM standard and not the software standard

These five are the designations a reader commonly mis-cites. E-ST-10-12 in the table above is radiation methods, not RAM. E-ST-70C in this table is ground systems and operations, not the software standard. The software standard is E-ST-40C Rev.1, last row.

DesignationTitleEditionOwnerStatusURL
ECSS-E-ST-32C Rev.1Structural general requirements. No structures pack. Catalogue URL only.Rev.1, 15 November 2008ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-32c-rev-1-structural-general-requirements/
ECSS-E-ST-33-01C Rev.2Mechanisms. No mechanisms pack. Catalogue URL only.Rev.2, 1 March 2019ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-33-01c-rev-2-1-march-2019-space-engineering-mechanisms/
ECSS-E-ST-50C Rev.2Communications. No RF, telemetry, or telecommand pack. The public URL slug still says rev-1. The page title is Rev.2. Copy the slug as fetched.Rev.2, 5 December 2024ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-50c-rev-1-communications-5-december-2024/
ECSS-E-ST-70CGround systems and operations. Not the software standard. No ground-segment pack. Catalogue URL only.Issue C, 31 July 2008ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-70c-ground-systems-and-operations/
ECSS-E-ST-40C Rev.1Software. This is the software standard. Free process ground: nasa-npr-7150 (NASA software engineering requirements, Classes A-F). Not the ECSS-E-ST-40 process text. Software product assurance is Q-ST-80, in the product assurance table.Rev.1, 30 April 2025ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-40c-rev-1-software-30-april-2025/

Project management (M branch)

The active management branch is exactly these five documents. M-ST-80C cancels the earlier M-00-03 lineage; that lineage is not a current designation and has no row here.

DesignationTitleEditionOwnerStatusURL
ECSS-M-ST-10C Rev.1Project planning and implementation. Free process ground: nasa-se-handbook, nasa-npr-7123. NASA phase labels differ from ECSS project phases.Rev.1, 6 March 2009ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-m-st-10c-rev-1-project-planning-and-implementation/
ECSS-M-ST-10-01COrganization and conduct of reviews. No product-page URL was verified. The URL is the management filter. Free process ground: nasa-se-handbook, nasa-npr-7123. Review names are NASA-specific.Issue C, 15 November 2008ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standards/active-standards/management/
ECSS-M-ST-40C Rev.1Configuration and information management. Free process ground: nasa-se-handbook, crosscutting CM, not an EIA-649-depth standard. No standalone NASA CM pack slug.Rev.1, 6 March 2009ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-m-st-40c-rev-1-configuration-and-information-management/
ECSS-M-ST-60CCost and schedule management. Free process ground splits: nasa-ceh for cost estimating, nasa-schedule for schedule. Neither is the ECSS cost and schedule standard.Issue C, 31 July 2008ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-m-st-60c-cost-and-schedule-management/
ECSS-M-ST-80CRisk management. Cancels the earlier M-00-03 lineage. Free process ground: nasa-risk. NASA risk taxonomy, not the ECSS clause text.Issue C, 31 July 2008ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-m-st-80c-risk-management/

Product assurance (Q branch)

Dependability is Q-ST-30C Rev.1, not E-ST-10-12C. E-ST-10-12C is radiation methods.

DesignationTitleEditionOwnerStatusURL
ECSS-Q-ST-10C Rev.1Product assurance management. No NASA product assurance management pack. Nearest culture pointer is nasa-system-safety, and it is not a PA programme equivalent.Rev.1, 15 March 2016ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-q-st-10c-rev-1-product-assurance-management-15-march-2016/
ECSS-Q-ST-20C Rev.2Quality assurance. No QA pack. Catalogue URL only.Rev.2, 1 February 2018ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-q-st-20c-rev-2-quality-assurance-1-february-2018/
ECSS-Q-ST-30C Rev.1Dependability. This is the RAM methods parent. Not E-ST-10-12. Free process ground: nasa-rm-standard, nasa-pra, nasa-fault-management. Not the ECSS Q-30 programme clauses.Rev.1, 15 February 2017ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-q-st-30c-rev-1-space-product-assurance-dependability-15-february-2017/
ECSS-Q-ST-30-02CFailure modes, effects (and criticality) analysis (FMEA/FMECA). Free process ground: nasa-pra, nasa-fault-management, nasa-rm-standard. No dedicated FMEA handbook pack.Issue C, 6 March 2009ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-q-st-30-02c-failure-modes-effects-and-criticality-analysis-fmeafmeca/
ECSS-Q-ST-40C Rev.1Safety. Free process ground: nasa-system-safety. NASA system safety handbook framing, not the ECSS safety programme standard.Rev.1, 15 February 2017ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-q-st-40c-rev-1-safety-15-february-2017/
ECSS-Q-ST-80C Rev.2Software product assurance. Partial pointer only: nasa-npr-7150 is engineering requirements, not a software product assurance standard.Rev.2, 30 April 2025ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-q-st-80c-rev-2-software-product-assurance-30-april-2025/

Sustainability, system description, and two optional rows

Four required rows, then two optional rows. Both optional rows ship, because a reader who asks for human factors or integrated product support will otherwise get silence.

DesignationTitleEditionOwnerStatusURL
ECSS-U-AS-10C Rev.2Adoption notice of ISO 24113, space debris mitigation requirements. Listed on the sustainability filter. No verified product-page URL, so the URL is the filter. Free process ground: nasa-std-8719-14. That pack is NASA orbital debris process limits, not ISO 24113 text and not this adoption notice.Rev.2, 9 February 2024ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standards/active-standards/sustainability/
ECSS-U-ST-20CPlanetary protection. No planetary protection pack. Catalogue URL only.Issue C, 1 August 2019ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-u-st-20c-space-sustainability-planetary-protection/
ECSS-S-ST-00C Rev.2Description, implementation and general requirements. System document, not a discipline standard. No NASA equivalent. Catalogue URL only.Rev.2, 21 November 2025ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-s-st-00c-rev-2-description-implementation-and-general-requirements-21-november-2025/
ECSS-P-00C Rev.1Standardization objectives, policies and organization. Policy source for the copyright clause (clause 5.8). Listed on the system-implementation filter. No verified product-page URL, so the URL is the filter. No NASA equivalent.Rev.1, 15 November 2024ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standards/active-standards/ecss-system-implementation/
ECSS-E-ST-10-11CHuman factors engineering. Edition date was not opened. The URL is the engineering filter, not an invented product page. Free process ground: nasa-hsi. NASA HSI process, not the ECSS human factors standard.listed active; product page not opened 2026-10-14ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standards/active-standards/engineering/
ECSS-I-ST-30-10CIntegrated Product Support (IPS). The public URL slug is mis-prefixed ecss-e-. The designation on the page is I-ST. Copy the slug as fetched. No IPS pack. I-branch (industrialization) was announced 20 March 2025.Issue C, 15 November 2024ECSS (catalogue: ecss.nl)Excludedhttps://ecss.nl/standard/ecss-e-st-30-10c-15-november-2024-integrated-product-support-ips/

Free NASA paths

Every row names one real in-repo slug. Every Status cell reads Open. No ECSS row in this table. Edition cells say (pack pin) where this signpost does not itself pin the NASA document revision.

DesignationTitleEditionOwnerStatusURL
nasa-se-handbookE-ST-10, E-ST-10-02, E-ST-10-06, E-ST-10-24, M-ST-10, M-ST-10-01, M-ST-40. NASA SE process model, not ECSS clauses.NASA/SP-2016-6105 Rev 2NASAOpenpacks/nasa-se-handbook/
nasa-npr-7123Same SE and project-planning needs, as the requirements NPR. Not ECSS.NPR 7123.1 (pack pin)NASAOpenpacks/nasa-npr-7123/
nasa-se-expandedDepth layer for E-ST-10 only. Pair with the handbook. Not ECSS.NASA/SP-2016-6105-SUPPL Vol 1NASAOpenpacks/nasa-se-expanded/
nasa-riskM-ST-80. Not the ECSS risk clause text.NASA risk management handbook (pack pin)NASAOpenpacks/nasa-risk/
nasa-rm-standardQ-ST-30 and Q-ST-30-02. Not ECSS Q-30 programme clauses. Not a dedicated FMEA standard.NASA-STD-8729.1NASAOpenpacks/nasa-rm-standard/
nasa-praQ-ST-30 and Q-ST-30-02. Not ECSS Q-30 programme clauses. Not a dedicated FMEA standard.NASA PRA procedures guide (pack pin)NASAOpenpacks/nasa-pra/
nasa-fault-managementQ-ST-30 and Q-ST-30-02. Not ECSS Q-30 programme clauses. Not a dedicated FMEA standard.NASA fault management handbook (pack pin)NASAOpenpacks/nasa-fault-management/
nasa-system-safetyQ-ST-40. Also the nearest culture pointer for Q-ST-10, and not a PA programme equivalent.NASA system safety handbook (pack pin)NASAOpenpacks/nasa-system-safety/
nasa-npr-7150E-ST-40 engineering requirements. Partial only for Q-ST-80. Not a software product assurance standard.NPR 7150.2 (pack pin)NASAOpenpacks/nasa-npr-7150/
nasa-cehCost half of M-ST-60. Not the ECSS cost and schedule standard. No separate cost-estimating pack exists in this catalogue.NASA cost estimating handbook (pack pin)NASAOpenpacks/nasa-ceh/
nasa-scheduleSchedule half of M-ST-60. Not the ECSS cost and schedule standard.NASA schedule management handbook (pack pin)NASAOpenpacks/nasa-schedule/
nasa-std-8719-14Debris analogue for U-AS-10. Not ISO 24113.NASA-STD-8719.14 (pack pin)NASAOpenpacks/nasa-std-8719-14/
nasa-hsiE-ST-10-11 process ground. Not the ECSS human factors standard.NASA HSI practitioner guide (pack pin)NASAOpenpacks/nasa-hsi/

Scope & Limits

  • No reproduced standards text. Rows carry designation, title, edition, owner, status, and URL only.
  • ECSS rows are Excluded. Free after registration is not a redistribution grant.
  • NASA rows are Open and name real in-repo slugs. They are process-topic analogues. They do not replace ECSS clause text, European customer-supplier DRDs, or contractual tailoring.
  • E-ST-10-12C is radiation methods, not RAM. Dependability is Q-ST-30C Rev.1.
  • E-ST-70C is ground systems and operations, not software. Software is E-ST-40C Rev.1.
  • No in-repo pack covers structures, mechanisms, communications, ground systems and operations, space environment, radiation methods, planetary protection, product assurance management, or quality assurance.
  • No dedicated cost-estimating pack exists in this catalogue beyond nasa-ceh. Schedule is nasa-schedule.
  • The communications URL slug says rev-1. The page title is Rev.2. The IPS URL slug is mis-prefixed ecss-e-. Both URLs are copied as fetched.
  • se-standards-signpost keeps a shorter ECSS list with no editions. This pack is the edition-pinned map. Do not treat the two lists as the same document.

Signpost content is original JG Systems Consulting Ltd. work, MIT licensed. Trademarks and standard designations are named for identification only.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Space Signpost AI skill do?

Signpost (not a knowledge pack) for the ECSS European space standards: the E-ST-10 system engineering family, the discipline standards a reader commonly mis-cites (radiation is E-ST-10-12, not a RAM standard; software is E-ST-40, not E-ST-70), the M-branch project management standards, the Q-branch product assurance standards, and the sustainability and system documents, with designation, edition, owner, status, and catalogue URL only. Contains no source content. Free process paths are existing NASA packs in this catalogue, named by slug, and are not ECSS clause substitutes. Several needs h...

Why use Space Signpost on TypingMind?

Because you install it once and use it with any model. Space Signpost is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Space Signpost in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs/tree/main/packs/space-signpost. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Space Signpost?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Space Signpost?

As many as you like. As long as a model supports skills, you can use Space Signpost with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Space Signpost AI skill free?

It is published on GitHub by jgsystemsconsulting. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇