integrate-skill

Integrate external skill documentation into .trellis/spec guideline files.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/MaplumeX/deepresearch --skill integrate-skill-maplumex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integrate-skill
Source: https://github.com/MaplumeX/deepresearch/tree/main/.agents/skills/integrate-skill
Command: npx skills add https://github.com/MaplumeX/deepresearch --skill integrate-skill-maplumex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes and adapts external reusable skill instructions into project-specific development guidelines so teams can follow consistent conventions instead of scattering examples and ad-hoc notes across repositories.

Core Features & Use Cases

  • Adds a dedicated section for the skill in the appropriate .trellis/spec/{target}/doc.md that covers overview, project adaptation, usage steps, caveats, and reference examples.
  • Creates an examples directory with code example templates using a .template suffix under .trellis/spec/{target}/examples/skills/<skill-name>/ to avoid IDE issues and provide runnable patterns for developers.
  • Updates quick navigation/index files to include the new skill section for discoverability, and produces an integration report summarizing compatibility and required dependencies.
  • Use case: Integrate a backend MCP-building skill into .trellis/spec/backend/ with server templates and index entries for onboarding backend engineers.

Quick Start

Integrate the mcp-builder skill into the backend guidelines and create example templates under .trellis/spec/backend/examples/skills/mcp-builder/.

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 skill documentation into project guidelines?▼

Integrating external skill documentation into project guidelines involves adding a dedicated section in .trellis/spec/{target}/doc.md covering overview, usage steps, caveats, and reference examples to standardize developer onboarding.

What is the best way to add third-party skill examples to .trellis spec files?▼

The best way to add third-party skill examples to .trellis spec files is creating example template files with a .template suffix under .trellis/spec/{target}/examples/skills/<skill-name>/ to provide runnable patterns and avoid IDE issues.

How does integrating external skills into guidelines improve developer onboarding?▼

Integrating external skills into guidelines improves developer onboarding by centralizing reusable instructions into project-specific conventions, updating quick navigation index files for discoverability, and producing an integration report summarizing compatibility.

Can I use this approach to add an MCP-building skill to backend spec guidelines?▼

Yes, you can use this approach to integrate an MCP-building skill into backend spec guidelines. It creates server templates and index entries under .trellis/spec/backend/ specifically for onboarding backend engineers.

Why do example template files use a .template suffix in the .trellis directory?▼

Example template files use a .template suffix in the .trellis directory to avoid IDE issues that would occur with standard code files, while still providing runnable patterns and reference examples for developers.