dev-skillify

Create custom skill files with YAML frontmatter and workflow steps.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-skillify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-skillify
Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/dev-skillify
Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-skillify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many useful developer and workspace processes remain ad-hoc and are lost or repeated manually; this Skill guides users to formalize those processes as reusable SKILL.md files so they can be reliably reinvoked. It reduces knowledge loss and speeds repetitive operational tasks by turning a described workflow into a discoverable, triggerable skill.

Core Features & Use Cases

  • Guided interview to capture the trigger, slug, inputs, workflow steps, outputs, and anti-patterns for a new skill.
  • Enforces naming and frontmatter conventions (custom- prefix, name and description fields) and explains how to add optional helper scripts or templates.
  • Verification steps and best-practice checks to avoid duplicate skills, one-off tasks, or unsafe project-specific values.
  • Use case: a developer asks to "create a daily QA checklist" and receives a validated custom-skill scaffold with a clear trigger, workflow, and output path.

Quick Start

Create a custom skill by choosing a short kebab-case slug, writing a one-line description with trigger phrases, listing the required inputs and outputs, and outlining the step-by-step workflow.

Frequently Asked Questions about dev-skillify

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

FAQPage Schema
How do I create a reusable workflow as a custom skill file?▼

To create a reusable workflow, this skill formalizes your ad-hoc processes into a SKILL.md file with YAML frontmatter, a custom- slug folder, explicit inputs, outputs, and step-by-step instructions.

What do I need to include in a SKILL.md frontmatter to automate a workflow?▼

A SKILL.md frontmatter requires a name and description to automate a workflow, and the file must be placed in a folder using the custom-{slug} naming convention alongside optional helper scripts or templates.

When should I formalize a repeatable workflow into a triggerable skill?▼

You should formalize a repeatable workflow into a triggerable skill when you want to reduce knowledge loss, speed up repetitive operational tasks, and make developer processes reliably reinvokable by a single command.

How does the guided interview process work for generating new devtools skills?▼

The guided interview process for generating new devtools skills captures the trigger, slug, inputs, workflow steps, outputs, and anti-patterns, followed by verification checks to prevent duplicate skills or unsafe project-specific values.

Can I add helper scripts and templates to my custom skill directory?▼

Yes, you can add helper scripts or templates to your custom skill directory by placing them adjacent to the SKILL.md file, allowing the validated custom-skill scaffold to execute more complex automated operations.

What validation checks prevent duplicate skills or one-off tasks during skill creation?▼

Verification steps and best-practice checks during skill creation prevent duplicate skills, one-off tasks, or unsafe project-specific values by ensuring the workflow is genuinely repeatable and follows naming conventions.