Update to Delos

{
  "description": "Prepare and submit a supported Delos Claim Sale, Collections, Factoring, Payment Protection or portfolio enquiry, with optional selected documents. Review the completed details and exact file plan and obtain approval before sending. Lien intake remains paused.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 545
    },
    {
      "relative_path": "references/local-files.md",
      "size_in_bytes": 3054
    },
    {
      "relative_path": "references/portfolio-financials.md",
      "size_in_bytes": 1417
    },
    {
      "relative_path": "references/procedure.md",
      "size_in_bytes": 15038
    },
    {
      "relative_path": "references/products.md",
      "size_in_bytes": 15723
    },
    {
      "relative_path": "references/submission-contract.md",
      "size_in_bytes": 4041
    },
    {
      "relative_path": "scripts/submit_local_documents.py",
      "size_in_bytes": 16735
    }
  ],
  "name": "submit-claim",
  "skill_md_contents": "---\nname: submit-claim\ndescription: Prepare and submit a supported Delos Claim Sale, Collections, Factoring, Payment Protection or portfolio enquiry, with optional selected documents. Review the completed details and exact file plan and obtain approval before sending. Lien intake remains paused.\n---\n\n# Prepare a Delos enquiry\n\nRead the generated [shared procedure](references/procedure.md) before intake.\nUse its normal-chat response style and service-specific party labels while keeping\nthe completed review summary complete. Native host approval controls still apply.\nThe procedure also supplies standalone MCP instructions and guidance hints.\nBefore constructing submission arguments, read the\n[submission field reference](references/submission-contract.md) and check the\nselected host tool's actual schema, even when a complete draft is already supplied.\nMap the reviewed facts to its exact nested keys; conversational labels are not API\naliases. For a single enquiry, use `creditor.name`, `creditor.address`,\n`creditor.contact_person`, `creditor.type_of_service_interested_in`, `debtor.address`\nand `financials.original_claim_balance`. Do not use `creditor.legal_name` or\n`financials.amount`; `debtor.legal_name` is correct for a business debtor.\nNo Delos account or user-supplied API key is needed.\n\n## Preserve the person's intent\n\nIf the user asks about suitability or terms, use `get_product_guidance` when exposed.\nUse it even if packaged product facts are already in context; their presence does\nnot make the live tool absent or optional.\nWhen it is not exposed, use the generated [product snapshot](references/products.md)\nand identify its revision/date on first use. A visible guidance failure follows the\nshared error procedure, not a silent fallback. Do not switch to a different Delos\nconnection to obtain an absent tool.\n\nCheck the chosen product's availability. Keep the existing four entry points:\n\n| Enquiry | No files selected | Selected files supported by this host |\n| --- | --- | --- |\n| One Claim Sale, Collections, Factoring or Payment Protection enquiry | `submit_claim` | `submit_claim_with_documents` |\n| Portfolio Sale or Portfolio Collections overview | `submit_portfolio` | `submit_portfolio_with_documents` |\n\nTool names can have a host prefix. Match the tools in this Delos connection.\nDedicated lien intake and files remain paused; use general contact instead.\nDo not infer additional portfolio services from legacy accepted enums.\n\nAsk one invoice or several, or which service, only if the request is unclear.\nDo not restart the questionnaire after the person has supplied a complete draft.\nUse planned payment/payer for PP, invoice recipient for Factoring, and debtor for\nClaim Sale/Collections. Keep the existing backend field mapping. Dates and terms\ngo in the description where appropriate; never invent an invoice number/object.\n\n## Prepare and review\n\nAsk one related group of at most three missing questions at a time. Keep optional\nfields optional. Resolve contradictions rather than inventing identities, countries,\namounts or dates. A portfolio overview needs no individual-debtor questionnaire.\n\nUse the shared review procedure: show the service, details, amount/currency,\ndescription and exact file list, including any files agreed for later upload.\nExplain that they go to Delos for review and obtain approval of that completed\nsummary. Reuse approval for an unchanged summary; show and approve changes before\nsending. Cancellation stops the send.\n\n## Use one document transport\n\nPrefer the matching with-documents MCP tool when the host supports its file input.\nFollow the actual advertised shape: a host may expose attached files as absolute\nlocal paths and bind them to remote descriptors itself. The remote MCP wire does\nnot read arbitrary paths. Do not fabricate IDs/URLs, pass Base64 or silently drop files.\n\nIf only readable selected local files are available, and this installed package\nincludes its uploader, follow [the local-file procedure](references/local-files.md).\nThe uploader is preserved from the published package. A URL-only MCP connection\ndoes not install it. Do not call a real send merely to test it.\n\nFor unsupported or oversized selected files, explain the relevant direct limit:\n10 files and a complete multipart request below 4 MiB. Offer submission of the\ndetails first and later upload through the expected emailed secure link, supporting\nup to 500 MB per file. Obtain explicit approval of any omitted/changed files before\nusing the no-document tool. This fallback does not apply to paused lien intake.\n\nRead [optional portfolio financials](references/portfolio-financials.md) only when\nthe user supplies or asks to include those amounts. Do not require them.\n\n## Send once and report the actual result\n\nCheck the required fields and selected-file input against that schema before the\ncall; do not use a real submission call as a payload validator.\nAfter approval, use one matching transport once, with `confirmed: true` for an MCP\nsubmission. Host confirmation controls also apply. Report the actual returned\npublic reference and status. Accepted means queued for review; it does not prove\ncompleted processing or email delivery. Explain that next steps and the secure\nupload link should follow after processing; never invent the link or reference.\n\nAfter an uncertain send, preserve the receipt and stop. Do not automatically retry\nor switch transports. The local uploader's documented, deliberate retry after a\nproven pre-connection failure is a narrow exception, not an uncertain-send retry.\nUse witold@delos.international with the actual reference for follow-up, and\nhello@delos.international for technical help. There is no status-lookup tool.\n\nFor validation failures, report the exact field paths and returned messages. For\na host safety block, quote the reason provided and stop; distinguish it from a\nDelos API error. Do not switch connections or transports, or change the approved\nfacts or files to get around the block. If no detailed reason is supplied, say so.\n\n"
}