skillify

Converts ad-hoc browse or scrape flows into reusable vibestack SKILL.md definitions.

5|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/timurgaleev/vibestack --skill skillify-timurgaleev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skillify
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/skillify
Command: npx skills add https://github.com/timurgaleev/vibestack --skill skillify-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning ad-hoc browse or scrape flows into reusable vibestack SKILL.md entries so workflows can be saved, shared, and re-run reliably.

Core Features & Use Cases

  • Capture intent, trigger phrases, steps, and outputs from a successful flow.
  • Save as a properly structured skills/<name>/SKILL.md and install for seamless reuse.
  • Validate, render, and install to make the new skill available to compatible agents.

Quick Start

Pin down a working flow, write skills/<name>/SKILL.md with proper frontmatter and sections, then render and install.

Frequently Asked Questions about skillify

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

FAQPage Schema
How do I convert an ad-hoc web scraping flow into a reusable automation skill?

To convert an ad-hoc web scraping flow into a reusable automation skill, you capture the intent, triggers, steps, and outputs, then save them as a structured SKILL.md file. This formalizes the flow so it can be validated, installed, and re-run reliably.

What is a SKILL.md definition and when do I need it for workflow automation?

A SKILL.md definition is a structured markdown file with frontmatter and sections that formalizes a successful browse or scrape flow. You need it when you want to persist an ad-hoc workflow as a named skill for future reliable execution.

What frontmatter is required to codify a workflow into a vibestack skill?

To codify a workflow into a vibestack skill, the required frontmatter includes name, description, allowed-tools, and triggers. It also requires a 'When to invoke' section and a structured body to ensure the skill can be properly rendered and installed.

How do I save and install a captured workflow as a new skill?

You save and install a captured workflow by writing the formalized flow to skills/<name>/SKILL.md with proper frontmatter and sections. Once saved, you render and install it to make the new skill available to compatible agents.

What's the best way to persist successful browse flows for future reuse?

The best way to persist successful browse flows is to codify them into a reusable vibestack skill. This involves capturing the flow's intent and steps into a SKILL.md definition, allowing the workflow to be saved, shared, and re-run reliably.