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.
Best use case
dipeo-package-maintainer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using dipeo-package-maintainer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/dipeo-package-maintainer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How dipeo-package-maintainer Compares
| Feature / Agent | dipeo-package-maintainer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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**: ```bash 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 1. **Assess complexity**: Simple pattern lookup vs. complex implementation 2. **If simple**: Load relevant section via `Skill(doc-lookup)`, provide guidance or make small change 3. **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
Related Skills
dipeo-frontend-dev
Router skill for DiPeO frontend (React, visual editor, GraphQL integration, TypeScript types). Use when task mentions React components, diagram editor, GraphQL hooks, or type errors. For simple tasks, handle directly; for complex work, escalate to dipeo-frontend-dev agent.
dipeo-codegen-pipeline
Router skill for DiPeO code generation pipeline (TypeScript specs → IR → Python/GraphQL). Use when task mentions TypeScript models, IR builders, generated code diagnosis, or codegen workflow. For simple tasks, handle directly; for complex work, escalate to dipeo-codegen-pipeline agent.
dipeo-backend
Router skill for DiPeO backend ecosystem (server/ and cli/): FastAPI server, CLI tools, database, MCP integration. Use when task mentions CLI commands, server endpoints, database queries, or MCP tools. For simple tasks, handle directly; for complex work, escalate to dipeo-backend agent.
todo-manage
Manage and organize TODO.md at project root - plan features, track progress, mark tasks complete, and clean up completed items. Use when planning tasks, organizing work, reviewing priorities, or managing the project TODO list. Access via /dipeotodos command.
test-backend-router
Test implementation of thin router skill for DiPeO backend. Provides decision criteria and documentation anchors for FastAPI server, CLI (dipeo run/results/metrics/compile/export), SQLite schema, and MCP integration in apps/server/. Use when task mentions CLI commands, server endpoints, database queries, or MCP tools.
separate-monolithic-python
Break large Python files (>500 LOC) into smaller, well-organized modules with proper package structure. Use when a Python file is too large, monolithic, or needs refactoring. Triggered by requests mentioning "too large", "separate", "split", "break up", or "refactor" for Python files.
maintain-docs
Update and maintain documentation to reflect current implementation after code changes, refactoring, or new features. Remove temporal language, verify accuracy against code, and keep docs current. Use when updating docs, syncing documentation, removing outdated info, or after implementing features.
import-refactor
Update all import statements, module references, string paths, and config references after moving or renaming files and modules. Handles Python, TypeScript, and JavaScript imports. Use when moving files, renaming modules, restructuring directories, or consolidating code.
skill-generator
Create new Claude Code skills with proper structure and best practices. Use when the user wants to create a new skill, extend Claude's capabilities, or needs help structuring a SKILL.md file.
doc-lookup
Locate and retrieve specific documentation sections from DiPeO's docs/ by heading anchors or keywords. Returns minimal, targeted excerpts instead of full files. Use when you need precise documentation context without loading entire guides.
clean-comments
Remove unnecessary, redundant, or obvious code comments while preserving valuable explanations. Use when cleaning up comments, removing verbose documentation, simplifying inline comments, or preparing code for review.
detecting-typosquatting-packages-in-npm-pypi
Detects typosquatting attacks in npm and PyPI package registries by analyzing package name similarity using Levenshtein distance and other string metrics, examining publish date heuristics to identify recently created packages mimicking established ones, and flagging download count anomalies where suspicious packages have disproportionately low usage compared to their legitimate targets. The analyst queries the PyPI JSON API and npm registry API to gather package metadata for automated comparison. Activates for requests involving package typosquatting detection, dependency confusion analysis, malicious package identification, or software supply chain threat hunting in package registries.