different-ai/openwork-hub
18 skills39 installs522 starsGitHub
Install
npx skills add https://github.com/different-ai/openwork-hubSkills in this repo
1Owpenbot TestExecutes the owpenbot and openwrk integration test script, auto-detecting repos and seeding Telegram config from test tokens. A developer uses it to run these Telegram bot integration tests.3installs2ScreenpipeProvides API and CLI commands to query Screenpipe's OCR and audio-transcription history running locally on port 3030. A developer uses it to search what appeared on screen or was said, filtered by app, window, or time.3installs3Skill CreatorScaffolds self-buildable OpenCode skills, emphasizing specific trigger phrases in the description and safe credential handling. A developer uses it after completing a flow to turn it into a reusable skill.3installs4Agent CreatorGuides creating OpenCode agents via opencode agent create, with a minimal markdown-plus-frontmatter template and default gpt-5.2-codex model. A developer uses it when adding a project or global subagent to an OpenCode setup.2installs5Command CreatorGuides authoring OpenCode custom commands in commands/*.md with frontmatter and prompt templates supporting $ARGUMENTS, shell output, and file includes. A developer uses it to add repeatable slash commands to an OpenCode project or global config.2installs6Create Cal Com LinkAutomates Cal.com link creation using bundled scripts to make a schedule, remove default availability, add a window, and time-box an event type. A developer uses it to generate a booking link for a specific person or team over a limited date range.2installs7Get StartedScripts the OpenWork get-started flow, printing four fixed welcome lines and then navigating to a requested site with the Chrome DevTools MCP. A developer or user triggers it when saying get started in OpenWork.2installs8Mcp ArchDocuments the MCP wiring between the OpenWork UI, OpenCode SDK, and OpenWork server, and provides steps to fix config, directory, and OAuth token errors. A developer uses it when debugging MCP architecture, config, or auth issues in OpenWork.2installs9Openwork Chrome Mcp TestingRequires Chrome MCP verification of OpenWork UI flows, especially any feature touching remote behavior, with snapshot and console-log evidence. A developer uses it as a non-negotiable gate before merging remote-behavior changes.2installs10Openwork Docker Chrome McpBoots the OpenWork Docker dev stack with dev-up.sh and drives a real UI chat flow through a Chrome MCP tool recipe to confirm a response renders. A developer uses it to test the real OpenWork flow end-to-end locally.2installs11Plugin CreatorGuides authoring OpenCode plugins as JS/TS modules, showing project vs global directories, npm plugin loading in opencode.json, and a minimal plugin template. A developer uses it when adding a plugin to extend OpenCode with hooks.2installs12Research DocDrafts a research/YYYY-MM-DD-topic.md file from a summary/key-points/findings/sources template and commits and pushes it. A developer uses it when saying hey research to capture a topic into the repo.2installs13Sandbox Lifecycle FastlaneProvides a one-command preflight and worktree setup for OpenWork sandbox lifecycle tasks, then defers to the Docker plus Chrome MCP end-to-end flow. A developer uses it when a sandbox is stuck or when starting sandbox-lifecycle work.2installs14Sync SubmodulesWalks through inspecting dirty state, stashing inside a dirty submodule, pulling the root, and updating submodules to pinned commits. A developer uses it when submodule update fails or local changes would be overwritten by checkout.2installs15TelegramSends Telegram bot notifications using credentials from a gitignored config and chat aliases resolved from telegram-chats.json. A developer uses it to push notifications or alerts to specific Telegram chats.2installs16Workspace GuideIntroduces OpenWork as a GUI for OpenCode, tailoring onboarding to technical or non-technical users and linking install and config docs. A developer or user uses it as the workspace welcome and setup guide.2installs17Worktree Ux PrRebases per-task worktrees on origin/dev, verifies the changed UI surface via Chrome MCP, and attaches screenshot evidence to the PR via upload and comment scripts. A developer uses it for one-PR-per-worktree UX changes with screenshot proof.2installs18Worktree WorkflowRequires each file-changing task to begin in a dedicated worktree, with scripts for starting the worktree and committing/pushing after each chunk. A developer uses it to keep tasks isolated with frequent commits and pushes.2installs