adapt-external-docs

Adapt external agent, rule, and skill files to project conventions.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/linnefromice/claude-code-workspace --skill adapt-external-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adapt-external-docs
Source: https://github.com/linnefromice/claude-code-workspace/tree/main/template-.claude/skills/custom-samples/adapt-external-docs
Command: npx skills add https://github.com/linnefromice/claude-code-workspace --skill adapt-external-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams convert and align external agent, rule, and skill definitions to a project's specific formats and conventions, enabling consistent implementation across platforms.

Core Features & Use Cases

  • Frontmatter standardization: Normalize YAML frontmatter to the project schema.
  • Path and reference rewriting: Update references to project-relative paths and documentation.
  • Migration support: Facilitate moving definitions between repositories by applying project rules.

Quick Start

Use the adapt-external-docs command to align an external file with your project conventions:

  • /adapt-external-docs @.claude/agents/planner.md type=agent
  • /adapt-external-docs @.claude/rules/new-rule.md type=rule
  • /adapt-external-docs @.claude/skills/new-skill/SKILL.md type=skill

Frequently Asked Questions about adapt-external-docs

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

FAQPage Schema
How do I adapt external markdown documentation to match project standards?

To adapt external documentation to project standards, you normalize YAML frontmatter, rewrite paths to project-relative conventions, and validate syntax. This ensures migrated agents, rules, and skills conform immediately to local repository formats.

What is the best way to migrate generic agent definitions into a project-specific format?

Migrating generic agent definitions involves applying project rules to standardize frontmatter and resolve references. Using a dedicated adaptation command enforces these conventions and validates integration readiness during the repository consolidation process.

How do I normalize YAML frontmatter when consolidating external best-practices?

Normalizing YAML frontmatter during consolidation requires mapping external schema fields to your project's specific format. This standardization process enforces local conventions and validates syntax for seamless integration.

Can I use a single command to update file paths and references for external rules?

Yes, you can use an adaptation command to automatically rewrite paths and references to project-relative locations. This enforces project path conventions while validating integration readiness for external rules.

When do I need to conform external skills to local conventions during a repository migration?

You need to conform external skills to local conventions when consolidating best-practices across repositories. This migration process enforces project path conventions, standardizes frontmatter, and resolves references to ensure consistent implementation.