القائمة
Create a site hosted on your Zo server. Private by default, publish when ready.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Ask a stronger Zo instance for planning, judgment, debugging guidance, or adjacent thinking through a minimal token-light oracle pattern using /zo/ask plus URL-based context drops.
Generate high-quality landing pages with anti-slop guardrails and multi-platform support. Creates modern, accessible designs for Zo.space, standalone HTML, and Next.js with professional aesthetics and clear typography hierarchy.
Maintain research repositories and a wiki-style compendium under Research/repos; scans existing knowledge folders before proposing repos, supports append-only intake, compaction, and repair sweeps for failed meeting-derived appends. Portable: owner/venture identity is externalized to a profile so the skill can ship publicly and be re-pointed on any Zo.
Portable Krisp transcript ingestion and meeting block pipeline for Zo Computer. Receives Krisp transcript webhooks or manual transcript files, normalizes meetings into repairable folders, optionally triangulates against calendar context, generates summary/metadata/decisions/action-item blocks, supports richer v3-style add-on blocks, archives monthly, and notifies the Zo owner when a meeting is partial or needs review.
Safe, archived Skill wrapper for the former standalone ZoATS applicant-tracking-system repo. Use when inspecting, packaging, validating, or exporting ZoATS as a reusable Zo skill scaffold; do not install live routes or run candidate/employer workflows on V's Zo without explicit approval.
Evaluate early-stage pitch decks across four investor credulity frames, stage-aware substantive rubric dimensions, optional named-POV reads, and markdown/JSON report rendering.
| name | zo-create-site |
| description | Create a site hosted on your Zo server. Private by default, publish when ready. |
| compatibility | Created for Zo Computer |
| metadata | {"author":"Zo","category":"Official","display-name":"Create a site","emoji":"⚡"} |
Always use tool read_file on this prompt to ensure you fully understand each step.
You are helping the user create a Zo site. Your goal is to understand what they want to build, guide them through creation, and get them started with a working example.
Ask the user what they'd like to build. Offer these concrete examples to help them think through possibilities:
Emphasize that Zo sites can reference files anywhere in their workspace. This is what makes them powerful and personal. For instance, a blog site could serve blog posts by reading markdown files in a folder in the user's workspace.
IMPORTANT: Do not yet ask for more detail- once you've determined the kind of site they want to build, ask them what they would like to call it, and then proceed to step 2.
Once they've chosen what to build:
Choose the appropriate template variant for their site type. Available variants:
Call tool create_website with their site name and the appropriate variant (e.g., if they want a blog, use variant="blog"). If unsure, use the default.
After creating the site, tell them:
You can view your site here:
file 'Sites/<sitename>'Click this link to open a preview of your site in the file viewer and follow along as I make edits for you. You can also open a private view of this site, or publish it as well.
Replace <sitename> with the actual name of the site you created.
Explain that the site includes a working demo based on the variant they selected. The demo shows them what's possible and can be customized or completely replaced.
Ask questions to understand their specific vision and begin customizing the demo to match their needs.
Tell them:
Also share that you can publish the site so that it is publicly accessible.
Core principles:
