agentleFS
srednoff888-artsrednoff888-art/srednoff-os-for-claude/.claude/skills/connector-orchestrator/SKILL.md

connector-orchestrator

Skill1 starsChanged 5 months agoMITView on GitHub

Use this skill when a task may benefit from MCP servers or connected tools such as GitHub, Vercel, Supabase, Figma, Canva, Gmail, Calendar, Contacts, Replit, Convex, Anthropic, or OpenAI.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use MCP/connectors only when they provide facts or actions that improve the result.

    line 8
  2. Distinctive:

    Check whether relevant MCP/connectors are available.

    line 13
  3. Distinctive:

    Use the minimum necessary data.

    line 14
  4. Distinctive:

    Ask confirmation before destructive actions.

    line 15
  5. Distinctive:

    Verify the result after actions.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Connector Orchestrator Skill

Use MCP/connectors only when they provide facts or actions that improve the result.

Workflow

  1. Identify which external systems matter.
  2. Check whether relevant MCP/connectors are available.
  3. Use the minimum necessary data.
  4. Ask confirmation before destructive actions.
  5. Verify the result after actions.
  6. Report what was used and why.

Destructive actions requiring explicit approval

  • deleting production data;
  • disabling RLS/auth/security;
  • changing production env vars;
  • deploying to production;
  • changing billing/domain/DNS/payment settings;
  • sending emails;
  • merging PRs;
  • force-pushing;
  • running irreversible migrations.

Output

## Connector Plan

Needed connectors:
-

Why:
-

Actions:
-

Requires confirmation:
-

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.