Update to Lucia
Snapshot Nov 11, 2026 · 18:09 UTC · version 0.1.230
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for quesito-legale-fiscale
Skill instructions — Now says: <!-- MPARANZA_REPORTING_BEGIN --> ## Task reporting and recovery For every substantive user mandate, follow `skills/lucia/references/workflow-usage.md` from...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Sep 30, 2026 · 23:14 UTC
follow it. The invoking product root is two levels above this skill directory. Informational research completes after validation. A concrete opinion or an explicit opposing-opinion request includes the opposing examination unless the use...
Nov 11, 2026 · 18:09 UTC
<!-- MPARANZA_REPORTING_BEGIN --> ## Task reporting and recovery For every substantive user mandate, follow `skills/lucia/references/workflow-usage.md` from this installation's root. Start one primary task before preparation, using `usag...
Supporting files
Sep 30, 2026 · 23:14 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":299}]
Nov 11, 2026 · 18:09 UTC
[]
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -2,6 +2,28 @@ name: quesito-legale-fiscale description: Use when Lucia receives a substantive legal, tax-law, or compliance question, analysis request, or source-backed legal drafting request and must take it through one complete question-to-reviewed-answer journey. Do not use for filings, signatures, submissions, or operational forms that require a dedicated workflow or the lawyer's direct action. --- +<!-- MPARANZA_REPORTING_BEGIN --> +## Task reporting and recovery + +For every substantive user mandate, follow +`skills/lucia/references/workflow-usage.md` from this installation's root. +Start one primary task before preparation, using `usage/pipelines.json`; nested +specialists, retries and Studio Archive infrastructure reuse that task. Record +only the observed whole-task outcome. Discover `lucia_incident_host_link`, +including deferred tools, and verify this run's Computer ID on the server. +Build the report input from actual phases even for chat-only drafts; missing +client files or a prepared input JSON do not waive reporting. Show the readable +local model-data report under `skills/lucia/references/model-data-report-contract.md`, link its +actual signed receipt, and ask once for the user's 1–5 stars after delivery. +Only user-authored feedback is submitted; tests remain explicitly marked. +Follow `skills/lucia/references/incident-recovery.md` for automatic technical +reporting, evidence requests and targeted remedies. Use the HTTPS browser recovery page in that reference if +local execution is unavailable. Never ask the user to relay logs or repeat consent +for technical reporting. Recovery requires an observed successful retry of the +original task and inputs, bound to the original report and current remedy. +Tutorials remain local-only and are excluded from task usage and ratings. +<!-- MPARANZA_REPORTING_END --> + <!-- LUCIA_OPENAI_ONBOARDING_BEGIN --> Onboarding is optional. Continue ordinary professional work immediately, @@ -29,15 +51,21 @@ it exists; otherwise resolve `../../../deep-research-validator` in repository source. Read that module's `skills/legal-tax-answer-review/references/answer-journey.md` completely and -follow it. The invoking product root is two levels above this skill directory. +follow it. Research resolves that same module's `skills/deep-research/SKILL.md`. +The invoking product root is two levels above this skill directory. Use this product's `../legal-tax-answer-planner/SKILL.md`, `../legal-tax-answer-review/SKILL.md` and, only when required, `../adversarial-opinion/SKILL.md`. Do not fork or summarize the shared method. -Informational research completes after validation. A concrete opinion or an -explicit opposing-opinion request includes the opposing examination unless the -user asks to omit it. The same shared method makes the Deep Research choice -independently and preserves professional review and the no-local-tools fallback. +Every new research assignment uses `../deep-research/SKILL.md`, which resolves +one shared method with repeated investigation, continuous validation and +adversarial challenge using the current host model and tools. Retain +`generation_route: codex_direct`; do not offer a normal/deep selector or depend +on an external research plugin. Final validation and, when required, the +reviewed opposing opinion can reopen targeted research in the same run. +Informational research completes after final validation. A concrete opinion or +an explicit opposing-opinion request includes the final opposing examination +unless the user asks to omit it. Early challenges do not replace that stage. Lucia normally delivers in Italian, unless the user requests another language. Keep governing law, jurisdiction, forum and source hierarchy separate from
Full technical diff · 2 changed fields
changed /included_files
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 299
}
][]
changed /skill_md_contents
"---\nname: quesito-legale-fiscale\ndescription: Use when Lucia receives a substantive legal, tax-law, or compliance question, analysis request, or source-backed legal drafting request and must take it through one complete question-to-reviewed-answer journey. Do not use for filings, signatures, submissions, or operational forms that require a dedicated workflow or the lawyer's direct action.\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# Risposta a quesiti legali e fiscali\n\nAfter substantive use of this workflow, read and follow the `Plugin Improvement Feedback` section in `../lucia/SKILL.md`.\n\nThis is Lucia's user-facing journey from a substantive legal, tax or\ncompliance question to a reviewed answer. Select it automatically for the\nrequested complete answer; the user need not choose internal stages.\n\nResolve `../../modules/deep-research-validator` from this skill directory when\nit exists; otherwise resolve `../../../deep-research-validator` in repository\nsource. Read that module's\n`skills/legal-tax-answer-review/references/answer-journey.md` completely and\nfollow it. The invoking product root is two levels above this skill directory.\nUse this product's `../legal-tax-answer-planner/SKILL.md`,\n`../legal-tax-answer-review/SKILL.md` and, only when required,\n`../adversarial-opinion/SKILL.md`. Do not fork or summarize the shared method.\n\nInformational research completes after validation. A concrete opinion or an\nexplicit opposing-opinion request includes the opposing examination unless the\nuser asks to omit it. The same shared method makes the Deep Research choice\nindependently and preserves professional review and the no-local-tools fallback.\n\nLucia normally delivers in Italian, unless the user requests another language.\nKeep governing law, jurisdiction, forum and source hierarchy separate from\noutput language. Final interpretations, strategy, signatures, filings, client\ncommunications and professional approval remain with the lawyer.\n"
"---\nname: quesito-legale-fiscale\ndescription: Use when Lucia receives a substantive legal, tax-law, or compliance question, analysis request, or source-backed legal drafting request and must take it through one complete question-to-reviewed-answer journey. Do not use for filings, signatures, submissions, or operational forms that require a dedicated workflow or the lawyer's direct action.\n---\n<!-- MPARANZA_REPORTING_BEGIN -->\n## Task reporting and recovery\n\nFor every substantive user mandate, follow\n`skills/lucia/references/workflow-usage.md` from this installation's root.\nStart one primary task before preparation, using `usage/pipelines.json`; nested\nspecialists, retries and Studio Archive infrastructure reuse that task. Record\nonly the observed whole-task outcome. Discover `lucia_incident_host_link`,\nincluding deferred tools, and verify this run's Computer ID on the server.\nBuild the report input from actual phases even for chat-only drafts; missing\nclient files or a prepared input JSON do not waive reporting. Show the readable\nlocal model-data report under `skills/lucia/references/model-data-report-contract.md`, link its\nactual signed receipt, and ask once for the user's 1–5 stars after delivery.\nOnly user-authored feedback is submitted; tests remain explicitly marked.\nFollow `skills/lucia/references/incident-recovery.md` for automatic technical\nreporting, evidence requests and targeted remedies. Use the HTTPS browser recovery page in that reference if\nlocal execution is unavailable. Never ask the user to relay logs or repeat consent\nfor technical reporting. Recovery requires an observed successful retry of the\noriginal task and inputs, bound to the original report and current remedy.\nTutorials remain local-only and are excluded from task usage and ratings.\n<!-- MPARANZA_REPORTING_END -->\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# Risposta a quesiti legali e fiscali\n\nAfter substantive use of this workflow, read and follow the `Plugin Improvement Feedback` section in `../lucia/SKILL.md`.\n\nThis is Lucia's user-facing journey from a substantive legal, tax or\ncompliance question to a reviewed answer. Select it automatically for the\nrequested complete answer; the user need not choose internal stages.\n\nResolve `../../modules/deep-research-validator` from this skill directory when\nit exists; otherwise resolve `../../../deep-research-validator` in repository\nsource. Read that module's\n`skills/legal-tax-answer-review/references/answer-journey.md` completely and\nfollow it. Research resolves that same module's `skills/deep-research/SKILL.md`.\nThe invoking product root is two levels above this skill directory.\nUse this product's `../legal-tax-answer-planner/SKILL.md`,\n`../legal-tax-answer-review/SKILL.md` and, only when required,\n`../adversarial-opinion/SKILL.md`. Do not fork or summarize the shared method.\n\nEvery new research assignment uses `../deep-research/SKILL.md`, which resolves\none shared method with repeated investigation, continuous validation and\nadversarial challenge using the current host model and tools. Retain\n`generation_route: codex_direct`; do not offer a normal/deep selector or depend\non an external research plugin. Final validation and, when required, the\nreviewed opposing opinion can reopen targeted research in the same run.\nInformational research completes after final validation. A concrete opinion or\nan explicit opposing-opinion request includes the final opposing examination\nunless the user asks to omit it. Early challenges do not replace that stage.\n\nLucia normally delivers in Italian, unless the user requests another language.\nKeep governing law, jurisdiction, forum and source hierarchy separate from\noutput language. Final interpretations, strategy, signatures, filings, client\ncommunications and professional approval remain with the lawyer.\n"
Full snapshot data
{
"description": "Use when Lucia receives a substantive legal, tax-law, or compliance question, analysis request, or source-backed legal drafting request and must take it through one complete question-to-reviewed-answer journey. Do not use for filings, signatures, submissions, or operational forms that require a dedicated workflow or the lawyer's direct action.",
"included_files": [],
"name": "quesito-legale-fiscale",
"skill_md_contents": "---\nname: quesito-legale-fiscale\ndescription: Use when Lucia receives a substantive legal, tax-law, or compliance question, analysis request, or source-backed legal drafting request and must take it through one complete question-to-reviewed-answer journey. Do not use for filings, signatures, submissions, or operational forms that require a dedicated workflow or the lawyer's direct action.\n---\n<!-- MPARANZA_REPORTING_BEGIN -->\n## Task reporting and recovery\n\nFor every substantive user mandate, follow\n`skills/lucia/references/workflow-usage.md` from this installation's root.\nStart one primary task before preparation, using `usage/pipelines.json`; nested\nspecialists, retries and Studio Archive infrastructure reuse that task. Record\nonly the observed whole-task outcome. Discover `lucia_incident_host_link`,\nincluding deferred tools, and verify this run's Computer ID on the server.\nBuild the report input from actual phases even for chat-only drafts; missing\nclient files or a prepared input JSON do not waive reporting. Show the readable\nlocal model-data report under `skills/lucia/references/model-data-report-contract.md`, link its\nactual signed receipt, and ask once for the user's 1–5 stars after delivery.\nOnly user-authored feedback is submitted; tests remain explicitly marked.\nFollow `skills/lucia/references/incident-recovery.md` for automatic technical\nreporting, evidence requests and targeted remedies. Use the HTTPS browser recovery page in that reference if\nlocal execution is unavailable. Never ask the user to relay logs or repeat consent\nfor technical reporting. Recovery requires an observed successful retry of the\noriginal task and inputs, bound to the original report and current remedy.\nTutorials remain local-only and are excluded from task usage and ratings.\n<!-- MPARANZA_REPORTING_END -->\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# Risposta a quesiti legali e fiscali\n\nAfter substantive use of this workflow, read and follow the `Plugin Improvement Feedback` section in `../lucia/SKILL.md`.\n\nThis is Lucia's user-facing journey from a substantive legal, tax or\ncompliance question to a reviewed answer. Select it automatically for the\nrequested complete answer; the user need not choose internal stages.\n\nResolve `../../modules/deep-research-validator` from this skill directory when\nit exists; otherwise resolve `../../../deep-research-validator` in repository\nsource. Read that module's\n`skills/legal-tax-answer-review/references/answer-journey.md` completely and\nfollow it. Research resolves that same module's `skills/deep-research/SKILL.md`.\nThe invoking product root is two levels above this skill directory.\nUse this product's `../legal-tax-answer-planner/SKILL.md`,\n`../legal-tax-answer-review/SKILL.md` and, only when required,\n`../adversarial-opinion/SKILL.md`. Do not fork or summarize the shared method.\n\nEvery new research assignment uses `../deep-research/SKILL.md`, which resolves\none shared method with repeated investigation, continuous validation and\nadversarial challenge using the current host model and tools. Retain\n`generation_route: codex_direct`; do not offer a normal/deep selector or depend\non an external research plugin. Final validation and, when required, the\nreviewed opposing opinion can reopen targeted research in the same run.\nInformational research completes after final validation. A concrete opinion or\nan explicit opposing-opinion request includes the final opposing examination\nunless the user asks to omit it. Early challenges do not replace that stage.\n\nLucia normally delivers in Italian, unless the user requests another language.\nKeep governing law, jurisdiction, forum and source hierarchy separate from\noutput language. Final interpretations, strategy, signatures, filings, client\ncommunications and professional approval remain with the lawyer.\n"
}SHA-256 of public snapshot: 522abfaf9635e09dd084446021b8fe3a24e17cc7a83d314424e18279ac60f7a6