メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Writes funnel assets step by step from a completed funnel plan. Process covers VSL script, landing page copy, OTO sequences, email nurture, and application page. Use when creating funnel copy after architecture is confirmed, or when you need to write VSL, landing page, or email assets from a defined offer. Run after funnel-plan. Triggers on "write the funnel", "build the funnel assets", "write the VSL", "write the landing page", "write the OTO", "write the email sequence", "build funnel copy".
Full funnel architecture session. Diagnoses your situation, selects the right funnel type, and designs the complete offer stack with price ratios and conversion targets. Use when building a new funnel from scratch, when reviewing an existing funnel architecture, or when you need to define the offer stack before creating assets. Run before funnel-build. Triggers on "design my funnel", "funnel architecture", "what funnel should I build", "funnel strategy", "offer stack design", "plan my funnel", "which funnel type".
Grades a funnel against vetted research benchmarks and produces a scored fix list. Checks offer stack ratios, traffic-funnel match, VSL structure, proof quality, and affiliate readiness. Use when you want to check if a funnel is ready to launch, when conversion is below target, or when you need a structured audit before scaling spend. Triggers on "review my funnel", "grade my funnel", "audit my funnel", "why is my funnel not converting", "funnel not working", "check my funnel", "is my funnel ready".
Quick single-ICP funnel builder. Takes your ICP and offer and produces a complete conversion pathway: landing page copy, lead magnet spec, and 3-email nurture sequence. Use when you need a functional funnel fast without the full architecture session. Triggers on "quick funnel", "simple funnel", "lead magnet funnel", "landing page for", "nurture sequence", "opt-in funnel".
Diagnostic operator for Markster OS. Identifies the constraint brick, runs the Hormozi diagnostic, and routes to the right playbook with context pre-filled. Run this before any other skill.
Seasoned business advisor persona with Socratic style. Use when working on business strategy, opportunity evaluation, resource allocation, risk assessment, quarterly reviews, pricing decisions, market entry, competitive analysis, or any strategic business decision. Challenges assumptions and asks clarifying questions before prescribing solutions. Frameworks include ScaleOS (GOD Engine, 5 Laws), Blue Ocean Strategy, lean startup, and customer development.
| name | markster-os |
| description | 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. |
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.
Ask:
markster-os already installed?Do not jump straight into installation commands.
Explain this in plain language:
Then ask:
"Do you want to review the full Markster OS installation steps now?"
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-osskill from inside the workspace."
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
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-osskill 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
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.
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
learning-loop/inbox/markster-os validate . before claiming the workspace is readymarkster-os skill is the real runtime