Update to Zid | زد

{
  "description": "Answer Zid developer questions from the live docs at docs.zid.sa. Use when building a Zid app or integration, calling the Zid Merchant API, setting up Zid OAuth, scopes or webhooks, or reading a Zid API error.",
  "included_files": [],
  "name": "zid-api",
  "skill_md_contents": "---\nname: zid-api\ndescription: Answer Zid developer questions from the live docs at docs.zid.sa. Use when building a Zid app or integration, calling the Zid Merchant API, setting up Zid OAuth, scopes or webhooks, or reading a Zid API error.\n---\n\n# Zid API\n\nPartners and merchants build on Zid through its public developer platform, and\nits documentation at `https://docs.zid.sa` is the only source for how that\nworks. The docs change, so this skill holds no API facts of its own: it is the\nprocedure for finding them. Running store work through the Zid MCP tools, or on\na schedule, is the `zid-ops` skill.\n\n## Ground rules\n\n- The user's explicit instructions take precedence over this skill.\n- Every endpoint, header, scope, parameter, limit, status code and event name in\n  an answer comes from a docs.zid.sa page fetched in this conversation, and the\n  answer links that page.\n- Answer with documented endpoints only. When the user names one the docs do not\n  list (seen in a browser, another tool or another integration), say it is not\n  in the Zid developer docs.\n- Secrets stay out of chat: client secrets, tokens and webhook credentials go\n  into the app's secret store. In examples, write them as placeholders such as\n  `<CLIENT_SECRET>`.\n\n## Look it up\n\n1. Fetch the index, `https://docs.zid.sa/llms.txt`. Each line holds a section\n   path (such as `Merchant APIs > Orders`), a page title and the page's `.md`\n   URL. Done when the index is loaded; if it cannot be fetched, say so and ask\n   the user for the page instead of answering from memory.\n2. Pick the pages. Every question needs the concept pages it touches (for\n   example `Authorization`, `Rate Limiting`, `Responses`, the webhooks\n   `Overview`) and the endpoint page for each call. Done when each part of the\n   question has a page, or is noted as not in the index.\n3. Fetch each page's `.md` URL. Endpoint pages carry the OpenAPI spec: server,\n   method, path, headers, parameters, request body and responses. Some also\n   list the scopes; when a page names none, say the scope is not stated there.\n4. Answer from the fetched text: exact names as written, a link per page, code\n   with secrets as placeholders. Where two pages disagree, give both with their\n   links and say which one is the API reference.\n\nDone when every fact in the answer links to a page fetched in step 3, and every\ngap is named as not documented.\n\n## Errors\n\nFor an error, ask for the status code and the full response body first, then\nfetch `Responses` and, for sign-in and token errors, `OAuth Errors &\nTroubleshooting`. Match the exact error text to the page; when it is not there,\nsay so and give the request and response the user would send to Zid.\n"
}