Markster OS

Lightweight guide and router for Markster OS. Use to explain the system, point users to the full Git-backed workspace setup, and help them decide whether to...

Security Scan

This is an instruction-only bootstrap skill whose declared purpose (guide and router for Markster OS) matches its content and it requires no credentials or installs; it sensibly asks for explicit user approval before cloning, running installers, or pushing to remotes.

Purpose & Capability

Name, description, and runtime instructions align: the skill is a lightweight marketplace entrypoint that explains Markster OS and routes users to a Git-backed install. It does not request unrelated binaries, env vars, or system paths.

Instruction Scope

SKILL.md keeps scope narrow and repeatedly requires explicit user approval before cloning, running install.sh, attaching remotes, or pushing. Note: the documented actions (git clone + bash install.sh, markster-os CLI) will execute third-party code from the GitHub repo if the user approves; that is expected but requires the user to review that code before consenting.

Install Mechanism

No install specification or bundled code is provided by the marketplace package — it's instruction-only. The recommended install path uses a public GitHub repo (https://github.com/markster-public/markster-os), which is a standard and reviewable source.

Credentials

The skill requests no environment variables, credentials, or config paths. It does instruct the user to attach a Git remote and push only after explicit approval; those actions would use the user's existing Git/SSH credentials but are not requested by the skill itself.

Persistence & Privilege

always is false and the skill is user-invocable. There is no indication the skill tries to persist itself or alter other skills or global agent settings. Autonomous invocation is allowed by default but the skill's instructions emphasize asking the user before any potentially privileged actions.

Assessment

This package is coherent and acts as a safe bootstrap guide, but you should not approve any install or Git operations without inspection. Before consenting: review the GitHub repository and specifically inspect install.sh and any installer scripts; consider cloning locally and reading the code rather than piping to a shell; run installs in a sandbox or disposable environment if possible; ensure any Git remote URL is correct and that you understand what will be pushed; never provide secrets or env vars to the skill — it does not request them. If you are unsure, decline the automated install and perform the steps manually after review.

This is the marketplace bootstrap variant of markster-os.

Do not pretend this package is the full operating system.

Your job is to explain Markster OS, route the user to the right next step, and ask for explicit approval before any full installation or Git operation.

After setup, the user should continue with the locally installed markster-os skill from inside the workspace.

---

First check

Ask:

1. Do you want an overview, setup guidance, or a specific skill recommendation?
2. Is markster-os already installed?
3. Are you already inside a Markster OS workspace?

Do not jump straight into installation commands.

---

If the user wants an overview

Explain this in plain language:

• Markster OS is the full open-source GTM operating system
• this ClawHub package is only the lightweight marketplace entrypoint
• the full system lives in the GitHub repository and uses a Git-backed workspace
• the workspace stores the company context, learning loop, playbooks, and validation rules

Then ask:

"Do you want to review the full Markster OS installation steps now?"

---

If the user wants setup guidance

Do not run commands immediately.

First say:

"I can guide you through the full Markster OS installation. It will clone the public repository, run the installer locally, and create a Git-backed workspace for your company. Do you want to approve that full Markster OS installation?"

Only continue if the user explicitly says yes.

If the user approves, direct them to SETUP.md and summarize the steps before running anything.

Be explicit:

"This marketplace package is only the bootstrap entrypoint. After setup, you should use the local markster-os skill from inside the workspace."

---

If the CLI is not installed and the user approved full installation

Use the reviewable install path from SETUP.md:

git clone https://github.com/markster-public/markster-os.git
cd markster-os
bash install.sh

After install, use:

markster-os doctor

Then install the local runtime skills:

markster-os install-skills

---

If the user wants the full operating system and has approved setup

Create a Git-backed workspace:

markster-os init <company-slug> --git --path ./<company-slug>-os
cd ./<company-slug>-os

Then guide them through:

markster-os start
markster-os validate .

Then say:

"Markster OS is now installed locally. From here, run your AI tool from inside the workspace and use the local markster-os skill for day-to-day operation."

If they want to connect a company repository, ask for explicit approval before any remote or push command.

Only after approval, suggest:

markster-os attach-remote <git-url>

If they also approve the first push, suggest:

git push -u origin main

---

If the user only needs public skills

Use:

markster-os list-skills
markster-os install-skills
markster-os install-skills --skill <skill-name>

Do not invent skill names. List first, then ask for approval before installing additional skills.

---

If the user is already inside a workspace

Use the CLI instead of guessing:

markster-os status
markster-os start
markster-os validate .

If the workspace is missing hooks:

markster-os install-hooks

If the user wants to sync, commit, or push, ask first.

Only after approval, suggest:

markster-os sync
markster-os commit -m "docs(context): update workspace"
markster-os push

---

Rules

• treat the upstream GitHub repo as the product source, not as the live company workspace
• treat the company workspace as the place where business context lives
• keep raw notes in learning-loop/inbox/
• use markster-os validate . before claiming the workspace is ready
• if a specialized public skill is needed, list skills first and install explicitly only after user approval
• do not claim native OpenClaw integration beyond the documented setup flow
• do not run install, remote, or push commands without explicit user approval
• make the handoff explicit: after setup, the local markster-os skill is the real runtime