Jackie Fact Authority

Sanitize property reports and enforce locked fact sheets before HTML export.

Updated Aug 8, 2026
One-click install
npx skills add https://github.com/dgoldoff-hue/camelot-scout-v6 --skill jackie-fact-authority
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Jackie Fact Authority
Source: https://github.com/dgoldoff-hue/camelot-scout-v6/tree/main/.codex/skills/jackie-fact-authority
Command: npx skills add https://github.com/dgoldoff-hue/camelot-scout-v6 --skill jackie-fact-authority

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents generated property reports and outreach materials from carrying stale or incorrect facts like addresses, unit counts, management names, missing assets, or mismatched report data.

Core Features & Use Cases

  • Canonical fact authority: normalizes known properties and resolves conflicts so narrative writing is grounded in locked, verified fact sheets.
  • Render sanitizer: scrubs stale cached tokens from final HTML outputs before preview, download, email, print, archive, or CRM push.
  • Source-of-truth archive: saves the generated report metadata (filename, timestamp, generator, contacts, and package type) so proposal and agreement modules do not recompute facts differently.
  • Known-property guardrails: applies property-specific correction rules (e.g., specific condominium profiles and verified local asset sets) before report rendering and after HTML assembly.
  • Verification workflow: enforces a post-change validation run (verify, lint, build) and supports regression smoke tests for known-property correctness.

Quick Start

Use the Jackie Fact Authority skill to sanitize and regenerate property-facing documents for a specific building so the output uses the locked fact sheet and passes verify:jackie, then export or preview the corrected HTML for internal review.

Frequently Asked Questions about Jackie Fact Authority

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent stale property facts from appearing in generated outreach documents?

To prevent stale property facts in generated outreach documents, you need canonical fact locking and HTML render sanitization. This normalizes known properties, resolves conflicts, and scrubs outdated cached tokens before preview or download.

What is canonical fact locking for condominium profiles?

Canonical fact locking for condominium profiles is the process of normalizing property data and resolving conflicts from uploaded files and public records. This grounds narrative writing in verified fact sheets to ensure report accuracy.

How do I sanitize HTML output to remove incorrect property data before CRM push?

You sanitize HTML output to remove incorrect property data before a CRM push by applying a render sanitizer. This scrubs stale cached tokens from final HTML assemblies after property-specific guardrail rules are applied.

Why does my generated property card contain mismatched unit counts and management names?

Generated property cards contain mismatched unit counts and management names when conflicting or outdated information exists across uploaded files and saved cards. Applying known-property guardrails normalizes data before rendering.

What's the best way to validate property facts after updating a report?

The best way to validate property facts after updating a report is running a post-change verification workflow. Enforcing verify, lint, and build steps supports regression smoke tests to ensure known-property correctness.