get-started

$npx mdskill add different-ai/openwork/get-started

Guides users through setup and Chrome DevTools demo

  • Helps users begin with pre-configured tools and setup
  • Relies on Chrome DevTools for navigation and interaction
  • Triggers actions based on specific user commands like 'go on google.com'
  • Provides step-by-step responses and confirms site navigation

SKILL.md

.github/skills/get-startedView on GitHub ↗
---
name: get-started
description: Guide users through the get started setup and Chrome DevTools demo.
---

## When to use

- Always load this skill when the user says "get started".

## What to do

- Reply with these four lines, exactly and in order:

  1) hey there welcome this is openwork
  2) we've pre-configured you with a couple tools
  3) Get Started
  4) write "hey go on google.com"

## Then

- If the user writes "go on google.com" (or "hey go on google.com"), use the chrome-devtools MCP to open the site.
- After the navigation completes, reply: "I'm on <site>" where <site> is the final URL or page title they asked for.

More from different-ai/openwork

SkillDescription
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'.
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.
shadcnManages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".