connect

Configures workspace, project, and mission context for ContextHub MCP tools.

Updated May 12, 2026
One-click install
npx skills add https://github.com/contexthub-md/marketplace --skill connect-contexthub-md
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connect
Source: https://github.com/contexthub-md/marketplace/tree/main/contexthub/skills/connect
Command: npx skills add https://github.com/contexthub-md/marketplace --skill connect-contexthub-md

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Every ContextHub tool (ch_get_mission, ch_discover_context, ch_ocxp_, etc.) fails with a NO_PROJECT error unless an active workspace, project, and mission context is set first. This Skill walks through that setup so all subsequent ContextHub operations work without manual configuration errors. ## Core Features & Use Cases - Guided Interactive Wizard: Lists workspaces, projects, and missions via ch_list_ tools, auto-selecting when only one option exists and prompting the user otherwise. - Direct Connection Modes: Connect instantly by project name (case-insensitive match) or by project UUID, skipping the wizard. - Session Locking: Calls ch_set_context and ch_connect_session to persist the selected context for the whole session. - Use Case: You open a new Claude Code session and want to resume work on your "brain" project. Run the connect skill with the project name, and it locks the workspace, project, and session in one step. ## Quick Start Ask the AI to connect to your ContextHub project by name, for example: connect to the brain project so all ContextHub tools use that context.

Frequently Asked Questions about connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect to a ContextHub project in Claude Code?

Run the connect skill with no arguments for a guided wizard, or pass a project name or UUID directly. It lists your workspaces and projects, lets you pick, then locks the context with ch_set_context and ch_connect_session.

Why do ContextHub ch_* tools return a NO_PROJECT error?

NO_PROJECT means no active project context has been set for the session. Run the connect skill first to select a workspace and project, after which all ch_* tools will use that context.

Can I connect to a ContextHub project by name instead of UUID?

Yes, pass the project name as an argument and the skill searches your project list with a case-insensitive match. If no match is found, it shows the available projects so you can pick one.

Does the connect skill import new GitHub repositories?

No, connect only works with existing projects already in your workspace. To import a new repository from GitHub, use the /contexthub:import skill instead, then connect to the imported project.

What happens if my workspace has no projects?

The skill stops and tells you no projects were found, directing you to import a GitHub repo first with /contexthub:import. It will not create a project on its own.