skill-derive

Convert a recurring local workflow into a reusable workspace skill draft.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/HuaGCS/Hahobot --skill skill-derive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-derive
Source: https://github.com/HuaGCS/Hahobot/tree/main/hahobot/skills/skill-derive
Command: npx skills add https://github.com/HuaGCS/Hahobot --skill skill-derive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn a repeatedly successful local workflow into a reusable workspace skill draft, enabling repeatability and knowledge capture.

Core Features & Use Cases

  • Capture when to use the workflow, what evidence to gather first, the exact tool sequence or command family, known pitfalls, and clear stop conditions.
  • Make the workflow portable inside the current workspace so future runs can reproduce the outcome without re-creating steps.
  • Provide a structured draft that can be tailored into a shared skill for teammates or future you.

Quick Start

Describe a successful workflow you want to turn into a reusable skill, including when to use it, evidence to gather, the exact tool sequence, known pitfalls, and stop conditions.

Frequently Asked Questions about skill-derive

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

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

To turn a repeatable workflow into a reusable skill draft, you capture the usage context, evidence, exact tool sequences, known failure patterns, and clear stop conditions to produce a portable workspace skill.

What context do I need to capture to automate a recurring project workflow?

Capturing a recurring project workflow requires documenting when to use it, gathering initial evidence, listing the exact command family, noting known pitfalls, and defining clear stop conditions to ensure a portable skill draft.

Can I create a reusable workspace skill for a debugging flow or release checklist?

Yes, you can create a reusable workspace skill for debugging flows, release checklists, and migrations by converting the successful local workflow sequence into a structured draft for future project runs.

What is the best way to document known failure patterns for a workflow automation draft?

The best way to document failure patterns for workflow automation is to record the exact tool sequences, known pitfalls encountered, and clear stop conditions alongside the initial usage context within the generated skill draft.

Does generating a workspace skill draft require capturing tool sequences and stop conditions?

Yes, generating a workspace skill draft requires capturing the exact tool sequences, known failure patterns, and clear stop conditions to make the local workflow portable and reproducible inside the current workspace.

When should I not use a skill draft for workflow automation?

You should not use a skill draft for workflow automation if the local workflow is not repeatedly successful, lacks clear stop conditions, or cannot provide the necessary usage context and evidence for reproducibility.