← Sistema Experto PPTCONTENT HISTORY

Update to Sistema Experto PPT

Snapshot Sep 30, 2026 · 23:18 UTC · version 4.0.3

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Audit, review, critique, score, evaluate, quality-check, or diagnose an existing presentation without changing it by default. Use for executive review, narrative review, evidence and citation review, design critique, accessibility review, technical PPTX inspection, template compliance, readiness assessment, or prioritized recommendations. Do not use when the primary request is to implement fixes, create a new deck, or produce a single new slide or chart.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 301
    },
    {
      "relative_path": "references/core/00_GOVERNANCE.md",
      "size_in_bytes": 3103
    },
    {
      "relative_path": "references/core/01_SEMANTIC_MODEL.md",
      "size_in_bytes": 2491
    },
    {
      "relative_path": "references/core/03_ANALYSIS_MATERIALITY.md",
      "size_in_bytes": 1240
    },
    {
      "relative_path": "references/core/04_CAPABILITY_ROUTING.md",
      "size_in_bytes": 1688
    },
    {
      "relative_path": "references/core/06_EVIDENCE_GOVERNANCE.md",
      "size_in_bytes": 1346
    },
    {
      "relative_path": "references/core/07_VISUAL_DATA_ACCESSIBILITY.md",
      "size_in_bytes": 958
    },
    {
      "relative_path": "references/core/08_PRODUCTION_INTEROP.md",
      "size_in_bytes": 1998
    },
    {
      "relative_path": "references/core/09_ASSURANCE.md",
      "size_in_bytes": 2138
    },
    {
      "relative_path": "references/core/11_AUDIT_RUBRIC.md",
      "size_in_bytes": 1082
    },
    {
      "relative_path": "references/core/12_CAPABILITY_BINDINGS.md",
      "size_in_bytes": 1520
    },
    {
      "relative_path": "references/core/13_PRIVACY_SECURITY_COMPLIANCE.md",
      "size_in_bytes": 3531
    },
    {
      "relative_path": "references/workflow.md",
      "size_in_bytes": 816
    }
  ],
  "name": "audit-presentation",
  "skill_md_contents": "---\nname: audit-presentation\ndescription: Audit, review, critique, score, evaluate, quality-check, or diagnose an existing presentation without changing it by default. Use for executive review, narrative review, evidence and citation review, design critique, accessibility review, technical PPTX inspection, template compliance, readiness assessment, or prioritized recommendations. Do not use when the primary request is to implement fixes, create a new deck, or produce a single new slide or chart.\n---\n\n# Audit presentation\n\nProduce an evidence-backed diagnosis that distinguishes material risks from preferences. Remain read-only unless the user separately requests implementation.\n\n## Workflow\n\n1. Read [governance](references/core/00_GOVERNANCE.md), [semantic model](references/core/01_SEMANTIC_MODEL.md), [materiality](references/core/03_ANALYSIS_MATERIALITY.md), [privacy/security](references/core/13_PRIVACY_SECURITY_COMPLIANCE.md), [audit rubric](references/core/11_AUDIT_RUBRIC.md) and [assurance](references/core/09_ASSURANCE.md).\n2. Apply [the audit workflow](references/workflow.md).\n3. Load only the applicable modules: [evidence](references/core/06_EVIDENCE_GOVERNANCE.md), [visual/data](references/core/07_VISUAL_DATA_ACCESSIBILITY.md) and [production](references/core/08_PRODUCTION_INTEROP.md).\n4. Use [capability routing](references/core/04_CAPABILITY_ROUTING.md) and [bindings](references/core/12_CAPABILITY_BINDINGS.md) when inspection needs tools.\n\n## Behavior\n\n- Establish the deck's intended audience, objective and use before judging it.\n- Inspect both overall story and individual critical slides.\n- Ground every finding in a slide, object, claim, rendering or missing requirement.\n- Classify severity and explain consequence, correction and verification.\n- Prioritize the few changes with highest decision/use impact.\n- Separate internal quality state from institutional approval.\n\n## Output contract\n\nLead with readiness and top risks. Then provide findings by severity, strengths worth preserving, prioritized remediation and validation conditions. Give a score only when the rubric and evidence make it meaningful.\n\n## Prohibitions\n\n- Do not call subjective taste a defect.\n- Do not infer factual correctness from visual polish.\n- Do not claim application-level inspection not performed.\n- Do not modify the deck without authorization.\n"
}

SHA-256 of public snapshot: 68fadf40b6f9ccabbb4ff6ab4462083a3dd8e44882a6bf7334ba0aaccceb8b97