Mstar Engine Legacy

Community

btspoony

mstar-engine-legacy

Engine-absent safety and historical-field archive: field history, checkout/atomic safety, dispatch/QC invariants. Use only when the host has no CLI/engine (execution state = conversation tracking).

Overview

Publisher	btspoony
Repository	`mstar-harness`
Skill name	`mstar-engine-legacy`
Stars	67
Forks	4
Bundled files	6
License	MIT
Links	Skill source Repository Homepage

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.
6 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by btspoony on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/btspoony/mstar-harness/tree/main/skills/mstar-engine-legacy
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.

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/btspoony/mstar-harness.git /tmp/mstar-harness
mkdir -p .claude/skills
cp -r /tmp/mstar-harness/skills/mstar-engine-legacy .claude/skills/mstar-engine-legacy

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mstar Engine Legacy 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 Mstar Engine Legacy 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 Mstar Engine Legacy 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.

mstar-engine-legacy（条件契约档案 / Engine-absent archive）

Load Order

Follow the host-selected lifecycle authority first; this archive never overrides runtime authorization and names no other mstar-* skill (inbound-only).
条件加载：仅当宿主无 engine 能力时读取本 skill 及其 references —— 无 mstar CLI、无 engine import、engine 约束未激活。engine 约束激活（或宿主含 engine 能力）时不加载：此时运行时 skills 的 engine-check 指针 + 短契约文本为权威。
本 skill 是单一条件归档：承接因 engine 校验而从运行时 skills 中移除的 contract 全文，engine-absent 宿主在此找回完整文本。归档只提供字段历史与安全/流程散文——不提供文件执行路径；engine-absent 宿主的执行状态走对话追踪（no-plan mode）。

Scope

归档被承接的完整契约散文（Task 2 displaced prose 的单一收容处）：
1. status.json v1→v2 字段历史表（字段、severity、lifecycle、jq/flock 示例）与 references/migration-source-shapes.md（root/snapshot/register 历史形状；无执行路径或 live writer）
2. Concurrent-write and checkout safety without recreated claim/bind/transfer APIs
3. 各宿主 QC 座次 N=3/N=1 重述（omp / opencode / cursor / codex / kimi / zcode / dsh）
4. 反递归完整清单（leaf executor checklist、红线、NEVER 规则）
5. Engine-check 样板含义（运行时 skills 中 Engine check (when available) blockquote 的语义与 standalone guarantee 规则）
执行状态边界：engine-absent 宿主无文件执行路径——执行状态 = 对话追踪（no-plan mode），门禁（QC/QA）仍适用；本归档不重建任何文件执行面。
运行时 skills 只保留短指针 + engine-check 命令；完整全文一律在本 skill 的 references/ 中（避免全仓重复）。

Workflow

确认触发条件：宿主无 engine（无 CLI / import；约束未激活）。满足才继续。
按需打开对应 reference（见下表），把其中的历史/安全文本作为参考应用；不用它们重建文件执行路径——执行状态走对话追踪（no-plan mode）。
engine 恢复后回到运行时 skills 的指针契约，停止使用本文件作为权威。

需要	打开
status 字段 / severity / lifecycle / 迁移 / jq-flock 示例	`references/status-field-history.md`
Historical root/snapshot/register shapes, provenance, closure, read aliases and retired rollups	`references/migration-source-shapes.md`
Checkout/atomic safety; no supported writer means report capability, never edit protected state	`references/lease-protocol.md`
各宿主 QC 座次 N=3/N=1 重述	`references/qc-seat-n-restatements.md`
反递归完整清单（leaf checklist + 红线）	`references/anti-recursion-checklists.md`
Engine-check 样板含义与 standalone guarantee 规则	`references/engine-check-boilerplate.md`

Decision Rules

不加载条件：engine 约束激活，或宿主含 engine 能力（mstar CLI / engine import 可用）→ 本 skill 不加载。
归档唯一性：完整契约文本只存在于本文件；不得同时在运行时 skills 重复维护全文（运行时只放指针 + engine-check）。
Inbound-only：运行时 skills 可指向本归档（条件归档指针），本归档永不点名其它 mstar-* skill——指代运行时契约时用中性描述（如 the runtime dispatch rules / the current field reference / the host references）；engine lint 以 roles.loadorder.legacy.archive.reference 强制。
权威性：engine-absent 时，本文件的完整文本是字段历史与安全/流程参考；engine-present 时，运行时 skills + engine 校验是权威，本文件不是。
不改契约语义：承接文本的字段名、severity 枚举、N 规则与反递归清单逐字保留；只做整理与归档（并移除文件执行路径的退役措辞），不重写规则。
无文件执行路径：不得以 status.json / snapshot / lease 文件重建执行状态；engine-absent 宿主的执行状态 = 对话追踪（no-plan mode），门禁（QC/QA）仍适用。

Evidence

正确结果 = references 中的历史/安全文本可独立支撑 engine-absent 宿主的字段查阅与安全判断（执行状态仍走对话追踪）；bun run validation:drift 绿（skill corpus lint 通过）；mstar skill lint skills/mstar-engine-legacy 绿。
回归 = grep 验证运行时 skills 已不再携带被承接的全文（原全文位置只剩指针 / engine-check）。

References

本 skill 的 references（见 When Workflow 表）。
Current execution, issue and lifecycle authority belongs to the runtime field reference and domain operations; this archive supplies history 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 Mstar Engine Legacy AI skill do?

Engine-absent safety and historical-field archive: field history, checkout/atomic safety, dispatch/QC invariants. Use only when the host has no CLI/engine (execution state = conversation tracking).

Why use Mstar Engine Legacy on TypingMind?

Because you install it once and use it with any model. Mstar Engine Legacy 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 Mstar Engine Legacy in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/btspoony/mstar-harness/tree/main/skills/mstar-engine-legacy. 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 Mstar Engine Legacy?

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 Mstar Engine Legacy?

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

Is the Mstar Engine Legacy AI skill free?

Yes. It is published on GitHub by btspoony under the MIT license. 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

Feishu Perm

openclaw

OrganizationPopular

Feishu collaborator and permission workflows. Activate when the user explicitly asks to inspect or change sharing, permissions, or collaborators.

Block Kit

Use proactively for structured or interactive Slack replies, and when asked to author or validate native Slack Block Kit JSON.

1password

Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.

Apple Reminders

List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

mstar-engine-legacy（条件契约档案 / Engine-absent archive）

Load Order

Scope

Workflow

Decision Rules

Evidence

References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now