Openwork Core
Orient agents and contributors inside the OpenWork Tauri native app: OpenCode mirror, dev commands, SQLite session data, and UI guardrails for non-technical users.
Overview
openwork-core is an agent skill most often used in Build (also Ship launch prep) that orients work on the OpenWork native app with OpenCode integration, Tauri workflows, and UI guardrails.
Install
npx skills add https://github.com/different-ai/openwork --skill openwork-coreWhat is this skill?
- Requires reading AGENTS.md, VISION.md, PRINCIPLES.md, PRODUCT.md, and ARCHITECTURE.md before behavior changes
- Documents OpenCode CLI spawn pattern: opencode -p prompt -f json -q and SQLite mirror at ~/.opencode/opencode.db (sessio
- Desktop and mobile dev entrypoints: pnpm tauri dev, ios dev, android dev, plus vendor/opencode fast-forward pull workflo
- Guardrails: stay within OpenCode tool surface, use Tauri commands for system access, keep UI at 60fps, mobile needs Xcod
- Directs stack specifics to the tauri-solidjs skill and self-reference via vendor/opencode
- 3 SQLite tables called out: sessions, messages, history
- 6 orientation docs required before behavior changes
Adoption & trust: 546 installs on skills.sh; 15.9k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are modifying OpenWork and need the official orientation—OpenCode mirror, Tauri dev flows, database tables, and tool-surface limits—without breaking non-technical UX expectations.
Who is it for?
Maintainers and indie builders hacking the OpenWork Tauri/OpenCode desktop or mobile client who need repo-specific constraints before touching features.
Skip if: Greenfield apps unrelated to OpenWork, pure web-only SPAs without Tauri, or tasks that need capabilities outside OpenCode’s documented tool surface.
When should I use this skill?
Changing OpenWork native app behavior, integrating OpenCode CLI or database, or running Tauri desktop/iOS/Android development workflows in the OpenWork repo.
What do I get? / Deliverables
You follow documented read order, dev commands, CLI and SQLite integration patterns, and Tauri-only system access so changes stay compatible with OpenCode and performant on desktop and mobile.
- Aligned implementation within OpenCode tool surface
- Correct Tauri dev/build command usage
- Documented use of OpenCode CLI JSON mode and local DB tables
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
OpenWork-core is the canonical onboarding shelf when you are building the agent-facing desktop and mobile shell and wiring OpenCode capabilities. Agent-tooling fits because the skill defines how the product exposes plans, permissions, tools, and OpenCode CLI/database integration—not generic app marketing.
Where it fits
Wire a new UI flow that surfaces OpenCode session progress without adding tools outside the OpenCode surface.
Debug reading ~/.opencode/opencode.db history when reconciling agent file changes with the desktop shell.
Run pnpm tauri ios dev or android dev and confirm platform studio prerequisites before a mobile release candidate.
Fast-forward vendor/opencode and verify CLI spawn flags still match production session logging expectations.
How it compares
Repo orientation skill for OpenWork contributors—not a general Tauri tutorial and not an MCP server catalog entry.
Common Questions / FAQ
Who is openwork-core for?
Developers working on the OpenWork native app who must align with OpenCode capabilities, Tauri commands, and product principles before implementing features.
When should I use openwork-core?
At the start of Build tasks in the OpenWork repo, when setting up tauri dev or mobile targets, when integrating OpenCode CLI/SQLite, and during Ship when validating platform-specific builds—not for unrelated product ideas.
Is openwork-core safe to install?
It describes shell, database, and file workflows; review the Security Audits panel on this Prism page and treat opencode CLI and local SQLite access as sensitive on your machine.
SKILL.md
READMESKILL.md - Openwork Core
## Quick Usage (Already Configured) ### Orientation - Read `AGENTS.md`, `VISION.md`, `PRINCIPLES.md`, `PRODUCT.md`, and `ARCHITECTURE.md` before changing behavior. - Ensure `vendor/opencode` exists for self-reference. - Use the `tauri-solidjs` skill for stack-specific guidance. ### Update the OpenCode mirror ```bash git -C vendor/opencode pull --ff-only ``` ### Development workflow ```bash pnpm tauri dev # Desktop development pnpm tauri ios dev # iOS development pnpm tauri android dev # Android development # Or run directly in the desktop package: pnpm -C packages/desktop tauri dev ``` ## OpenCode Integration ### Spawn OpenCode CLI ```bash opencode -p "your prompt" -f json -q ``` ### Read OpenCode database ``` ~/.opencode/opencode.db # SQLite database ``` ### Key tables - `sessions` — Task runs - `messages` — Chat messages and tool calls - `history` — File change tracking ## Common Gotchas - OpenWork must stay within OpenCode's tool surface; avoid inventing new capabilities. - Always expose plans, permissions, and progress for non-technical users. - Use Tauri commands for all system access (file, shell, database). - Keep UI at 60fps; avoid blocking the main thread. - Mobile builds require platform-specific setup (Xcode, Android Studio). ## UI Principles - **Slick and fluid**: animations, transitions, micro-interactions. - **Mobile-first**: touch targets, gestures, adaptive layouts. - **Transparency**: show plans, steps, and tool calls. - **Progressive disclosure**: hide advanced controls until needed. ## First-Time Setup (If Not Configured) ### Clone the OpenCode mirror ```bash git clone https://github.com/anomalyco/opencode vendor/opencode ``` ### Initialize Tauri project ```bash pnpm create tauri-app . --template solid-ts ``` ### Add mobile targets ```bash pnpm tauri ios init pnpm tauri android init ``` ## Common Gotchas - OpenWork must stay within OpenCode’s tool surface; avoid inventing new capabilities. - Always expose plans, permissions, and progress for non-technical users. ## First-Time Setup (If Not Configured) ### Clone the OpenCode mirror ```bash git clone https://github.com/anomalyco/opencode vendor/opencode ```