smoke-test

Run runtime health checks on PopKit for plugin loading and connectivity.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jrc1883/popkit-claude --skill smoke-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test
Source: https://github.com/jrc1883/popkit-claude/tree/main/skills/pop-smoke-test
Command: npx skills add https://github.com/jrc1883/popkit-claude --skill smoke-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that PopKit runtime components are functional after updates or on a fresh session without performing full integration tests.

Core Features & Use Cases

  • Runtime visibility: checks plugin loading, hooks, cloud connectivity, and session state.
  • Fast validation: ensures core paths are working before deeper testing.
  • Guided output: provides concise PASS/FAIL summaries with steps.

Quick Start

Run the quick smoke test to confirm PopKit is functioning.

Frequently Asked Questions about smoke-test

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

FAQPage Schema
How do I verify PopKit is working after an update?

Run a smoke test to quickly verify PopKit runtime health. It checks plugin loading, hook responsiveness, API connectivity, and session state without requiring full integration tests, confirming core functionality is operational after updates or fresh sessions.

What does a PopKit smoke test validate?

A smoke test validates command availability, hook responses, API key presence, endpoint reachability, and STATUS.json read/write access. It confirms both functional and technical requirements are met for typical PopKit usage scenarios.

When should I run a PopKit health check?

Run health checks after updating PopKit or starting a new session to validate plugin loading and session state management before deeper testing. Quick runtime verification ensures core paths are functioning before proceeding with full integration tests.

Can I use a smoke test instead of full integration testing?

A smoke test provides fast validation of core runtime components but is not a replacement for full integration testing. It confirms basic functionality and cloud connectivity are working, allowing you to proceed with confidence to more comprehensive testing.

What happens if a PopKit health check fails?

The smoke test provides concise PASS/FAIL summaries with specific steps, identifying which components failed—such as plugin loading, hook responsiveness, API connectivity, or file access—so you can troubleshoot the exact issue.