skill-distillery

Name: skill-distillery
Availability: InStock
Author: Outfitter

Convert external code repositories into Claude Code plugins via a seven-stage workflow.

6|1|Updated Jan 22, 2026

Search Tags:#automation #plugin development #code conversion #repository analysis #claude plugins #skillcraft

Ready to run

npx skills add https://github.com/outfitter-dev/outfitter --skill skill-distillery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-distillery
Source: https://github.com/outfitter-dev/outfitter/tree/main/plugins/fieldguides/skills/skill-distillery
Command: npx skills add https://github.com/outfitter-dev/outfitter --skill skill-distillery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of converting external code repositories into functional Claude Code plugins, making complex tools accessible through an AI interface.

Core Features & Use Cases

Repo-to-Plugin Conversion: Guides users through analyzing a repository, identifying patterns, and codifying them into skills and commands.
Phased Workflow: Breaks down the conversion into manageable stages: Discovery, Recon, Pattern Identification, Mapping, Authoring, Packaging, and Audit.
Use Case: You have a powerful CLI tool in a GitHub repository that you want to expose to Claude. This Skill will help you analyze the CLI's commands and workflows, then package them into a usable Claude plugin.

Quick Start

Use the skill-distillery skill to turn the repository at 'https://github.com/example/my-cli-tool' into a Claude plugin.

Frequently Asked Questions about skill-distillery

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

FAQPage Schema

How do I convert a GitHub repository into a Claude Code plugin?▼

To convert a GitHub repository into a Claude Code plugin, this Skill automates the transformation by analyzing the repository structure, identifying repeatable patterns, and codifying them into functional skills, commands, hooks, and agents.

What is the process for turning a CLI tool into an AI-accessible plugin?▼

Turning a CLI tool into an AI-accessible plugin involves a structured seven-stage workflow: Discovery, Recon, Pattern Identification, Mapping, Authoring, Packaging, and Audit, which exposes the tool's commands to Claude.

Can I convert MCP servers and testing frameworks into Claude plugins?▼

Yes, you can convert MCP servers, build tools, testing frameworks, libraries, and CLI tools into Claude plugins using either the full pipeline or quick mode conversion supported by the Skill.

Does Claude plugin development require manual pattern identification from repositories?▼

Claude plugin development does not require manual pattern identification because the Skill facilitates the analysis of repository structure and automatically identifies repeatable patterns for codification.

What is the best way to package repository code into skills and commands?▼

The best way to package repository code into skills and commands is through the structured Authoring and Packaging stages of the conversion pipeline, which systematically codifies identified workflows into a usable plugin format.

What are the limitations of automating code conversion for Claude plugins?▼

Limitations of automating code conversion include relying on identifying repeatable patterns within the repository structure, meaning highly unique or unstructured codebases may not codify cleanly into functional Claude plugins.