How do I install the Dipeo Package Maintainer skill?

Run npx skillmds@latest add tomevault-io/dipeo-package-maintainer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dipeo Package Maintainer safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dipeo Package Maintainer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dipeo Package Maintainer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dipeo Package Maintainer?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dipeo Package Maintainer by tomevault-io

Name: Dipeo Package Maintainer
Author: tomevault-io

Dipeo Package Maintainer

Router skill for DiPeO runtime Python code (execution handlers, service architecture, domain models, LLM infrastructure). Use when task mentions node handlers, EventBus, ServiceRegistry, Envelope pattern, or domain logic. For simple tasks, handle directly; for complex work, escalate to dipeo-package-maintainer agent. Use when this capability is needed.

tomevault-io 0d14a8f 2 files · 3.7 KB Updated Sep 17, 2026

File contents

DiPeO Package Maintainer Router

Domain: Runtime Python in /dipeo/ (application, domain, infrastructure - EXCLUDING codegen and generated code).

Quick Decision: Skill or Agent?

✅ Handle Directly (This Skill)

Simple changes: <20 lines, 1-2 files
Read-only tasks: Understanding patterns, reviewing implementation
Pattern lookup: Envelope usage, service registration examples
Small fixes: Typos, minor refactors, simple handler tweaks

❌ Escalate to Agent

New node handlers: Creating handlers with complex logic
Service architecture: EventBus integration, ServiceRegistry configuration
Domain model changes: Conversation management, memory strategies
Multi-file refactoring: Affects >2 files or cross-layer changes
Generated code issues: If generated APIs don't work, escalate to dipeo-codegen-pipeline first

Agent: Task(dipeo-package-maintainer, "your detailed task description")

Documentation Sections (Load On-Demand)

Use Skill(doc-lookup) with these anchors when you need detailed context:

Architecture & Ownership:

docs/agents/package-maintainer.md#your-domain-of-expertise - Code layers and ownership
docs/agents/package-maintainer.md#core-architectural-principles - Service architecture, LLM integration

Implementation:

docs/agents/package-maintainer.md#your-responsibilities - Node handlers, services, GraphQL resolvers

Patterns & Imports:

docs/agents/package-maintainer.md#common-patterns - Envelope, service registry, node handlers
docs/agents/package-maintainer.md#key-import-paths - Common imports

Escalation:

docs/agents/package-maintainer.md#when-you-need-help-escalation-paths - When to escalate

Example doc-lookup call:

python .claude/skills/doc-lookup/scripts/section_search.py \
  --query "envelope-pattern" \
  --paths docs/agents/package-maintainer.md \
  --top 1

Escalation to Other Agents

To dipeo-codegen-pipeline: Generated code issues, TypeScript specs, new node types, GraphQL schema To dipeo-backend: CLI commands, server config, database schema, MCP server

Typical Workflow

Assess complexity: Simple pattern lookup vs. complex implementation
If simple: Load relevant section via Skill(doc-lookup), provide guidance or make small change
If complex: Escalate with Task(dipeo-package-maintainer, "task details")
Generated code problems: First check if it's a generation issue → escalate to dipeo-codegen-pipeline

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: dipeo-package-maintainerdescription: Router skill for DiPeO runtime Python code (execution handlers, service architecture, domain models, LLM infrastructure). Use when task mentions node handlers, EventBus, ServiceRegistry, Envelope pattern, or domain logic. For simple tasks, handle directly; for complex work, escalate to dipeo-package-maintainer agent. Use when this capability is needed.---# DiPeO Package Maintainer Router**Domain**: Runtime Python in `/dipeo/` (application, domain, infrastructure - EXCLUDING codegen and generated code).## Quick Decision: Skill or Agent?### ✅ Handle Directly (This Skill)- **Simple changes**: <20 lines, 1-2 files- **Read-only tasks**: Understanding patterns, reviewing implementation- **Pattern lookup**: Envelope usage, service registration examples- **Small fixes**: Typos, minor refactors, simple handler tweaks### ❌ Escalate to Agent- **New node handlers**: Creating handlers with complex logic- **Service architecture**: EventBus integration, ServiceRegistry configuration- **Domain model changes**: Conversation management, memory strategies- **Multi-file refactoring**: Affects >2 files or cross-layer changes- **Generated code issues**: If generated APIs don't work, escalate to dipeo-codegen-pipeline first**Agent**: `Task(dipeo-package-maintainer, "your detailed task description")`## Documentation Sections (Load On-Demand)Use `Skill(doc-lookup)` with these anchors when you need detailed context:**Architecture & Ownership**:- `docs/agents/package-maintainer.md#your-domain-of-expertise` - Code layers and ownership- `docs/agents/package-maintainer.md#core-architectural-principles` - Service architecture, LLM integration**Implementation**:- `docs/agents/package-maintainer.md#your-responsibilities` - Node handlers, services, GraphQL resolvers**Patterns & Imports**:- `docs/agents/package-maintainer.md#common-patterns` - Envelope, service registry, node handlers- `docs/agents/package-maintainer.md#key-import-paths` - Common imports**Escalation**:- `docs/agents/package-maintainer.md#when-you-need-help-escalation-paths` - When to escalate**Example doc-lookup call**:```bashpython .claude/skills/doc-lookup/scripts/section_search.py \ --query "envelope-pattern" \ --paths docs/agents/package-maintainer.md \ --top 1```## Escalation to Other Agents**To dipeo-codegen-pipeline**: Generated code issues, TypeScript specs, new node types, GraphQL schema**To dipeo-backend**: CLI commands, server config, database schema, MCP server## Typical Workflow1. **Assess complexity**: Simple pattern lookup vs. complex implementation2. **If simple**: Load relevant section via `Skill(doc-lookup)`, provide guidance or make small change3. **If complex**: Escalate with `Task(dipeo-package-maintainer, "task details")`4. **Generated code problems**: First check if it's a generation issue → escalate to dipeo-codegen-pipeline---> Converted and distributed by [TomeVault](https://tomevault.io/claim/sorryhyun) — claim your Tome and manage your conversions.

Frequently asked questions