How do I install the Jpl Explorer 1 skill?

Run npx skillmds@latest add blencorp/jpl-explorer-1 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jpl Explorer 1 safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jpl Explorer 1?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jpl Explorer 1 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jpl Explorer 1?

blencorp (@blencorp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jpl Explorer 1 by blencorp — Agent Skill

Name: Jpl Explorer 1
Author: blencorp

Jpl Explorer 1

Builds NASA Jet Propulsion Laboratory public-facing interfaces with Explorer 1 Vue components or compiled framework-neutral assets. Use for JPL products authorized to use Explorer 1, not generic NASA or spacecraft-operations tools.

blencorp bdb7761 4 files · 5.5 KB Updated Sep 17, 2026

File contents

NASA JPL Explorer 1

Build within the system's documented scope and delivery model.

Before editing

Confirm the product owner and that this system is authorized for the target surface.
Read references/implementation.md before installing or changing dependencies.
Read references/sources.md when checking versions, provenance, license, or release state.
Inspect the existing framework, package manager, asset pipeline, and accessibility tests. Preserve them unless the official integration requires a change.

Workflow

Choose one documented delivery path; do not mix compiled, source, CDN, and framework-wrapper paths accidentally.
Pin the dependency or downloaded asset version and keep upstream notices.
Reuse official components, tokens, content guidance, and templates before adding custom UI.
Extend through documented tokens, properties, slots, Sass settings, or composition. Do not edit vendored package files.
Test semantic structure, keyboard operation, focus order and visibility, accessible names, error recovery, zoom/reflow, contrast, and target browsers.
Report custom patterns, unsupported requirements, and upstream gaps explicitly.

Boundaries

Scope: JPL public-facing products governed by Explorer 1. Route spacecraft-operations tools to Stellar and NASA-wide modernization work to Horizon when appropriate.
Release: active official repository and published packages.
Delivery: Vue component library plus compiled shared assets for HTML or other frameworks.
Do not invent component APIs, tokens, package names, or compliance claims.
Do not import another jurisdiction's branding to fill a gap.
A passing component example does not prove the completed service conforms to WCAG, Section 508, the ADA, or local policy.

References

Implementation — packages, setup, and integration decisions
Sources — authoritative URLs, snapshot versions, ownership, and license notes

---name: jpl-explorer-1description: Builds NASA Jet Propulsion Laboratory public-facing interfaces with Explorer 1 Vue components or compiled framework-neutral assets. Use for JPL products authorized to use Explorer 1, not generic NASA or spacecraft-operations tools.---# NASA JPL Explorer 1Build within the system's documented scope and delivery model.## Before editing1. Confirm the product owner and that this system is authorized for the target surface.2. Read [references/implementation.md](references/implementation.md) before installing or changing dependencies.3. Read [references/sources.md](references/sources.md) when checking versions, provenance, license, or release state.4. Inspect the existing framework, package manager, asset pipeline, and accessibility tests. Preserve them unless the official integration requires a change.## Workflow1. Choose one documented delivery path; do not mix compiled, source, CDN, and framework-wrapper paths accidentally.2. Pin the dependency or downloaded asset version and keep upstream notices.3. Reuse official components, tokens, content guidance, and templates before adding custom UI.4. Extend through documented tokens, properties, slots, Sass settings, or composition. Do not edit vendored package files.5. Test semantic structure, keyboard operation, focus order and visibility, accessible names, error recovery, zoom/reflow, contrast, and target browsers.6. Report custom patterns, unsupported requirements, and upstream gaps explicitly.## Boundaries- **Scope:** JPL public-facing products governed by Explorer 1. Route spacecraft-operations tools to Stellar and NASA-wide modernization work to Horizon when appropriate.- **Release:** active official repository and published packages.- **Delivery:** Vue component library plus compiled shared assets for HTML or other frameworks.- Do not invent component APIs, tokens, package names, or compliance claims.- Do not import another jurisdiction's branding to fill a gap.- A passing component example does not prove the completed service conforms to WCAG, Section 508, the ADA, or local policy.## References- [Implementation](references/implementation.md) — packages, setup, and integration decisions- [Sources](references/sources.md) — authoritative URLs, snapshot versions, ownership, and license notes

Frequently asked questions