integrate-skill

Integrate external skills into project guidelines and update .trellis/spec indexes.

21|4|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/Jerry-Z07/WindBoard --skill integrate-skill-jerry-z07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integrate-skill
Source: https://github.com/Jerry-Z07/WindBoard/tree/main/.agents/skills/integrate-skill
Command: npx skills add https://github.com/Jerry-Z07/WindBoard --skill integrate-skill-jerry-z07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adapts external skills into project-specific development guidelines within .trellis/spec, standardizing how new skills and patterns are introduced across the codebase.

Core Features & Use Cases

  • Creates dedicated guideline sections for each skill
  • Generates code example templates with a .template suffix and places them under .trellis/spec/{target}/examples/skills/<skill-name>/
  • Updates spec indexes to keep discovery consistent

Quick Start

Use integrate-external-skill to fold a new skill into your project guidelines with minimal friction

Frequently Asked Questions about integrate-skill

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

FAQPage Schema
How do I integrate external skills into project development guidelines?

To integrate external skills into project development guidelines, you can create dedicated guideline sections within .trellis/spec. This standardizes how new patterns are introduced across your codebase for consistent team adoption.

How do I standardize new skill adoption across frontend and backend teams?

Standardize new skill adoption by updating spec indexes in .trellis/spec to keep discovery consistent across frontend and backend teams. This ensures everyone references the same centralized guidelines.

Where should I place code example templates for skill integration?

Code example templates for skill integration should be generated with a .template suffix and placed under .trellis/spec/{target}/examples/skills/<skill-name>/ to maintain a standardized directory structure.

Does skill integration generate direct project code or documentation updates?

Skill integration enforces non-code updates such as document templates and index maintenance rather than direct project code generation. It focuses on standardizing how new skills are adopted through documentation.

What is the best way to maintain spec indexes for consistent skill discovery?

The best way to maintain spec indexes for consistent skill discovery is to update the .trellis/spec indexes whenever a new skill is folded into the project guidelines, ensuring centralized and accurate references.