alfadocs-sanity-check

Verify AlfaDocs app build, authentication, API connectivity, and safety guardrails.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/alfadocs/ai-harness-instructions --skill alfadocs-sanity-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alfadocs-sanity-check
Source: https://github.com/alfadocs/ai-harness-instructions/tree/main/lovable/skills/alfadocs-sanity-check
Command: npx skills add https://github.com/alfadocs/ai-harness-instructions --skill alfadocs-sanity-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a fast pre-ship smoke check for AlfaDocs apps so you can quickly confirm the app actually runs, connects, and avoids obvious security or implementation blockers before a demo or release.

Core Features & Use Cases

  • Build and runtime verification: Checks that the app builds cleanly, loads without a blank screen, and stays free of console errors and leaked logging.
  • End-to-end connectivity check: Confirms authentication works, /me returns real tenant IDs, and at least one additional API call succeeds with the correct auth header.
  • Safety and architecture guardrails: Flags server-side secret handling, tenant-scoped access, kit-only UI usage, and correct webhook and CORS behavior.
  • Use case: A developer finishing an AlfaDocs integration can run this as the first pass before deeper reviews to catch the most common shipping blockers.

Quick Start

Use this skill to perform a fast pre-ship sanity check on the AlfaDocs app and identify any blockers before moving on to deeper review skills.

Frequently Asked Questions about alfadocs-sanity-check

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

FAQPage Schema
How do I run a pre-ship smoke test for an AlfaDocs API integration?

A pre-ship smoke test for an AlfaDocs integration verifies build health, successful login, real /me responses, authenticated API calls, and server-side secret storage before sharing or demoing your app.

What should an AlfaDocs sanity check verify before releasing an app?

An AlfaDocs sanity check should verify a clean build, working OAuth or API-key flows, correct webhook handling, tenant scoping, restricted CORS, and kit-only frontend implementation to catch shipping blockers.

Does my AlfaDocs app need server-side secret storage to pass a pre-ship check?

Yes, your AlfaDocs app needs server-side secret storage to pass a pre-ship check, as this safety guardrail prevents leaked secrets and ensures authentication flows remain secure before release.

How do I validate OAuth and webhook handling before launching an AlfaDocs integration?

Validate OAuth and webhook handling by confirming successful login, checking that /me returns real tenant IDs, and ensuring at least one authenticated API call succeeds with the correct auth header.

What are common shipping blockers caught by an AlfaDocs pre-launch connectivity check?

Common shipping blockers include blank screens on load, console errors, leaked logging, incorrect tenant scoping, unrestricted CORS, and frontend implementations that fail to use the required kit-only components.

Can I use a sanity check to test API connectivity and CORS restrictions for my app?

Yes, you can use a sanity check to test API connectivity by confirming authenticated calls succeed, and to verify CORS restrictions are properly enforced to prevent unauthorized access before launch.