Grey Golus logoGREYGOLUSStart here

03 // Resource guide

Updated June 2026

Anatomy of a harness

Context, tools, connectors, MCPs, APIs, skills, computer use, and automations are related, but they are not interchangeable.

Bottom line

The model provides intelligence. The harness becomes useful by adding the right context, access, actions, and reusable instructions around it.

01 // Core parts

The plain-language map

Context

01
What it knows

The facts, files, examples, preferences, and history the AI should use for this task.

Tool

02
What it can do

A specific action the AI can take, such as web search, file editing, code execution, or calculation.

Connector

03
What it can reach

A packaged connection to an outside service or account, such as Gmail, Drive, Calendar, or Slack.

Plugin

04
Capability pack

A bundle that can add instructions, connectors, commands, tools, or specialized behavior to a harness.

MCP

05
Common adapter

An open standard that lets AI applications connect to external data, tools, and workflows through a common pattern.

API

06
Program doorway

A defined software interface that lets one program request data or actions from another service.

Skill

07
Playbook

Saved reusable instructions for how a repeated task should be completed and checked.

Automation

08
Standing order

A workflow triggered by a schedule or event instead of being rebuilt manually each time.

02 // Access order

Prefer the most precise path

MethodBest whenMain caution
Local filesThe work already lives in a selected folderScope the folder carefully
ConnectorA supported service has structured data or actionsConfirm the account and permissions
MCPA harness needs a reusable standard connectionTrust and review the server
Computer useNo direct connector or tool existsSlower and easier to mis-click
APIYou are building software or a custom automationCredentials, cost, and error handling

03 // Build the stack

Add capability in this order

  1. 01

    Define the outcome

    Name what done looks like before adding tools or access.

  2. 02

    Add durable context

    Give it the smallest trustworthy set of files, examples, and preferences.

  3. 03

    Connect only what is needed

    Add the exact service or tool the workflow requires.

  4. 04

    Save the procedure as a skill

    Capture the repeatable steps, output format, and verification rules.

  5. 05

    Automate only after it works

    Run it manually, inspect failures, then schedule or trigger it.

04 // Permission rule

Access is not permission

  • Being able to read a file does not mean the AI should share it.
  • Being able to open a website does not mean the AI should submit or publish.
  • Being able to edit a folder does not mean the AI should delete or overwrite important work.
  • Use the narrowest access that can complete the task, then verify the result.

Official sources