Customize Skopos05 · Connect external services
Use outside services without giving agents a blank check.
Represent an approved provider operation as a governed project Action with explicit network, secret, service, approval, and effect boundaries.
External operations stay attributable, reviewable, and attached to the work that required them.Start with a conversation
Tell your agent the outcome and the safety boundary.
Skopos can help translate the request into its technical model after the intent is clear.
“Help me model this external service operation as a Skopos Action. Declare the exact service and operation, required network and secret capabilities, expected external effect, approval rule, safe inputs, and normalized provider receipt. Do not claim Skopos can reverse or sandbox effects the provider controls.”
A reviewed path from intent to project behavior.
- 01
Declare access
Name the required service, tool, network, browser, secret, and approval capabilities explicitly.
- 02
Run within the boundary
Skopos preflights the declared capability and refuses unavailable or unapproved execution.
- 03
Keep the receipt
A successful provider response is normalized and linked to the Task as external-effect Evidence.
USE IT FOR
Common project uses.
- Create a deployment preview
- Run a remote compatibility check
- Request an approved provider operation
- Call a project-owned internal service
The Skopos names for what you just configured.
- External effect
- A declared change outside the local repository.
- Provider receipt
- Allowlisted provider-reported confirmation of one operation and request.
- Approval
- An explicit requirement that fails closed when missing.
WHAT THIS CANNOT DO
Skopos governs the declared request and records the provider response. It does not promise universal provider support, operating-system isolation, or reversal of an external mutation.
NEXT
Read the trust model