Skip to content
cccskills
FreePublished on GitHub

openwork-connect

Find and use skills, shared tools, and connected services available in an OpenWork organization. Match a requested outcome to an available capability, run it with the required parameters, and explain any connection or permission steps.

OriginalShow the original description

Search and use the skills, MCP connections, and connected services available through the user's OpenWork organization.

See how to install

Good for

  • Finding skills available within an OpenWork organization
  • Searching shared tools and connected services by intended outcome
  • Running available OpenWork Cloud operations
  • Checking next steps for authentication and permission issues

Files included (1)

  • SKILL.md1.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

OpenWork Connect

Use the OpenWork MCP server when the user asks for an organizational skill, shared MCP tool, connected service, or OpenWork Cloud operation.

Skills

  1. Call list_skills to see every skill the member may use; no keywords are needed. Pass query only to narrow a long catalog.
  2. Call get_skill with the skill's name or exact capability, read the whole returned SKILL.md, then follow it.

Workflow

  1. Call search_capabilities with a short description of the outcome unless the exact capability name is already available in the current context.
  2. Select an exact capability name from the search result.
  3. Call execute_capability with that exact name and only the parameters required for the requested outcome.
  4. If OpenWork returns a connection, authentication, permission, or admin setup state, relay that state and its next action accurately. Do not claim that an unavailable capability ran.

Search results reflect the signed-in member's organization, grants, teams, and connection readiness. Do not infer access from a capability that was visible in another organization or an earlier authorization context.

OpenWork Connect performs OAuth through the MCP client. Never request, embed, or persist OpenWork access tokens in plugin files or chat content.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

add-a-feature

FreeSummary

Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.

  • Registering a feature before implementation
  • Releasing a feature to selected organizations
  • Separating cloud and self-hosted availability
different-ai/openwork24.2KUpdated Oct 18, 2026

Connect OpenCode browser tools to a locally running OpenWork Electron app to inspect its UI, enter a task, and check the response. This skill supports exploration and debugging through CDP, Chrome's remote control protocol.

  • Connecting browser tools to a local Electron development app
  • Inspecting screen state during debugging
  • Entering a task in the composer and running it
different-ai/openwork24.2KUpdated Oct 18, 2026

Check added lines in a change for information identifying customers, prospects, partners, or outside individuals. Report locations and generic remediation without reproducing identities, and escalate cases where the information is already public.

  • Checking changes for customer and partner identities
  • Reviewing documents and test data for identifying details
  • Reporting disclosure locations without repeating identities
different-ai/openwork24.2KUpdated Oct 18, 2026

Connects supported AI clients, including Claude Code and Codex, to OpenWork through MCP, a protocol for accessing external tools. It guides account sign-in and verifies that tools for finding and running organization capabilities are available.

  • Connecting an AI client to OpenWork organization resources
  • Signing in and verifying available MCP tools
  • Switching organizations or troubleshooting authentication
different-ai/openwork24.2KUpdated Oct 18, 2026

Review an outside contributor’s pull request before running its code. Identify concealed behavior, obfuscated code, risky dependencies, and build hooks, with file locations and specific checks for maintainers to follow up.

  • Screening an outside contributor’s pull request before execution
  • Checking encoded code and unexplained network calls
  • Reviewing dependency changes and installation scripts
different-ai/openwork24.2KUpdated Oct 18, 2026

create-plugin

FreeSummary

Create an OpenCode plugin for OpenWork with custom tools and hooks, which run code at specific events. The skill builds the plugin file and adds its entry to the project configuration.

  • Adding custom tools to OpenWork
  • Creating a plugin to save and list notes
  • Running custom code before or after tool execution
different-ai/openwork24.2KUpdated Oct 18, 2026

See all skills by different-ai

Report a problem with this skill