Agent Skills

Make integration knowledge
reusable.

Package the right references, checks and workflow instructions so your team’s agents work from the same foundation.

Amlok / CONNECTED INTELLIGENCE

EvidenceContextHuman judgment

REUSABLE INTEGRATION GUIDE

A practical starting point.

Adapt this guide to your environment and workflow. It contains instructions and references, not credentials or an API client.

SKILL.md

---
name: amlok-integration
description: Implement and review institution-authorized Amlok API integrations.
---

# Amlok integration guide

Build an Amlok integration for our institution’s approved workflow.

Start with https://docs.amlok.io/llms.txt and the OpenAPI contract at https://docs.amlok.io/openapi/amlok-v1.json. Read the quickstart, product scope, integration security, and relevant sandbox journey before implementing endpoints. Use the current contract for exact operation names and schemas.

Ask the developer to provide the framework, intended Insights or Signal journey, workspace scope, and institution-issued sandbox base URL. Read API credentials from the server environment; never put secrets in client code, logs, prompts, or source control.

Implement input validation, workspace authorization, explicit asynchronous states, safe retries, and error handling. Verify webhook signatures against raw bytes; persist accepted events and deduplicate deliveries before processing. Retrieve authoritative results and their source evidence.

Keep approval, borrower outreach, payments, and consequential interventions in institution-owned systems. Do not invent API endpoints or convert missing evidence into a valid zero.

Validate against the provisioned sandbox, including expired access, incomplete evidence, repeated requests, duplicate events, and unavailable providers. Summarize tested behavior and remaining deployment requirements for engineering review.

Keep secrets and borrower information outside your instructions.

Download skill guide

Capture the integration playbook

A skill can bundle task instructions with links to the API contract, product journey and security requirements. Keep it focused on a specific task such as implementing signed webhook delivery.

Ground the work in current references

Include the documentation index and require the agent to resolve actual operations and schemas before it writes code. Keep secrets and borrower data outside the skill.

Keep review part of the workflow

Require a sandbox verification checklist, evidence of expected behavior and human review before production. Reusable guidance helps teams stay consistent without granting an agent new authority.

BUILD WITH THE RIGHT REFERENCES