silver-migrate

Migrate Silver Bullet projects from Claude Desktop SB to Forge-compatible setups.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill silver-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: silver-migrate
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/silver-migrate
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill silver-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates a Silver Bullet project from Claude Desktop SB or older Forge SB to a Forge-compatible setup, reconciling paths, removing hook-only artifacts, and generating Forge-equivalent scaffolding.

Core Features & Use Cases

  • Detect migration source (Claude Desktop SB indicators, legacy Forge SB patterns) and inventory artifacts (planning state, project context, and configuration)
  • Translate artifacts to Forge equivalents, preserving project intent and gating rules
  • Remove Claude-only artifacts and generate Forge-side guidance (AGENTS.md) for the migrated project
  • Verify and align the global skill+agent set to ensure continued enforcment and governance

Quick Start

Run the migration tool on your project to convert Claude Desktop SB or older Forge SB scaffolding into Forge-compatible artifacts.

Frequently Asked Questions about silver-migrate

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

FAQPage Schema
How do I migrate a Silver Bullet project from Claude Desktop to Forge?

Migrate a Silver Bullet project by running a migration tool that detects Claude Desktop SB indicators, inventories existing artifacts, and converts them into Forge-compatible scaffolding. This preserves your project intent and planning state.

What does a Forge project migration do with legacy planning state and artifacts?

A Forge project migration preserves legacy planning state while translating artifacts into Forge equivalents. It removes Claude-only artifacts and generates an AGENTS.md file to provide Forge-side guidance for the project.

Can I update older Forge SB scaffolding to be compatible with the latest Forge setup?

Yes, you can update older Forge SB scaffolding by running the migration process. It detects legacy Forge SB patterns, reconciles project paths, and aligns the global skill and agent set to ensure continued governance enforcement.

How to generate AGENTS.md and remove Claude-only artifacts during project setup?

Generate AGENTS.md and remove Claude-only artifacts by executing the Silver Bullet migration. The process inventories your project context, strips incompatible hooks, and outputs Forge-equivalent scaffolding with updated guidance.

Does migrating to Forge preserve my existing project context and gating rules?

Migrating to Forge preserves existing project context and gating rules. The migration translates artifacts into Forge equivalents while maintaining the original project intent and enforcement policies.

What are the limitations of migrating a Silver Bullet project to Forge?

The migration removes Claude-only artifacts and hook-only configurations that do not translate to Forge. You must verify the global skill and agent set post-migration to ensure complete compatibility and continued enforcement.