skillify

Extract session workflow details into a reusable OMC skill file with YAML frontmatter.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill skillify-cheggin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skillify
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/skillify
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill skillify-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn repeated, manual session workflows into reusable, codified skills that can be instantiated across projects.

Core Features & Use Cases

  • Extracts inputs, ordered steps, success criteria, and constraints from a completed session.
  • Decides whether the result should be a repo-built skill, a learned/user skill, or documentation-only.
  • Produces a ready-to-use skill file beginning with YAML frontmatter and a structured workflow section.

Quick Start

Draft a complete skill file for the identified repeatable workflow, starting with YAML frontmatter and a clear set of triggers and steps.

Frequently Asked Questions about skillify

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

FAQPage Schema
How do I turn a repeatable workflow into a reusable skill?

To turn a repeatable workflow into a reusable skill, you extract inputs, ordered steps, success criteria, and constraints from a completed session, then package them into a structured skill file with YAML frontmatter.

What is the best way to capture manual session steps for project automation?

Capturing manual session steps for project automation involves identifying repeatable tasks, extracting explicit triggers and success criteria, and formatting them into a complete skill file that can be instantiated across projects.

How do I generate a skill file with YAML frontmatter?

Generate a skill file with YAML frontmatter by drafting a complete workflow definition that includes explicit triggers, ordered steps, success criteria, and notes on unresolved decisions or fuzzy areas for safety.

Should my captured workflow be a repo-built skill or documentation-only?

Decide whether your captured workflow should be a repo-built skill, a learned user skill, or documentation-only by applying the workflow logic to evaluate the extracted inputs, steps, and optimal storage location.

Does skill generation work for documenting fuzzy or unresolved workflow areas?

Yes, skill generation works for fuzzy areas by requiring the resulting skill draft to explicitly note unresolved decisions or constraints, ensuring safety when the workflow is instantiated across projects.