integrate-skill

Integrates external skills into frontend/backend guideline documents via .trellis/spec/{target}/ directories.

3.9k|339|Updated Feb 3, 2026

Search Tags:#templates #documentation #guidelines #code-examples #project-standards #skill-integration

Ready to run

npx skills add https://github.com/zhukunpenglinyutong/desktop-cc-gui --skill integrate-skill-zhukunpenglinyutong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: integrate-skill
Source: https://github.com/zhukunpenglinyutong/desktop-cc-gui/tree/main/.agents/skills/integrate-skill
Command: npx skills add https://github.com/zhukunpenglinyutong/desktop-cc-gui --skill integrate-skill-zhukunpenglinyutong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External skills often exist in silos; this process standardizes their incorporation into project development guidelines without touching source code, ensuring consistency across teams.

Core Features & Use Cases

Provides a standardized workflow to read a skill's SKILL.md, determine the target spec (frontend or backend), and populate the project's guideline documents.
Encourages creating code examples and templates under the designated .trellis/spec/{target}/ directories to support reproducible adoption.
Updates documentation indexes and quick-navigation entries to reflect newly integrated skills.

Quick Start

Execute the integration using a target skill name to update your project guidelines.

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?▼

Integrating external skills into project guidelines requires parsing a SKILL.md definition, mapping it to a target spec directory, and updating documentation indexes with consistent templates and code samples to ensure standardized team adoption without modifying source code.

What is the .trellis spec directory used for in skill integration?▼

The .trellis spec directory is used to store standardized guideline documents, templates, and code examples for newly integrated skills. It separates frontend and backend targets to maintain organized project standards and reproducible adoption workflows.

How do I standardize external skill documentation across frontend and backend teams?▼

You standardize external skill documentation by applying a consistent workflow that reads SKILL.md definitions and populates target spec directories. This ensures both frontend and backend teams follow unified project standards for templates and code examples.

Do I need a SKILL.md file to add new skills to a spec index?▼

Yes, a clear SKILL.md definition is required to add new skills to a spec index. This file dictates how the skill is documented, templated, and mapped to the correct target directory within your project guidelines.

Can I update documentation indexes without modifying the actual source code?▼

Yes, you can update documentation indexes and quick-navigation entries without modifying source code. The integration process standardizes how new skills are templated and added to spec indexes, ensuring consistency without touching application logic.

What's the best way to structure code examples and templates for project standards?▼

The best way to structure code examples and templates for project standards is to place them under designated .trellis/spec/{target}/ directories. This ensures reproducible adoption and aligns with the skill's defined SKILL.md structure.