atlan-fact-verification-gate

Verify Atlan app behavior against SDK and CLI references.

4|7|Updated Apr 30, 2025
One-click install
npx skills add https://github.com/atlanhq/atlan-sample-apps --skill atlan-fact-verification-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atlan-fact-verification-gate
Source: https://github.com/atlanhq/atlan-sample-apps/tree/main/.agents/skills/atlan-fact-verification-gate
Command: npx skills add https://github.com/atlanhq/atlan-sample-apps --skill atlan-fact-verification-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill validates Atlan app behavior against SDK/docs and CLI references to prevent risky, behavior-changing decisions.

Core Features & Use Cases

  • Lightweight verification checkpoint before critical decisions in build, modify, test, review, or release workflows.
  • Reads sources from SDK/CLI documentation and generates a portable verification_manifest.json for traceability.
  • Records evidence provenance from local checkout, installed package, or remote sources to support auditability.
  • Applies across quick-start and production workflows to ensure alignment with official guidance.

Quick Start

  1. Trigger the verification workflow for your app task (build, modify, test, review, or release).
  2. Review the generated verification_manifest.json and the provenance evidence.
  3. If needed, adjust inputs and re-run to reach a ready state.

Frequently Asked Questions about atlan-fact-verification-gate

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

FAQPage Schema
How do I verify Atlan app behavior before deploying changes?

Verification gates check your app against official SDK and CLI references to catch behavior-changing decisions before build, test, review, or release. Generate a verification_manifest.json from a template, run validation, and review the provenance evidence to confirm alignment with documented behavior.

What does a verification manifest do and why do I need one?

A verification manifest is a portable JSON record that documents your app's behavior against SDK/CLI sources and records where evidence came from—local checkout, installed package, or remote sources. It provides auditability and traceability for risky decisions across your workflow.

Can I use verification gates in production workflows?

Yes, verification gates apply to both quick-start and production workflows. They work as lightweight checkpoints across build, modify, test, review, and release tasks to ensure your app remains aligned with official Atlan guidance at each stage.

How do I know if verification failed and what to do next?

Review the generated verification_manifest.json and provenance evidence after running validation. If verification shows misalignment, adjust your inputs based on the evidence and re-run the gate to reach a ready state before proceeding.

What sources does the verification gate check against?

The verification gate reads from SDK documentation and CLI references to validate your app behavior. It records the provenance of evidence from local checkouts, installed packages, or remote sources to support your verification audit trail.