trellis-meta

Diagnose and customize Trellis workflows, agents, skills, hooks, specs and task state in a user project.

10|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/tincopper/neeko --skill trellis-meta-tincopper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-meta
Source: https://github.com/tincopper/neeko/tree/main/.agents/skills/trellis-meta
Command: npx skills add https://github.com/tincopper/neeko --skill trellis-meta-tincopper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps an AI understand and modify the local Trellis architecture inside a user project, so the project’s workflow, context loading, and AI-entry behavior stay consistent.

Core Features & Use Cases

  • Local workflow guidance: Explains how Trellis phases, routing, and workflow-state prompts work inside the project.
  • Platform integration awareness: Covers hooks, agents, skills, commands, and platform-specific file layouts for supported AI tools.
  • Project customization support: Helps update task flow, context injection, specs, multi-agent channel behavior, and bundled-versus-local skill boundaries.
  • Use case: A team wants to change how AI reads tasks, specs, and session context across Claude, Codex, Cursor, and shared .trellis/ files without editing upstream Trellis source.

Quick Start

Read this skill, then inspect the project’s .trellis/workflow.md, .trellis/config.yaml, and relevant platform files before making local Trellis changes.

Frequently Asked Questions about trellis-meta

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

FAQPage Schema
How do I customize local Trellis workflow files without editing upstream source?

Customize local Trellis workflow files by modifying project-level .trellis configurations instead of upstream source. Read the project's authoritative local files like .trellis/workflow.md and .trellis/config.yaml first, then respect generated-file boundaries and template hashes to safely update task flow and context injection.

What is the best way to change multi-agent channel behavior in an existing Trellis project?

Change multi-agent channel behavior by diagnosing and updating local Trellis configurations across planning, implementation, checking, and memory workflows. Inspect platform-specific entry points and platform directories to modify how agents route context and tasks within the established .trellis file structure.

Can I update Trellis hooks and skills for multiple AI platforms like Claude, Cursor, and Codex?

Yes, you can update Trellis hooks and skills for multiple AI platforms. The system provides platform integration awareness covering hooks, agents, skills, commands, and platform-specific file layouts for supported AI tools like Claude, Codex, and Cursor across shared .trellis files.

How do bundled skills differ from project-local skills when modifying Trellis specs?

Bundled skills are upstream provided templates, while project-local skills are custom overrides within your .trellis directory. When modifying Trellis specs, respect bundled-skill versus project-local customization rules and generated-file boundaries to prevent overwriting upstream template hashes.

Why does my Trellis context loading break after modifying platform directories?

Trellis context loading breaks when modifications violate generated-file boundaries, template hashes, or platform-specific entry points. Diagnose the local Trellis architecture by reading the project's authoritative local files first to ensure workflow-state prompts and routing remain consistent.

Do I need to run trellis init before customizing agent workflows and task states?

Yes, you must run trellis init before customizing agent workflows and task states. This Skill applies exclusively to projects that already have the initialization complete and need changes to .trellis files, platform directories, or multi-agent channel behavior.