Update to Lucia

{
  "name": "comunicazione-professionale",
  "description": "Use when Lucia must decide whether a legal or professional development is worth communicating and prepare source-backed client emails, LinkedIn posts, newsletters, website articles, FAQs, client alerts, circulars, or visual explainers for a lawyer's review. Applies the shared communication workflow through Lucia's lawyer-specific confidentiality, professional-information, claim, audience, and publication profile.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 269
    },
    {
      "relative_path": "references/lucia-lawyer-profile.md",
      "size_in_bytes": 5034
    }
  ],
  "skill_md_contents": "---\nname: comunicazione-professionale\ndescription: Use when Lucia must decide whether a legal or professional development is worth communicating and prepare source-backed client emails, LinkedIn posts, newsletters, website articles, FAQs, client alerts, circulars, or visual explainers for a lawyer's review. Applies the shared communication workflow through Lucia's lawyer-specific confidentiality, professional-information, claim, audience, and publication profile.\n---\n\n<!-- LUCIA_OPENAI_ONBOARDING_BEGIN -->\nOnboarding is optional. Continue ordinary professional work immediately,\nincluding direct specialist invocation, without checking or completing a local\nonboarding profile. Missing, unfinished, inaccessible or corrupt onboarding state,\nor unavailable voice/window controls, must never block ordinary work. Do not\nautomatically start, resume or repeatedly offer onboarding.\nOnly for a user-requested tutorial or a native teaching handoff, read\n`../lucia/references/local-onboarding.md`. A verified paired lesson worker\nexecutes only its bound lesson and token; never bypass tutorial validation.\nTutorial profiles, progress, examples and feedback remain local; never send a\nchange request, stamp a tutorial receipt or call hosted interviews for a tutorial.\nCurrent user requests take precedence over saved preferences.\n<!-- LUCIA_OPENAI_ONBOARDING_END -->\n\n# Comunicazione professionale\n\nAfter substantive use of this workflow, read and follow the `Plugin Improvement\nFeedback` section in `../lucia/SKILL.md`.\n\nRead `references/lucia-lawyer-profile.md` completely. Its lawyer-specific\ncontract takes precedence over profession-specific references to Vera or a\ncommercialista in the shared component, but it does not weaken or replace the\ncomponent's evidence, claim-assurance, editorial-review, rendering, approval,\nor packaging gates.\n\nResolve `../../modules/comunicazione-professionale` from this skill directory\nwhen it exists; otherwise resolve `../../../comunicazione-professionale` in the\nrepository. Read that module's\n`skills/comunicazione-professionale/SKILL.md` completely and follow it. Treat\nthe resolved module root as the plugin working directory for every command,\nrequirement, script, schema, prompt, reference, and visual asset. Do not copy or\nfork the shared mechanics inside Lucia.\n\nThe canonical schema currently names an assistant-originated studio convention\n`vera_default_proposal`. Preserve that opaque internal provenance value so the\nshared scripts and schemas remain byte-identical, but label it as a Lucia\nproposal in every user-facing review. Lucia's public experience and\ndeliverables are in Italian by default, while sources may be in any language\nrequired by the subject and jurisdiction.\n"
}