forge-export

Export a dev-forge marketplace into a new standalone repository.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/dmedina-dev/dev-forge --skill forge-export
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-export
Source: https://github.com/dmedina-dev/dev-forge/tree/main/plugins/forge-export/skills/forge-export
Command: npx skills add https://github.com/dmedina-dev/dev-forge --skill forge-export

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It lets users create a clean, standalone marketplace repository from an existing dev‑forge marketplace, enabling personal or team use without retaining the original environment.

Core Features & Use Cases

  • Guided interview that collects marketplace name, description, destination, and ownership details.
  • Plugin detection and classification into external or native, with customization counting.
  • Selective plugin inclusion with dependency validation and optional native content copying.
  • Hook analysis to package project‑level hooks as a dedicated plugin.
  • Automatic file generation for marketplace.json, README, CLAUDE.md, docs, and install scripts, followed by Git initialization.

Quick Start

Run the forge-export skill and follow its prompts to generate a new marketplace repository.

Frequently Asked Questions about forge-export

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

FAQPage Schema
How do I export a dev-forge marketplace to a new standalone repository?

You export a dev-forge marketplace by following a guided interview that collects naming and destination details, selectively includes plugins with dependency validation, packages hooks, and generates configuration files into a new Git repository.

What does it mean to package project-level hooks when exporting a marketplace?

Packaging project-level hooks during a marketplace export means analyzing existing hooks and bundling them into a dedicated plugin, ensuring custom automation logic transfers cleanly to the new standalone repository.

Can I selectively include plugins and validate dependencies when exporting a marketplace?

Yes, you can selectively include plugins during the export process. The skill performs dependency validation, classifies plugins as external or native, and allows optional copying of native content to the new repository.

Do I need specific permissions to export a dev-forge marketplace into a standalone repo?

You need read access to the source marketplace files and write permission to create a new repository. These permissions allow the skill to read existing configurations and generate new standalone repository files.

What files are automatically generated when creating a standalone marketplace repository?

The export process automatically generates a marketplace.json file, README, CLAUDE.md, documentation, and install scripts, providing the necessary configuration and structure for personal or team use in the new repository.