fp-smoke-test

Name: fp-smoke-test
Availability: InStock
Author: Endor

Execute comprehensive smoke tests on CLI, library, web API, and web UI applications.

6|Updated Mar 6, 2026

Search Tags:#manual testing #e2e testing #smoke test #exploratory testing #application verification

Ready to run

npx skills add https://github.com/endorhq/flightplanner --skill fp-smoke-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fp-smoke-test
Source: https://github.com/endorhq/flightplanner/tree/main/skills/fp-smoke-test
Command: npx skills add https://github.com/endorhq/flightplanner --skill fp-smoke-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a direct, agent-driven method to manually verify application behavior and identify issues that automated tests might miss, ensuring end-to-end functionality in a live environment.

Core Features & Use Cases

Manual Exploration: Guides an agent through interactive testing of CLI tools, libraries, web APIs, or web UIs.
Environment Verification: Confirms that the application functions correctly outside of automated test suites.
Use Case: After deploying a new version of a web API, use this Skill to manually test critical endpoints and user flows to catch any regressions before they impact users.

Quick Start

Use the fp-smoke-test skill to perform a smoke test on the application, focusing on the user registration and login workflows.

Frequently Asked Questions about fp-smoke-test

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

FAQPage Schema

How do I manually verify application behavior after deployment?▼

To manually verify application behavior after deployment, you can run a smoke test that directly interacts with the application's interface to check end-to-end functionality. This process covers discovery, exercise, capture, and reporting phases to identify regressions.

What is exploratory testing for catching issues automated tests miss?▼

Exploratory testing for catching missed issues is an agent-driven method to manually verify application behavior in a live environment. It guides direct interaction with entry points to identify end-to-end functionality regressions beyond automated suites.

Can I perform a smoke test on different application types like web APIs and CLIs?▼

Yes, you can perform a smoke test on different application types including CLI, library, web API, and web UI. The testing process adapts to interact directly with the specific interface or entry points of each application type.

How do I test critical web API endpoints and user flows manually?▼

To test critical web API endpoints and user flows manually, execute a comprehensive smoke test that interacts directly with the API. This verifies end-to-end behavior and catches regressions before they impact users.

Does manual smoke testing work without existing automated test suites?▼

Yes, manual smoke testing works independently of automated test suites to confirm environment verification. It provides a direct, agent-driven method to interact with application entry points and verify live end-to-end behavior.