ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

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 approve a full Markster OS installation.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/atiti/markster-os
Or

Markster OS

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:

Metadata

Author@atiti
Stars4473
Views0
Updated2026-05-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-atiti-markster-os": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.