gstack-skillify

You can codify a successful web scraping flow into a permanent on-disk browser skill by asking your assistant to skillify it. This converts the conversation history into a reusable script for future runs.

Browser automation reruns slowly because it re-drives the entire page flow each time. Codifying the scrape intent into a permanent skill replays the script in about 200ms instead of re-driving the browser.

To generate test files for a browser scraping script, the skillify process walks back through conversation history, synthesizes script.ts and script.test.ts plus a fixture, and runs the generated test in a temporary directory.

You can automate web scraping tasks without rewriting code by codifying the scrape intent into a durable on-disk skill. This saves the most recent scrape flow as a reusable script that runs quickly when matched again.

The skillify process does not commit code changes automatically; it gates commits behind an interactive confirmation step. It reconstructs the script and tests, validates them in a temp directory, and asks before committing permanently.

You should codify a browser scrape into a permanent skill immediately after you have a successful scrape you want to make permanent. This prevents re-driving the same page and conversation for identical scrape intents later.