Platforms / Understand the connection

Claude

Learn where project instructions fit in Claude and what to verify before adapting an agent package to a different host.

01 / Connection context

Project instructions and knowledge have different jobs

Claude’s documentation describes project instructions as guidance applied across project chats. The project knowledge area holds uploaded context. A project’s name and description are not themselves visible to Claude as task instructions. Put durable behavioral guidance in the appropriate instruction field and source material in the appropriate context area.

Read the official sources for this guide ↓

02 / Connection context

Porting requires a new check

An instruction package tested on another platform is a candidate for adaptation, not automatically a verified Claude resource. AgentGrid recommends checking the package’s declared platforms and exact version first. If Claude is not listed, do not interpret this general guide as a compatibility badge. A creator must test and publish an appropriate version before making that claim.

03 / Connection context

Begin with a small, reviewable task

Use a separate project or task context for the trial. Supply only the material required for that task and compare the result with the package’s normal, missing-input and adversarial-input expectations. Keep external actions disabled unless the resource explicitly requires them and you have separately approved the necessary access.

04 / Connection context

Check visibility and account availability

Claude documents project visibility and sharing controls that depend on account context. Inspect the actual project’s audience before uploading material. Verify current plan limits in the provider documentation; this page does not promise a particular entitlement, integration or usage allowance.

Check before you continue.

  • Check the package’s declared platform and distribution format before adapting it.
  • Keep task instructions separate from source documents and verify project visibility.
  • Record observed failures and uncertainties instead of treating fluent output as successful verification.

AgentGrid does not ask you to paste an API key or connect an account on this page. Any provider access, subscription or usage charge is separate.

Resources that declare this platform.

Showing 0 of 0 resources with this declared requirement. Open the resource to check its publication status, exact setup, version and verification evidence.

No published resources currently declare this platform. General guidance is not a promise that an agent supports it.

Official sources, checked on 2026-10-08.

Provider facts above are drawn from these sources. Testing and review recommendations are AgentGrid’s editorial guidance.

Next documentation review due: .