Loading...
Loading...
Found 9 Skills
Agent Workspace Migration. Organize any project into a long-term maintainable Agent workspace with consistent support for both Claude Code and Codex: audit rule files, identify source-of-truth skills, standardize naming conventions, and generate bridges. Triggers: /dbs-agent-migration, /agent-migration, "migrate to Codex", "migrate to Claude Code", "unify AGENTS.md", "organize skill bridges", "my Agent workspace is messy", "help me unify Claude and Codex" Agent workspace migration. Turn any project into a maintainable Claude Code / Codex dual-host workspace by auditing rule files, establishing source-of-truth skills, normalizing names, and generating bridges. Trigger: /dbs-agent-migration, /agent-migration, "migrate to Codex", "migrate to Claude Code", "fix AGENTS.md", "organize skill bridges"
Agent skill for migration-plan - invoke with $agent-migration-plan
Migrate an MLflow ResponsesAgent from Databricks Model Serving to Databricks Apps. Use when: (1) User wants to migrate from Model Serving to Apps, (2) User has a ResponsesAgent with predict()/predict_stream() methods, (3) User wants to convert to @invoke/@stream decorators.
Export agent data into a Starchild migration bundle. For use by ANY agent (OpenClaw, Claude Code, Cursor, etc.) to migrate into Starchild.
Complex migration strategies for LangChain applications. Use when migrating from legacy LLM frameworks, refactoring large codebases, or implementing phased migration approaches. Trigger with phrases like "langchain migration strategy", "migrate to langchain", "langchain refactor", "legacy LLM migration", "langchain transition".
Import a migration bundle into Starchild. Downloads from relay, validates, and loads all components using native tools.
Migrate a Java application from the classic Elastic APM Java agent to the EDOT Java agent. Use when switching from elastic-apm-agent.jar to elastic-otel-javaagent.jar.
Import ElevenLabs conversational AI agents into Telnyx. Preserves instructions, voice settings, tools, and call analysis. Supports all SDK languages.
Use when adding capabilities to an existing agent project — memory, app integration, VPC, multi-agent, migration, model changes, browser, code interpreter, or resource removal. Triggers on: "add memory", "remember across sessions", "call agent from app", "invoke agent from code", "auth to call agent", "streaming responses", "VPC", "VPC connectivity", "VPC error", "can't reach from VPC", "multi-agent", "A2A", "A2A auth", "orchestrator not delegating", "specialist not called", "migrate Bedrock Agent", "after import", "migration issue", "framework for migration", "change model", "browser tool", "code interpreter", "delete agent", "tear down", "agentcore remove", "cross-account memory", "resource-based policy on memory". Not for connecting to external APIs via Gateway — use agents-connect. Not for scaffolding a new project — use agents-get-started. Not for CLI/dev server errors — use agents-debug. Strands vs LangGraph in a migration context routes here.