Skill Desk One Technical Guide

← Documentation

Skill Desk One — Technical Guide

Purpose: provide a neutral Skills workspace that recommends, validates, packages, and routes portable AI Skills without making one AI provider a hard dependency.

Core Components

  • Skills Catalog: indexes local and approved Skill definitions.
  • Active Workspace: stores the selected Skill stack and workspace preferences.
  • Safety Preflight: checks Skill files for malformed metadata, secret-like material, prompt-injection patterns, privileged/destructive instructions, and risky network/filesystem behavior.
  • Prompt Builder: produces target-ready prompts with safety, evidence, confirmation, and read-only instructions.
  • AI Target Layer: opens the user’s own ChatGPT, Claude, Microsoft Copilot, GitHub Copilot, Cursor, Gemini, or Codex account. Skill Desk One does not pay model API costs for this bring-your-own-account workflow.
  • Release Center: WordPress + WPWriter is the primary path for pages, documentation, and release-state updates. When CarrySkills engine/plugin code changes, use a versioned package with SHA-256 integrity, backup, health verification, and a last-known-good rollback point.

State & Privacy

Workspace preferences are browser-local unless explicitly persisted by the product. v1.43 stores minimal Mission Session health in sd1_mission_session_state_v143: mission/Skill identifiers, origin, nonce-present flag, session status, and timestamp. v1.52 adds the Founder OS assumption store founder_os_watchlist_v1, containing only device-local assumption text, evidence-needed text, review date, and created timestamp; watch items can be promoted into Custom Missions and are included in the portable workspace backup/import/restore path. Neither store places Founder evidence, Company Memory, or private buyer text in the SD1 return URL. Release backups include safe Skill Desk One state while credential-like keys are excluded from state snapshots.

Release Rule

For page/UI/documentation releases, production upgrades follow: edit through WPWriter → verify the live WordPress page → synchronize documentation/release state → record the release. For CarrySkills engine/plugin changes, use: build versioned ZIP → syntax/integrity validation → SHA-256 checksum → preserve last-known-good package/state → install/activate → health check → rollback if needed. WPVibe is backup only and is not part of the normal SD1/Founders deployment path.

Release Center: /skills-releases/   •   Engine updater/status: /skills-update/