Agent skill

Edgeone Makers Migration

by TencentEdgeOne in TencentEdgeOne/edgeone-makers-tools

Migrate existing AI agent projects (LangChain, LangGraph, OpenAI Agents SDK, Claude Agent SDK, CrewAI) to EdgeOne Makers platform conventions.

MITAuto-check passedAI & LLM Engineering

Install Edgeone Makers Migration

skills CLI
$ npx skills add TencentEdgeOne/edgeone-makers-tools --skill edgeone-makers-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TencentEdgeOne/edgeone-makers-tools edgeone-makers-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TencentEdgeOne/edgeone-makers-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/edgeone-makers-tools/references/makers-migration .claude/skills/edgeone-makers-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
edgeone-makers-migration
GitHub stars
1.9k
Used in
1 other repo
Token cost
~4.1k tokens
SKILL.md length
798 words
Files
7 (incl. references)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Migrate existing AI agent projects (LangChain, LangGraph, OpenAI Agents SDK, Claude Agent SDK, CrewAI) to EdgeOne Makers platform conventions.

  • Works in 7 steps: Replace Flask/FastAPI entry with async… → Read env from ctx.env, never os.environ → Use LLM(provider="openai",… → …
  • The user wants to adapt a standard agent project to run on EdgeOne Makers
  • SKILL.md covers Migration Decision Tree, ⚠️ Migration Checklist (common…, §1. Standard API Route →… and §2. CrewAI (Python), plus 5 more sections
  • Needs AI_GATEWAY_API_KEY and OPENAI_API_KEY

What it does

Edgeone Makers Migration is an agent skill from TencentEdgeOne/edgeone-makers-tools. Migrate existing AI agent projects (LangChain, LangGraph, OpenAI Agents SDK, Claude Agent SDK, CrewAI) to EdgeOne Makers platform conventions. Use when the user wants to adapt a standard agent project to run on EdgeOne Makers, convert Express/Next.js API routes to Makers handlers, or add platform capabilities (context.tools, context.sandbox, context.store). Do NOT trigger for new agent projects (use makers-agents instead).

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/api-route-to-makers.md`, `references/claude-agent-sdk-to-makers.md` and `references/crewai-to-makers.md`).

It sits in AI & LLM Engineering, covering Building AI agents. It works with CrewAI, Next.js, LangGraph and OpenAI Agents SDK. The licence is MIT.

When your agent uses it

  • The user wants to adapt a standard agent project to run on EdgeOne Makers
  • Convert Express/Next.js API routes to Makers handlers
  • Add platform capabilities (context.tools
  • Context.sandbox

Example prompts

  • “/edgeone-makers-migration”

Requirements

  • Python 3
  • A credential in WSA_API_KEY
  • A credential in OPENAI_API_KEY

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Replace Flask/FastAPI entry with async def handler(ctx)
  2. Read env from ctx.env, never os.environ
  3. Use LLM(provider="openai", api_key=ctx.env["AI_GATEWAY_API_KEY"], base_url=ctx.env["AI_GATEWAY_BASE_URL"])
  4. Set Crew(memory=False, verbose=False)
  5. Wrap crew.kickoff() in asyncio.to_thread()
  6. Replace custom tools with ctx.tools.to_crewai_tools(BaseTool)
  7. Return SSE via ctx.utils.stream_sse(gen())

What it can do on your machine

Read from SKILL.md and the folder at commit e6ead94. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json, typescript and python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • AI_GATEWAY_API_KEY
    • OPENAI_API_KEY
    • WSA_API_KEY
    • ANTHROPIC_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Edgeone Makers Migration loads about 4.1k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 113 tokens; SKILL.md has 798 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~113
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TencentEdgeOne/edgeone-makers-tools at commit e6ead94, republished under its MIT licence (© TencentEdgeOne). 798 words, ~4,125 tokens.

Download SKILL.mdSave it as .claude/skills/edgeone-makers-migration/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
edgeone-makers-migration
description
Migrate existing AI agent projects (LangChain, LangGraph, OpenAI Agents SDK, Claude Agent SDK, CrewAI) to EdgeOne Makers platform conventions. Use when the user wants to adapt a standard agent project to run on EdgeOne Makers, convert Express/Next.js API routes to Makers handlers, or add platform capabilities (context.tools, context.sandbox, context.store). Do NOT trigger for new agent projects (use makers-agents instead).
pathPatterns
agents/**, cloud-functions/**
metadata.author
edgeone
metadata.version
1.0.0

EdgeOne Makers Migration Guide

Migrate existing AI agent projects to the EdgeOne Makers platform format. Covers structural conversion, API adaptation, and platform capability injection.


Migration Decision Tree

What type of project are you migrating?
├── Python project
│   ├── Using CrewAI → See §2 CrewAI
│   ├── Using LangChain/LangGraph/DeepAgents → See §3 LangGraph (Python)
│   ├── Using OpenAI Agents SDK → See §4 OpenAI Agents (Python)
│   └── Using Claude Agent SDK → See §5 Claude SDK (Python)
└── Node/TS project
    ├── Using Express/Next.js API routes → See §6 Express → Makers
    ├── Using LangGraph/DeepAgents → See §3 LangGraph (Node)
    ├── Using OpenAI Agents SDK → See §4 OpenAI Agents (Node)
    └── Using Claude Agent SDK → See §5 Claude SDK (Node)

⚠️ Migration Checklist (common to all frameworks)

Before starting framework-specific changes, check these global items:

  • Create edgeone.json with correct agents.framework and buildCommand/outputDirectory
  • Move backend code from Express routes / Next.js API routes into agents/ directory
  • Replace process.env / os.environ with context.env / ctx.env
  • Replace req.headers.get('x') with context.request.headers['x'] (Node) or plain dict access (Python)
  • Replace await req.json() with context.request.body (already parsed)
  • Replace direct model API calls (OpenAI, Anthropic) with AI_GATEWAY_* env vars
  • Add SSE streaming for AI endpoints (replace res.json() / return {"data": ...})
  • Add makers-conversation-id header to frontend fetch calls
  • Wire platform tools through context.tools instead of custom tool implementations
  • Wire conversation history through context.store instead of in-memory or custom DB
  • If using web_search, set WSA_API_KEY env var and use context.tools.get("web_search")
  • Set up edgeone makers dev for local development

§1. Standard API Route → Makers Handler

This is the most common migration pattern. Applies to Express/Next.js API routes, plain HTTP handlers, etc.

Node (Express/Next.js → Makers)
typescript
// ❌ Before: Next.js API route (app/api/chat/route.ts)
export async function POST(req: Request) {
  const body = await req.json();
  const headers = req.headers;
  const apiKey = process.env.OPENAI_API_KEY;
  // ... LLM call ...
  return Response.json({ data: result });
}

// ✅ After: Makers agent handler (agents/chat/index.ts)
export async function onRequest(context: any) {
  const body = context.request.body;               // already parsed
  const conversationId = context.conversation_id;   // auto-injected from header
  const env = context.env;                          // context.env, never process.env
  // ... LLM call via AI_GATEWAY_* ...
  return new Response(JSON.stringify({ data: result }), {
    headers: { 'Content-Type': 'application/json' },
  });
}
Python (Flask/FastAPI → Makers)
python
# ❌ Before: Flask route
@app.route('/chat', methods=['POST'])
def chat():
    body = request.get_json()
    api_key = os.environ.get('OPENAI_API_KEY')
    # ... LLM call ...
    return jsonify({'data': result})

# ✅ After: Makers agent handler (agents/chat/index.py)
async def handler(ctx):
    body = ctx.request.body
    conversation_id = ctx.conversation_id
    api_key = ctx.env.get("AI_GATEWAY_API_KEY")
    # ... LLM call via AI_GATEWAY_* ...
    return {"data": result}

§2. CrewAI (Python)

Key changes
BeforeAfter
os.environ.get("OPENAI_API_KEY")ctx.env.get("AI_GATEWAY_API_KEY")
LLM(provider="openai", ...) — LiteLLM dispatchLLM(provider="openai", base_url=ctx.env["AI_GATEWAY_BASE_URL"], ...) — bypass LiteLLM
memory=True on Crewmemory=False + use ctx.store
verbose=Trueverbose=False (events go through crewai_event_bus)
crew.kickoff() (blocking)await asyncio.to_thread(crew.kickoff)
Custom search toolsUse ctx.tools.to_crewai_tools(BaseTool)
Flask/FastAPI handlerasync def handler(ctx): → ctx.utils.stream_sse(gen())
edgeone.json
json
{
  "buildCommand": "",
  "outputDirectory": "",
  "agents": {
    "framework": "crewai"
  }
}
Requirements
txt
crewai>=1.14.5
openai>=1.50.0
Migration steps
  1. Replace Flask/FastAPI entry with async def handler(ctx):
  2. Read env from ctx.env, never os.environ
  3. Use LLM(provider="openai", api_key=ctx.env["AI_GATEWAY_API_KEY"], base_url=ctx.env["AI_GATEWAY_BASE_URL"])
  4. Set Crew(memory=False, verbose=False)
  5. Wrap crew.kickoff() in asyncio.to_thread()
  6. Replace custom tools with ctx.tools.to_crewai_tools(BaseTool)
  7. Return SSE via ctx.utils.stream_sse(gen())

See makers-agents/references/python-frameworks/crewai.md for the complete pattern. Detailed before/after: references/crewai-to-makers.md


§3. LangGraph / DeepAgents (Node + Python)

Key changes
BeforeAfter
Direct model creation (new ChatOpenAI(...))Use AI_GATEWAY_* for apiKey/baseURL
MemorySaver (in-memory checkpointer)context.store.langgraphCheckpointer (persistent)
Custom tool functionscontext.tools.toLangChainTools(tool)
agent.stream()SSE via createSSEResponse(gen, signal) (Node) or ctx.utils.stream_sse(gen()) (Python)
thread_id manual managementthread_id = context.conversation_id
Node — edgeone.json
json
{
  "agents": {
    "framework": "langgraph"
  }
}
Python — edgeone.json
json
{
  "buildCommand": "",
  "outputDirectory": "",
  "agents": {
    "framework": "langgraph"
  }
}
Migration steps
  1. Move handler into agents/<name>/index.ts (or .py)
  2. Replace model initialization: use AI_GATEWAY_API_KEY + AI_GATEWAY_BASE_URL
  3. Replace checkpointer: context.store.langgraphCheckpointer instead of MemorySaver
  4. Replace store: context.store.langgraphStore
  5. Replace tools: context.tools.toLangChainTools(tool) instead of custom tool functions
  6. Set thread_id: { configurable: { thread_id: context.conversation_id } }
  7. Replace response with SSE streaming pattern

Node: makers-agents/references/node-frameworks/langgraph.md Python: makers-agents/references/python-frameworks/langgraph.md DeepAgents: makers-agents/references/node-frameworks/deepagents.md Detailed before/after: references/langgraph-to-makers.md, references/deepagents-to-makers.md


§4. OpenAI Agents SDK (Node + Python)

Key changes
BeforeAfter
new OpenAI({ apiKey, baseURL })Read AI_GATEWAY_* from context.env / ctx.env
Runner.run(agent, input, { tools })Tools from context.tools.all() (already OpenAI function format)
Session managementcontext.store.openaiSession(convId) (Node)
Express route responseSSE via createSSEResponse(gen, signal) (Node) or ctx.utils.stream_sse(gen()) (Python)
Model name hardcoded`ctx.env.AI_GATEWAY_MODEL
Node — edgeone.json
json
{
  "agents": {
    "framework": "openai-agents-sdk"
  }
}
Python — edgeone.json
json
{
  "buildCommand": "",
  "outputDirectory": "",
  "agents": {
    "framework": "openai-agents-sdk"
  }
}
Migration steps
  1. Move handler into agents/<name>/index.ts (or .py)
  2. Create OpenAI client from context.env (not process.env)
  3. Replace tools with context.tools.all() (returns OpenAI function tools)
  4. Use context.store.openaiSession(conversationId) for session (Node)
  5. Map stream events to SSE: output_text_delta → ai_response, tool_called → tool_call

Node: makers-agents/references/node-frameworks/openai-agents.md Python: makers-agents/references/python-frameworks/openai-agents.md Detailed before/after: references/openai-agents-to-makers.md


Show full SKILL.md (318 more words)Show less

§5. Claude Agent SDK (Node + Python)

Key changes
BeforeAfter
ANTHROPIC_API_KEY env varMapped from AI_GATEWAY_* via collectGatewayEnv()
process.envcontext.env injected into query().options.env
Custom MCP toolscontext.tools.toClaudeMcpServer()
Sessioncontext.store.claudeSessionStore() (Node)
Stdout EPIPE crashSwallow EPIPE on process.stdout (Node)
No writable config dirSet CLAUDE_CONFIG_DIR=/tmp/claude-agent-sdk, CLAUDE_CODE_TMPDIR=/tmp
Node — edgeone.json
json
{
  "agents": {
    "framework": "claude-agent-sdk"
  }
}
Python — edgeone.json
json
{
  "buildCommand": "",
  "outputDirectory": "",
  "agents": {
    "framework": "claude-agent-sdk"
  }
}
Migration steps
  1. Move handler into agents/<name>/index.ts (or .py)
  2. Map AI_GATEWAY_* → ANTHROPIC_* via collectGatewayEnv(context.env)
  3. Inject env into query({ options: { env: collectGatewayEnv(...) } })
  4. Replace MCP tools: context.tools.toClaudeMcpServer('edgeone', { alwaysLoad: true })
  5. Node only: swallow EPIPE on process.stdout
  6. Set writable config dirs: CLAUDE_CONFIG_DIR=/tmp/claude-agent-sdk, CLAUDE_CODE_TMPDIR=/tmp

Node: makers-agents/references/node-frameworks/claude-sdk.md Python: makers-agents/references/python-frameworks/claude-sdk.md Detailed before/after: references/claude-agent-sdk-to-makers.md


§6. Express / Next.js API Routes (Node)

General migration for any Express-based or Next.js API route agent.

The 7-step conversion
StepBeforeAfter
1. File locationapp/api/chat/route.ts or server/routes/chat.tsagents/chat/index.ts
2. Entry signatureexport async function POST(req) or app.post('/chat', handler)export async function onRequest(context)
3. Body parsingawait req.json()context.request.body (already parsed)
4. Headersreq.headers.get('x-foo')context.request.headers['x-foo']
5. Abort signalreq.signalcontext.request.signal (AbortSignal)
6. Model accessprocess.env.OPENAI_API_KEY → direct callcontext.env.AI_GATEWAY_* → AI Gateway
7. Responseres.json() or return Response.json()SSE stream via createSSEResponse(gen, signal)
Example: Next.js API route → Makers
typescript
// ❌ Before: Next.js (app/api/chat/route.ts)
import { NextRequest } from 'next/server';
import OpenAI from 'openai';

export async function POST(req: NextRequest) {
  const { message } = await req.json();
  const client = new OpenAI({ apiKey: process.env.OPENAI_API_KEY });
  const response = await client.chat.completions.create({
    model: 'gpt-4o',
    messages: [{ role: 'user', content: message }],
    stream: true,
  });
  // ... stream back as Response
}

// ✅ After: EdgeOne Makers (agents/chat/index.ts)
import { createLogger, sseEvent, createSSEResponse } from '../_shared';

export async function onRequest(context: any) {
  const { message } = context.request.body ?? {};
  if (!message) return new Response('Missing message', { status: 400 });

  const signal = context.request.signal as AbortSignal;

  return createSSEResponse(async function* (sig) {
    const response = await fetch(context.env.AI_GATEWAY_BASE_URL + '/v1/chat/completions', {
      method: 'POST',
      headers: {
        'Content-Type': 'application/json',
        'Authorization': `Bearer ${context.env.AI_GATEWAY_API_KEY}`,
      },
      body: JSON.stringify({
        model: context.env.AI_GATEWAY_MODEL || '@makers/deepseek-v4-flash',
        messages: [{ role: 'user', content: message }],
        stream: true,
      }),
      signal: sig,
    });
    // ... proxy SSE chunks ...
    yield 'data: [DONE]\n\n';
  }, signal);
}

§7. Client-Side Migration

Frontend fetch calls
typescript
// ❌ Before: plain fetch without conversation-id
const response = await fetch('/api/chat', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ message }),
});

// ✅ After: with makers-conversation-id header
const conversationId = getOrCreateConversationId(); // crypto.randomUUID() + localStorage
const response = await fetch('/chat', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'makers-conversation-id': conversationId,  // ⭐ required for all AI endpoints
  },
  body: JSON.stringify({ message }),
});
/stop endpoint
typescript
// ✅ Always pass conversation_id in body for /stop
await fetch('/stop', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ conversation_id: conversationId }),
});
SSE parsing
typescript
const reader = response.body!.getReader();
const decoder = new TextDecoder();
let buffer = '';

while (true) {
  const { done, value } = await reader.read();
  if (done) break;
  buffer += decoder.decode(value, { stream: true });

  const lines = buffer.split('\n\n');
  buffer = lines.pop() || '';
  for (const line of lines) {
    if (line.startsWith('data: ')) {
      const data = line.slice(6);
      if (data === '[DONE]') return;
      try {
        const event = JSON.parse(data);
        if (event.type === 'ai_response') { /* display text */ }
        if (event.type === 'tool_call') { /* show tool call */ }
        if (event.type === 'ping') { /* ignore heartbeat */ }
      } catch { /* skip non-JSON */ }
    }
  }
}

§8. Post-Migration Verification

After migration, verify these items before deploying:

  • edgeone makers dev starts without errors
  • /chat endpoint returns SSE stream (not JSON)
  • AI responses work end-to-end (frontend → agent → model → frontend)
  • context.env is used everywhere (grep for process.env / os.environ — none should remain)
  • edgeone.json has correct agents.framework
  • Platform tools (context.tools) work in at least one framework
  • Conversation history persists across requests (via context.store)
  • /stop endpoint cancels active runs
  • Frontend sends makers-conversation-id header

See Also

Detailed before/after reference files

© TencentEdgeOne, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in skills/edgeone-makers-tools/references/makers-migration of TencentEdgeOne/edgeone-makers-tools.

  • SKILL.md
  • references/api-route-to-makers.md
  • references/claude-agent-sdk-to-makers.md
  • references/crewai-to-makers.md
  • references/deepagents-to-makers.md
  • references/langgraph-to-makers.md
  • references/openai-agents-to-makers.md

Open the folder on GitHubat commit e6ead94

Used in 1 other repository

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in TencentEdgeOne/edgeone-makers-tools, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Edgeone Makers Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Edgeone Makers Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Edgeone Makers Migration this skillTencentEdgeOne/edgeone-makers-tools1.9k1 repos~4.1kAutomated safety check: PassMIT
Mem0 Platform SDKmem0ai/mem067k1 repos~2.2kAutomated safety check: PassApache-2.0
Omnigent Framework Detectionomnigent-ai/omnigent11k—~610Automated safety check: PassApache-2.0
AI Agents Architectomer-metin/skills-for-antigravity163—~558Automated safety check: PassApache-2.0
Agentsop Framework Selectionagentsope/SkillAlchemy436—~5.8kAutomated safety check: PassMIT
Agentsop Prompt History Inspectagentsope/SkillAlchemy436—~8.4kAutomated safety check: PassMIT

Similar skills

  • Adds persistent memory to AI apps with the Mem0 Python and TypeScript SDKs: store, search, update and delete user memories, with framework integrations.

    67k GitHub starsUsed in 1 repo~2.2k tokens
    AI & LLM EngineeringAuto-check passed
  • Omnigent Framework Detection

    omnigent-ai/omnigent

    Scans Python agent code for framework imports and recommends the matching Omnigent executor type, or says when the framework is not natively supported yet.

    11k GitHub stars~610 tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • AI Agents Architect

    omer-metin/skills-for-antigravity

    Expert in designing and building autonomous AI agents. An agent skill from omer-metin/skills-for-antigravity.

    163 GitHub stars~558 tokensUpdated 8 mo ago
    AI & LLM EngineeringAuto-check passed
  • Agentsop Framework Selection

    agentsope/SkillAlchemy

    Neutral, framework-agnostic decision tree for project kickoff: "which agent / RAG / LLM framework should I reach for?" Synthesizes the ecosystem sections of 7 landmark-project SOPs (LangGraph…

    436 GitHub stars~5.8k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Agentsop Prompt History Inspect

    agentsope/SkillAlchemy

    Tool skill — the first move in any LM-debugging session: dump the actual rendered prompt the framework sent to the model, before changing anything else.

    436 GitHub stars~8.4k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Cloudbase Agent

    TencentCloudBase/CloudBase-AI-Toolkit

    Build and deploy AI agents with CloudBase Agent SDK (TypeScript & Python).

    1.1k GitHub starsUsed in 2 repos~479 tokens
    AI & LLM EngineeringAuto-check passed

More from TencentEdgeOne/edgeone-makers-tools

All 12 skills in this repo
  • Edgeone Makers Agents

    TencentEdgeOne/edgeone-makers-tools

    This skill guides building AI agent endpoints on EdgeOne Makers — five framework routes (DeepAgents, LangGraph, CrewAI, OpenAI Agents SDK, Claude Agent SDK), platform-injected context.store /…

    1.9k GitHub starsUsed in 1 repo~5.8k tokens
    Auto-check: notes
  • Edgeone Makers CLI

    TencentEdgeOne/edgeone-makers-tools

    EdgeOne Makers CLI command reference. An agent skill from TencentEdgeOne/edgeone-makers-tools.

    1.9k GitHub starsUsed in 1 repo~739 tokens
    Auto-check: notes
  • Edgeone Makers Env Adaption

    TencentEdgeOne/edgeone-makers-tools

    Environment-specific adaptation rules for EdgeOne Makers Skills running in sandboxed or restricted AI coding environments (e.g.

    1.9k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Edgeone Makers Recipes

    TencentEdgeOne/edgeone-makers-tools

    Project structure templates and scaffolding recipes for typical EdgeOne Makers applications — full-stack apps, static sites, API services, and AI agent projects.

    1.9k GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check passed
  • Edgeone Makers Storage

    TencentEdgeOne/edgeone-makers-tools

    KV and Blob storage services on EdgeOne Makers. An agent skill from TencentEdgeOne/edgeone-makers-tools.

    1.9k GitHub starsUsed in 1 repo~930 tokens
    Auto-check passed
  • Edgeone Makers Edge Functions

    TencentEdgeOne/edgeone-makers-tools

    V8-based lightweight edge functions on EdgeOne Makers. An agent skill from TencentEdgeOne/edgeone-makers-tools.

    1.9k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed

Questions about Edgeone Makers Migration

What does Edgeone Makers Migration do?

Migrate existing AI agent projects (LangChain, LangGraph, OpenAI Agents SDK, Claude Agent SDK, CrewAI) to EdgeOne Makers platform conventions. Edgeone Makers Migration is an agent skill from TencentEdgeOne/edgeone-makers-tools. Migrate existing AI agent projects (LangChain, LangGraph, OpenAI Agents SDK, Claude Agent SDK, CrewAI) to EdgeOne Makers platform conventions.

When should I use Edgeone Makers Migration?

Edgeone Makers Migration fits situations like: the user wants to adapt a standard agent project to run on EdgeOne Makers; convert Express/Next.js API routes to Makers handlers; add platform capabilities (context.tools; context.sandbox.

How do I install Edgeone Makers Migration in Claude Code?

Run `npx skills add TencentEdgeOne/edgeone-makers-tools --skill edgeone-makers-migration -a claude-code`. Or copy the skill folder (skills/edgeone-makers-tools/references/makers-migration in TencentEdgeOne/edgeone-makers-tools) into .claude/skills/edgeone-makers-migration in your project. Claude Code loads it when a task matches its description.

How do I install Edgeone Makers Migration in Codex?

Run `npx skills add TencentEdgeOne/edgeone-makers-tools --skill edgeone-makers-migration -a codex`. Or copy the skill folder (skills/edgeone-makers-tools/references/makers-migration in TencentEdgeOne/edgeone-makers-tools) into .agents/skills/edgeone-makers-migration in your project. Codex loads it when a task matches its description.

Can I use Edgeone Makers Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TencentEdgeOne/edgeone-makers-tools --skill edgeone-makers-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/edgeone-makers-migration, .gemini/skills/edgeone-makers-migration, .github/skills/edgeone-makers-migration and .opencode/skills/edgeone-makers-migration in your project.

What does Edgeone Makers Migration need to run?

Going by SKILL.md and its folder, Edgeone Makers Migration needs credentials named AI_GATEWAY_API_KEY, OPENAI_API_KEY, WSA_API_KEY and ANTHROPIC_API_KEY. Our summary lists: Python 3; A credential in WSA_API_KEY; A credential in OPENAI_API_KEY.

Does Edgeone Makers Migration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Edgeone Makers Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Edgeone Makers Migration use?

Edgeone Makers Migration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Edgeone Makers Migration use?

About 4.1k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.5k tokens, read only when the agent opens those files.

What are the alternatives to Edgeone Makers Migration?

Skills that share tags, products or a category with Edgeone Makers Migration: Mem0 Platform SDK (mem0ai/mem0, 67k stars), Omnigent Framework Detection (omnigent-ai/omnigent, 11k stars), AI Agents Architect (omer-metin/skills-for-antigravity, 163 stars) and Agentsop Framework Selection (agentsope/SkillAlchemy, 436 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Edgeone Makers Migration?

TencentEdgeOne (a GitHub organization) maintains it in TencentEdgeOne/edgeone-makers-tools, which has 1,861 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 8, 2026.

Source: TencentEdgeOne/edgeone-makers-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.