Connector Setup

Plan a safe, least-privilege way to connect the user's real tools (Drive, Slack, a task board, a calendar, etc.) to Claude so it works from live data instead of copy-paste. Use when wiring up connectors/MCP. Works for any stack and any role.

114 stars 1 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add DylXBT/claude-orchestrator-skills --skill connector-setup
Manual install
git clone --depth 1 https://github.com/DylXBT/claude-orchestrator-skills.git /tmp/claude-orchestrator-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-orchestrator-skills/connector-setup ~/.claude/skills/connector-setup

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Connector Setup

Most people are the integration layer — copy-pasting between tabs to give Claude what it needs. Connectors (MCP) let Claude read the tools you already use and work from live context. This skill plans that safely, one source at a time.

It does **not** assume a stack. Ask what the user actually uses.

## Step 1 — Interview

1. **What's your stack?** The tools where your work and information actually live.
2. **Where's the friction worst?** Where do you copy-paste the most? That's the first source to connect — usually a document store or a task board.
3. **What does one real task need to read?** Be specific. "This week's activity in the marketing folder", not "all of Drive".

## Step 2 — Connect with least privilege

For the chosen source, produce a connection plan:

- **Scope:** the minimum access a task needs — read-only where possible, a single folder/channel/project rather than the whole account.
- **What it can and can't see**, stated plainly so the user can sanity-check it.
- **How to connect it** in their agent (the connector/MCP server for that tool, or the native integration).

Grant access to exactly what a task needs, nothing more. Intent over convenience.

## Step 3 — Run one real task on live data

Have the user ask Claude to do one genuine task that pulls from the connected source — no pasting, no exporting. Confirm it's reading **current** data (check a fact that changed recently).

## Step 4 — Fold it in
Read the full skill on GitHub

Details

Skill name
connector-setup
Path
connector-setup/SKILL.md
License
MIT
Repo updated
2 June 2026

FAQ

What does the Connector Setup skill do?

Plan a safe, least-privilege way to connect the user's real tools (Drive, Slack, a task board, a calendar, etc.) to Claude so it works from live data instead of copy-paste. Use when wiring up connectors/MCP. Works for any stack and any role.

How do I install the Connector Setup skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add DylXBT/claude-orchestrator-skills --skill connector-setup. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Connector Setup popular?

It lives in DylXBT/claude-orchestrator-skills, which has 114 GitHub stars and 1 forks.

Related skills

Context Brain

114

DylXBT/claude-orchestrator-skills

Build a reusable context pack (a "brain") so Claude reasons from the user's role, audience, voice, and standards every time, instead of generic output. Use when setting up a Project/workspace, or when output is on-topic but off-voice. Works for any role or domain.

Images, Video & Audio

Orchestrator

114

DylXBT/claude-orchestrator-skills

Assemble the user's context brain, skills, connectors, and pipelines into one system they actually run end-to-end — and document it so a teammate could run it too. The capstone meta-skill. Works for any role.

Skill & Plugin Authoring

Pipeline Builder

114

DylXBT/claude-orchestrator-skills

Break a big, multi-part task into a clean pipeline where each step's output feeds the next, with context carried forward. Use when one prompt is trying to do too much and the result drowns. Works for any multi-stage task in any field.

Productivity & Notes

Zettel Note

200

lyndonkl/claude

The note-writing discipline for this vault's evergreen knowledge graph, modeled on a Zettelkasten reading companion and governed by the vault conventions. Enforces declarative-claim titles, one claim per note (atomicity), own-words prose with no block quotes, the piped [[slug|Title]] link form, the labeled link-relationship vocabulary (Confirms/Contradicts/Extends/Context/Prerequisite/Builds-on/Applies/Example-of/Contrasts-with), 3-6 links per note, and search-before-create deduplication. Use when capturing a claim as an evergreen note, refactoring a sprawling note into atomic ones, or wiring

Productivity & Notes25

Dream

75

sneg55/agent-starter

Memory consolidation - review, merge, prune, and index memory files. Run periodically to keep memories organized and up-to-date.

Productivity & NotesIn 1 list

Wc Fixture Progression

200

lyndonkl/claude

Rates fixture difficulty (separately for an attacking and a defending fantasy asset, 1-5 each way, from opponent xGA/xG), computes team progression probabilities (group qualification odds from the mini-table; round-by-round knockout survival down the bracket) by reference-class forecasting updated Bayesianly on observed form and group state, detects weak-group/mismatch fixtures (powerhouse-vs-minnow -> captain candidates and clean-sheet locks), and builds a multi-round swing calendar of where each team's difficulty flips so transfers can be planned ahead. Emits the `fixture` signal. Use when c

Productivity & Notes25

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.