Triagem de reclamação de consumidor em ambiente digital (cobrança indevida, propaganda enganosa, falha na entrega, chargeback). Análise de mérito e opções de resposta. Rascunho para revisão de advogado.
How this skill is triggered — by the user, by Claude, or both
Slash command
/digital-ecommerce-legal:digital-consumer-claims-triage [cola a reclamação ou descreva o caso][cola a reclamação ou descreva o caso]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Matter context.** Check `## Matter workspaces` in the practice-level CLAUDE.md. If `Enabled` is `✗` (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run `/digital-ecommerce-legal:matter-workspace switch <slug>` or say `practice-l...
Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /digital-ecommerce-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/digital-ecommerce-legal/matters/<matter-slug>/.
When a consumer makes a complaint via chat, email, or a platform like Reclame Aqui, the team needs a quick triage: Is the claim valid? What's the exposure? What are our response options?
This skill takes the complaint, applies the relevant law (CDC art. 37, 39, 49, Decreto 7.962/2013, Marco Civil art. 19), and produces a triage memo with legal merit assessment + recommended response.
Premissa de jurisdição (Brasil):
CDC Art. 37 — Publicidade enganosa: Qualquer propaganda que induz o consumidor a erro sobre características do produto. [verified: https://www.planalto.gov.br/ccivil_03/leis/l8078compilado.htm]
CDC Art. 39 — Práticas abusivas: (I) venda casada/limites quantitativos; (II) recusar atendimento às demandas do consumidor; (III) enviar ou entregar produto/serviço sem solicitação; (IV) prevalecer-se de fraqueza/ignorância do consumidor; (V) exigir vantagem manifestamente excessiva. [verified: https://www.planalto.gov.br/ccivil_03/leis/l8078compilado.htm]
CDC Art. 49 — Direito de arrependimento: Consumidor pode desistir da compra no prazo de 7 dias (corridos, não úteis [verified: https://www.planalto.gov.br/ccivil_03/leis/l8078compilado.htm]). Se o cliente reclama 6 dias após a compra, direito existe. Se reclama 8 dias, prescrição completou.
Decreto 7.962/2013: O fornecedor deve informar forma e prazo da entrega ou disponibilização do produto (Art. 2º, V). [verified: https://www.planalto.gov.br/ccivil_03/_ato2011-2014/2013/decreto/d7962.htm]
No silent supplement. If a research query returns few results for a CDC article or Decreto 7.962 provision, report what was found and stop. Do NOT invent case law or assert a rule you're unsure of. Instead, ask the user / attorney.
Read ~/.claude/plugins/config/claude-for-legal/digital-ecommerce-legal/CLAUDE.md first. Any standing positions on claims (e.g., "we always refund COD orders within 48h", "we dispute chargebacks if order was shipped") apply to this triage.
| Type | CDC article | Key question |
|---|---|---|
| Cobrança indevida | Art. 42, parágrafo único | Was the customer charged for something they didn't owe? |
| Propaganda enganosa | Art. 37 | Did our ad claim something the product doesn't do? |
| Alteração de preço no checkout | CDC Arts. 30, 35 e 37; Decreto 7.962/2013 Art. 2º, IV [verified: https://www.planalto.gov.br/ccivil_03/leis/l8078compilado.htm; https://www.planalto.gov.br/ccivil_03/_ato2011-2014/2013/decreto/d7962.htm] | Did we show one price in the catalog and a different price in the cart/invoice? |
| Falha na entrega | Decreto 7.962/2013 Art. 2º, V | Did we fail to state the promised delivery or availability deadline? |
| Produto defeituoso / não conforme | CDC Art. 20 | Is the product broken or not what was promised? |
| Recusa de devolução / arrependimento | CDC Art. 49 | Did we refuse to allow a 7-day return? |
| Chargeback | Banking / Art. 39 | Consumer did a chargeback — did they have a legitimate reason? |
High-risk claims (we likely lose if this goes to court):
[verified: https://www.planalto.gov.br/ccivil_03/leis/l8078compilado.htm][verified: https://www.planalto.gov.br/ccivil_03/leis/l8078compilado.htm][verified: https://www.planalto.gov.br/ccivil_03/leis/l8078compilado.htm]Medium-risk claims (defense exists but gray):
[review][verified: https://www.planalto.gov.br/ccivil_03/leis/l8078compilado.htm; https://www.planalto.gov.br/ccivil_03/_ato2011-2014/2013/decreto/d7962.htm]Low-risk claims (we have a defense):
[review]Before recommending "deny" or escalating to legal action:
Read ## Who's using this in ~/.claude/plugins/config/claude-for-legal/digital-ecommerce-legal/CLAUDE.md. If the Role is Non-lawyer:
Recommending denial or escalation is a legal decision with business consequences (reputational risk, potential lawsuit, regulatory scrutiny). Have you reviewed this with your attorney? If yes, proceed. If no, here's a brief: [Claim type, legal merit (high/medium/low risk), aggravating factors, recommended response, reason for that response.]
Do not recommend "deny" or "escalate to arbitration" without explicit attorney approval.
Format as a brief triage report with claim summary, legal merit assessment (🔴 high-risk | 🟠 medium | 🟢 low), and recommended next step.
npx claudepluginhub bossmann007/claude-legal-br --plugin digital-ecommerce-legalGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.