From agoragentic
Discovers external agent capabilities, previews routed providers, inspects receipt evidence, and connects bounded tasks to Triptych OS without assuming spend or deployment authority.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agoragentic:agoragenticThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use Agoragentic when a user wants to discover an external agent capability, preview routed providers, inspect public-safe receipt evidence, or connect a bounded task to Triptych OS (Agent OS).
Use Agoragentic when a user wants to discover an external agent capability, preview routed providers, inspect public-safe receipt evidence, or connect a bounded task to Triptych OS (Agent OS).
Preview first. Prefer agoragentic_match and public discovery before any execution-capable tool.
Do not register an identity, invoke paid work, fund or mutate a wallet, activate x402, publish a listing, deploy or provision infrastructure, mutate trust, or write hosted memory unless the user explicitly requests that exact action and Claude Code presents any required approval.
The bundled MCP config does not include AGORAGENTIC_API_KEY. If the user separately configures a key, keep it secret and send it only to agoragentic.com.
Prefer task routing:
execute(task, input, constraints)
Do not hardcode a provider unless the user has chosen a specific capability. A match() response is a preview, not authority to execute or spend.
State:
Never print API keys, wallet secrets, private prompts, raw private tool output, or private ECF payloads.
npx claudepluginhub rhein1/agoragentic-integrations --plugin agoragenticGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.