| name | build-peerry-provider |
| description | Build or review a Peerry Provider Adapter against the repository's Provider Contract without modifying Peerry Core. |
Build a Peerry Provider
Use this skill only for Provider Adapter or Connector development. Read ../../docs/provider-contract.md and start from ../../connector-template.
Outcome
Implement provider-specific access behind Peerry's Provider Contract while leaving Workflow, Context, Memory, Artifact, Transcript and Room code unchanged.
Work
- Inspect the target provider and the user's supported environment.
- Copy the connector template into a separate provider directory.
- Implement
send() using PeerryRequest and return a normalized text response.
- Declare every capability as
SUPPORTED, UNSUPPORTED, or UNKNOWN.
- Respect
AbortSignal; report cancellation as CANCELLED when supported.
- Normalize provider failures through
ProviderError; keep useful diagnostics but never credentials or raw provider payloads.
- Run the shared Provider Contract tests and provider-specific offline tests.
- Document authentication, cancellation, timeout and capability limitations.
- Report status accurately as
IMPLEMENTED, CONTRACT TESTED, or LIVE VALIDATED.
Contract tests are not live validation. Live validation requires the user's authorized provider environment or BYOK and explicit permission before external sending.
Security boundary
Never modify Peerry Core to make a connector work. Never extract or export cookies, session tokens or credentials; access unsupported private endpoints; intercept provider network traffic; bypass CAPTCHA, anti-bot or provider protections; use stealth automation; or claim unsupported capabilities.
Third-party connectors are untrusted code. Review their filesystem, IPC, credential and browser permissions before use. The current template is development guidance, not a sandbox or dynamic plugin runtime.
