skillify

Extracts workflows from sessions and drafts reusable SKILL.md documents with placement guidance.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Pryma-Tech/iris --skill skillify-pryma-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skillify
Source: https://github.com/Pryma-Tech/iris/tree/main/cli/skills/skillify
Command: npx skills add https://github.com/Pryma-Tech/iris --skill skillify-pryma-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn repeatable task sessions into reusable OMC skill drafts, enabling rapid capture and reuse of proven automation patterns.

Core Features & Use Cases

  • Identify repeatable tasks from the current session and extract inputs, ordered steps, success criteria, and constraints.
  • Decide whether the workflow should live as a repo-built skill, a user/project learned skill, or documentation only.
  • Draft the SKILL.md content with clear triggers, steps, and success criteria, and surface any open questions.

Quick Start

Capture a repeatable session workflow and draft a new SKILL.md with inputs, steps, success criteria, and placement guidance.

Frequently Asked Questions about skillify

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

FAQPage Schema
How do I turn repeatable session workflows into reusable documentation?

Workflow extraction identifies repeatable task patterns by capturing inputs, ordered steps, success criteria, and constraints directly from your active session. It then structures these elements into a draft to propose a reusable automation pattern for future sessions.

How do I create a structured skill draft from an automation workflow?

You create a structured skill draft by running this Skill on your current session; it extracts the workflow steps, triggers, and success criteria, then outputs a complete SKILL.md draft. The draft includes recommended placement and any open questions for refinement.

When should a workflow be a repo-built skill versus documentation-only?

A workflow should be a repo-built skill, a user/project learned skill, or documentation-only depending on its complexity and reuse frequency. The Skill evaluates the extracted workflow constraints and placement guidance to recommend the most appropriate category for your automation pattern.

What is the best way to document automation patterns for team reuse?

The best way to document automation patterns for team reuse is to extract the ordered steps, triggers, and success criteria into a structured SKILL.md draft. This approach captures proven workflows during your session and surfaces open questions to ensure the pattern is reliable.

Do I need any dependencies to extract workflows from a session?

No dependencies are required to extract workflows from a session and generate a skill draft. The Skill operates independently to identify repeatable tasks, document the inputs and steps, and propose the appropriate placement without external tools.