{"id":83469,"plugin_id":"plugin_asdk_app_6ad9af1d8ff081919d1c3a90dd6dbfa1","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-06T00:14:06.566Z","digest":"5946e2c6eb9c875cd01d26c2f81cc5e410af98e897428698a9b92735d930dd95","against":null,"payload":{"description":"Prepare weekly pet-care billing drafts grouped by client from supplied records, agreed USD rates, client discounts and user-reported payments.","included_files":[],"name":"weekly-pet-care-billing","skill_md_contents":"---\nname: weekly-pet-care-billing\ndescription: Prepare weekly pet-care billing drafts grouped by client from supplied records, agreed USD rates, client discounts and user-reported payments.\n---\n\n# Weekly pet-care billing drafts\n\nUse `draft_weekly_pet_care_billing` when the user supplies several service records\nor clients and wants a billing draft. The tool does not retrieve a week's records\nfrom HoundTrust or check whether work was completed.\n\nAsk the user to supply the records to include, a unique clientId per client and a\nunique recordId for every record. Short aliases such as client-a and walk-1 are\nenough; do not request database IDs or contact details. Do not merge people by\nsimilar names or silently drop repeated records. Clarify ambiguous duplicates.\n\nEach record uses the quote workflow's explicit USD rate, included-pet count,\nadditional-pet rate, pet count and calendar-night dates or flat-session count.\nAsk for missing rates; do not invent them or use market research as approval.\nConvert dollars to whole cents. Do not infer a completed week from the chat date.\n\nApply a supplied discount or reported payment once at the client level. Leave\nrecord-level discount and payment at zero or omit them. Do not double-apply an\nadjustment, allocate an unexplained payment, or convert an overpayment into a\nzero balance. Ask for a correction if the input is rejected. The batch is\nvalidated together; do not present a partial result as a complete batch.\n\nThe tool accepts at most 10 clients, 10 records per client and 50 records in one\nrequest. The entire MCP request also has a 32 KiB limit, so long holiday lists\nmay require smaller user-reviewed batches. Do not silently split a client or\ntheir discount/payment across calls. If the user has more, explain the limit\nand agree on complete client batches; do not omit records or combine balances\nacross batches.\n\nReturn each client's itemized records, subtotal, discount, total, reported\npayment and calculated balance, followed by the batch totals and all assumptions.\nPayments and completion are user-reported. The result is an unsent draft, not a\nsaved invoice, receivables report, payment request or verified collection record.\nDo not claim to send reminders, update HoundTrust, reserve care or charge cards.\n\nShow the single returned websiteContinuation link after the complete result,\nwith its notice immediately beside it. Use its exact URL and fixed labels. Do\nnot put client IDs, names, dates, rates or the draft in a URL. The destination\nprovides weekly billing checks without an account, with product analytics choices;\nit does not import or save this batch. Do not add signup or upgrade links.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}