skillify

Codify a successful /scrape flow into script.ts, script.test.ts, and a fixture.

Updated May 6, 2026
One-click install
npx skills add https://github.com/stayconnectquick/gstack --skill skillify-stayconnectquick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skillify
Source: https://github.com/stayconnectquick/gstack/tree/main/skillify
Command: npx skills add https://github.com/stayconnectquick/gstack --skill skillify-stayconnectquick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codifies the most recent successful /scrape flow into a permanent browser-skill on disk to enable quick replays.

Core Features & Use Cases

  • Codifies the most recent successful /scrape flow into script.ts, script.test.ts, and a fixture for deterministic testing.
  • Runs the test in a temporary directory and prompts before committing changes to ensure safety and traceability.
  • Provides a quick way to save and reuse a scraping intent when the user asks for "skillify", "codify this scrape", or "save this scrape".

Quick Start

Say "skillify this scrape" to codify the latest successful /scrape flow into a permanent browser-skill, then the system will test it and prompt before saving.

Frequently Asked Questions about skillify

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

FAQPage Schema
How do I save a successful web scrape as a reusable automation script?

To save a successful web scrape as a reusable automation script, you can codify the latest scraping flow into a permanent browser-skill on disk. This generates script.ts, script.test.ts, and a fixture for deterministic testing.

What is the fastest way to replay a browser scraping workflow?

Replaying a browser scraping workflow is fastest when you codify the successful flow into a permanent browser-skill. This speeds up execution to approximately 200ms for future scrapes with the same intent.

How do I generate test fixtures for browser automation scraping?

Generating test fixtures for browser automation scraping happens automatically when you codify a successful scrape. The system creates script.test.ts and a fixture file to ensure deterministic testing of the scraping intent.

Can I review scraping code changes before committing them to disk?

You can review scraping code changes before committing them because the system runs tests in a temporary directory and prompts you before saving. This ensures safety and traceability for your permanent browser-skills.

Does codifying a scrape workflow require manual test setup?

Codifying a scrape workflow does not require manual test setup. The system automatically runs a temp-dir test run and generates the necessary script and test files before prompting you to commit the browser-skill.