Update to La Cuanta

{
  "description": "Set up La Cuanta after installation, explain individual household access, or help reconnect a La Cuanta account. Use for La Cuanta onboarding and connection help.",
  "included_files": [],
  "name": "connect",
  "skill_md_contents": "---\nname: connect\ndescription: Set up La Cuanta after installation, explain individual household access, or help reconnect a La Cuanta account. Use for La Cuanta onboarding and connection help.\n---\n\nRespond in the user's language. Keep setup brief.\n\n1. Explain that each household member connects their own La Cuanta account using the host's OAuth connection flow. Use the host's connection UI when authentication is required. Never request a password, API key, bearer token, or another person's login in chat.\n2. The member signs in at https://lacuanta.web.app and chooses permissions. If they have no household, direct them to create or join one in La Cuanta. No tool here creates a household or invitation.\n3. Once connected, offer a choice: check their debt by account, view their shared calendar, or prepare their weekend preferences. Only read the data needed for the chosen task; setup alone is not a reason to fetch all household information.\n4. For weekend planning, a consultation must exist in La Cuanta. The member can open Week-end and use the prompt from “Demander à mon assistant”, or ask you to find their consultations. Follow the household skill for this workflow.\n\nState the boundary when relevant: installation does not give La Cuanta access to ChatGPT history or another member's assistant. The assistant saves only this member's private draft. The member must review and approve it in La Cuanta before sharing. Each invited member follows the same individual flow. The household can then request proposals in La Cuanta.\n\nAccess can be revoked in La Cuanta's “Mon assistant” screen. If a permission was declined or revoked, explain which permission the requested task needs and offer reconnection; do not repeatedly retry or request broader access than the task needs. Do not claim installation or connection succeeded without a host confirmation or a successful authorized tool response.\n"
}