super-jarvis-lantern-os

Inspect Lantern OS repository state and produce evidence-backed update plans.

3|5|Updated May 26, 2026
One-click install
npx skills add https://github.com/alex-place/lantern-os --skill super-jarvis-lantern-os
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: super-jarvis-lantern-os
Source: https://github.com/alex-place/lantern-os/tree/main/skills/super-jarvis-lantern-os
Command: npx skills add https://github.com/alex-place/lantern-os --skill super-jarvis-lantern-os

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a single canonical operator entrypoint for Lantern OS, unifying repo inspection, safe routing, evidence tracking, and release-ready validation across the project.

Core Features & Use Cases

  • Repo control and validation: Inspect repository state, make minimal safe changes, and verify results before shipping.
  • Reporting and artifacts: Support Markdown-first report workflows, PDF validation, and evidence-backed recordkeeping.
  • Operational governance: Route work across Bayesian confidence, wallet and archive boundaries, device and server constraints, and legacy reference material.

Quick Start

Use the super-jarvis-lantern-os skill to inspect the current Lantern OS repository state and produce a safe, evidence-backed update plan.

Frequently Asked Questions about super-jarvis-lantern-os

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inspect a Lantern OS repository state before shipping changes?

Lantern OS repo inspection requires frontmatter discovery to evaluate repository state and produce an evidence-backed update plan. It classifies evidence and applies minimal-change execution to validate results before shipping any modifications.

What is evidence-backed workflow control for repository operations?

Evidence-backed workflow control routes Lantern OS operations using Bayesian confidence to ensure safe repository updates. It classifies evidence, applies minimal-change execution, and validates results before shipping across wallet, archive, device, and server boundaries.

How do I generate Markdown reports and validate PDF artifacts for Lantern OS?

Generate Markdown-first report workflows and validate PDF artifacts through evidence classification and recordkeeping. This operational governance ensures all Lantern OS updates maintain evidence-backed documentation before shipping.

Does Lantern OS workflow routing support legacy skill and archive boundaries?

Lantern OS workflow routing supports legacy reference material, wallet and archive boundaries, and device or server safety checks. It uses Bayesian confidence to route operational work safely across these distinct project constraints.

What are the limitations of minimal-change execution for repository validation?

Minimal-change execution limits repository modifications by requiring frontmatter discovery, evidence classification, and validation before shipping. It enforces safe routing across device and server constraints, preventing unverified changes to Lantern OS.

Can I use Bayesian confidence for device and server safety checks in Lantern OS?

Bayesian confidence enables device and server safety checks by providing probabilistic evidence-backed workflow routing for Lantern OS. It ensures operational governance by validating repository state and constraints before shipping changes.