workspace-guide
$
npx mdskill add different-ai/openwork/workspace-guideGuides new users through OpenWork workspace setup and onboarding
- Helps users understand how to interact with OpenWork based on technical proficiency
- Uses question tool to determine user's technical background
- Provides tailored instructions for file management and automation
- Directs users to skills, plugins, and configuration resources
SKILL.md
.github/skills/workspace-guideView on GitHub ↗
--- name: workspace-guide description: Workspace guide to introduce OpenWork and onboard new users. --- # Welcome to OpenWork Hi, I'm Ben and this is OpenWork. It's an open-source alternative to Claude's cowork. It helps you work on your files with AI and automate the mundane tasks so you don't have to. Before we start, use the question tool to ask: "Are you more technical or non-technical? I'll tailor the explanation." ## If the person is non-technical OpenWork feels like a chat app, but it can safely work with the files you allow. Put files in this workspace and I can summarize them, create new ones, or help organize them. Try: - "Summarize the files in this workspace." - "Create a checklist for my week." - "Draft a short summary from this document." ## Skills and plugins (simple) Skills add new capabilities. Plugins add advanced features like scheduling or browser automation. We can add them later when you're ready. ## If the person is technical OpenWork is a GUI for OpenCode. Everything that works in OpenCode works here. Most reliable setup today: 1) Install OpenCode from opencode.ai 2) Configure providers there (models and API keys) 3) Come back to OpenWork and start a session Skills: - Install from the Skills tab, or add them to this workspace. - Docs: https://opencode.ai/docs/skills Plugins: - Configure in opencode.json or use the Plugins tab. - Docs: https://opencode.ai/docs/plugins/ MCP servers: - Add external tools via opencode.json. - Docs: https://opencode.ai/docs/mcp-servers/ Config reference: - Docs: https://opencode.ai/docs/config/ End with two friendly next actions to try in OpenWork.
More from different-ai/openwork
- browser-setup-devtoolsGuide users through browser automation setup using Chrome DevTools MCP only. Use when the user asks to set up browser automation, Chrome DevTools MCP, browser MCP, or runs the browser-setup command.
- daytona-electron-testTest the real Electron app on Daytona: create sandbox, start services, connect via CDP, create workspaces, drive sessions, and verify settings. Use when the user says 'test on Daytona', 'run the app on Daytona', 'Daytona dry run', 'test Electron remotely', or 'reproduce on Daytona'.
- get-startedGuide users through the get started setup and Chrome DevTools demo.
- opencode-bridgeBridge between OpenWork UI and OpenCode runtime
- opencode-mirrorMaintain the local OpenCode mirror for self-reference
- opencode-primitivesReference OpenCode docs when implementing skills, plugins, MCPs, or config-driven behavior.
- openwork-coreCore context and guardrails for OpenWork native app
- openwork-debugDebug OpenWork sidecars, config, and audit trail
- openwork-orchestrator-npm-publish|
- run-evalsRun OpenWork UI evals on a Daytona sandbox or local Electron instance. Handles sandbox creation, service startup, and eval execution via CDP browser tools.