integrate-skill

Name: integrate-skill
Availability: InStock
Author: yizhitangtongxue

Integrates reusable skills into project development guidelines and example directories.

Updated Mar 24, 2026

Search Tags:#automation #workflow #templates #documentation #spec #guidelines #skill integration

Ready to run

npx skills add https://github.com/yizhitangtongxue/opencode-switch --skill integrate-skill-yizhitangtongxue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: integrate-skill
Source: https://github.com/yizhitangtongxue/opencode-switch/tree/main/.agents/skills/integrate-skill
Command: npx skills add https://github.com/yizhitangtongxue/opencode-switch --skill integrate-skill-yizhitangtongxue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams accumulate reusable AI skills but lack a consistent way to fold them into project documentation, so best practices stay scattered instead of becoming enforceable development guidelines. ## Core Features & Use Cases - Guideline Integration: Reads a skill's SKILL.md and writes an adapted section into `.trellis/spec/{target}/doc.md` with overview, project adaptation, usage steps, and caveats. - Example Scaffolding: Creates `examples/skills/<skill-name>/` directories containing `.template` code files that avoid IDE errors, plus index updates in `index.md`. - Integration Report: Produces a structured report covering tech stack compatibility, integration locations, dependencies, and a completion checklist. - Use Case: After adopting the `mcp-builder` skill, run the integration to add an MCP server development guide to your backend spec along with TypeScript template examples. ## Quick Start Ask the agent to integrate the mcp-builder skill into the project guidelines using the integrate-skill workflow.

Frequently Asked Questions about integrate-skill

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

FAQPage Schema

How do I integrate a skill into project guidelines?▼

Run the integrate-skill workflow with the skill name, for example $integrate-skill mcp-builder. It reads the skill's SKILL.md, determines the frontend or backend target, and writes a new section into the corresponding doc.md plus template examples.

Where are integrated skill guidelines stored?▼

Guidelines go into .trellis/spec/{target}/doc.md where target is frontend or backend based on skill type. Code examples are placed in examples/skills/<skill-name>/ under the same target directory, and index.md gets a navigation entry.

Why do example files use the .template suffix?▼

The .template suffix (e.g., component.tsx.template) prevents IDEs from treating example files as real project code, avoiding false type errors and lint warnings while keeping the examples readable and copyable.

What happens if the skill cannot be found?▼

The workflow first looks for .agents/skills/<skill-name>/SKILL.md in the repository and then the skill list in AGENTS.md. If neither exists, it asks the user to provide the source path or repository.

Does skill integration modify project source code?▼

No, integration only updates development guidelines and example templates. The core principle is that skill content becomes documentation in doc.md and .template example files, never direct modifications to project code.