workspace-guide_skill

This skill guides new OpenWork users through setup, usage, and onboarding workflows, highlighting practical steps and benefits.

TypeScript

186

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill different-ai/agent-bank --skill workspace-guide

SKILL.md1.6 KB

Overview

This skill is a workspace guide that introduces OpenWork and helps onboard new users to a CLI-first banking-for-agents environment. It explains differences for technical and non-technical users, outlines how to enable skills and plugins, and points to where configuration and integrations live. The goal is quick orientation so users can start working with files and AI-assisted automation confidently.

How this skill works

The guide asks an initial preference question to tailor the explanation to technical or non-technical users. For non-technical users it explains how to add files, request summaries, or generate checklists. For technical users it shows how OpenWork maps to OpenCode, where to install and configure providers, and how to add skills, plugins, and external tool servers via configuration files.

When to use it

Onboard a new teammate to OpenWork and explain core workflows.
Show non-technical users how to safely work with files and get AI summaries.
Help developers connect OpenWork to OpenCode and external providers.
Decide whether to add skills, plugins, or MCP servers for extra capabilities.
Reference when configuring models, API keys, or opencode.json integrations.

Best practices

Start by asking whether the user is technical or non-technical to tailor guidance.
Keep sensitive files restricted to only the workspace areas you trust.
Install and configure providers in OpenCode before starting complex sessions.
Install skills from the Skills tab and add plugins via opencode.json for reproducibility.
Document any MCP servers or external tools you add to opencode.json for team visibility.

Example use cases

A new hire who needs a simple walkthrough: show how to drop files and ask for summaries.
A project manager who wants weekly checklists and document drafts generated from workspace files.
A developer integrating model providers and API keys via OpenCode, then running sessions in OpenWork.
An automation lead adding a scheduling plugin to trigger routines from workspace prompts.
Next actions to try: Ask 'Are you more technical or non-technical?' and then 'Summarize the files in this workspace.'

FAQ

No. Non-technical users can upload files and ask the AI to summarize, organize, or draft content. Technical users get extra options for provider and plugin configuration.

Where do I configure model providers and plugins?

Install and configure providers in OpenCode, then use the Skills tab or opencode.json and the Plugins tab to add skills and plugins. Keep opencode.json under version control for reproducible setups.