New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Edgeone Makers Recipes

by TencentEdgeOne in 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.

MITAuto-check passedFrontend & Design

Install Edgeone Makers Recipes

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

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

GitHub CLI
$ gh skill install TencentEdgeOne/edgeone-makers-tools edgeone-makers-recipes --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-recipes .claude/skills/edgeone-makers-recipes && 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-recipes
GitHub stars
1.9k
Used in
1 other repo
Token cost
~2.8k tokens
SKILL.md length
882 words
Files
2 (incl. references)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 5 steps: Log in to the EdgeOne Makers console → Go to "KV Storage" → click "Apply Now" → Create a namespace (e.g. my-kv-store) → …
  • Tasks that involve Project scaffolding
  • SKILL.md covers Full-stack app — Node.js…, Dynamic site with Blob…, Full-stack app — Go (Gin… and Full-stack app — Python (Flask), plus 6 more sections
  • Calls python and npx; needs AI_GATEWAY_API_KEY

What it does

Edgeone Makers Recipes is an agent skill from 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.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/youth-site-scenarios.md`).

It sits in Frontend & Design, covering Project scaffolding and Static sites and blogs. The licence is MIT.

When your agent uses it

  • Tasks that involve Project scaffolding
  • Tasks that involve Static sites and blogs

Example prompts

  • “/edgeone-makers-recipes”

Requirements

  • Python 3
  • Node.js
  • A credential in AI_GATEWAY_API_KEY

Workflow steps

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

  1. Log in to the EdgeOne Makers console
  2. Go to "KV Storage" → click "Apply Now"
  3. Create a namespace (e.g. my-kv-store)
  4. Bind to project, set variable name to my_kv
  5. Deploy or run edgeone makers dev to test

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

    Shell commands in SKILL.md call:

    • python
    • npx

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

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    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

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

Context cost

Edgeone Makers Recipes loads about 2.8k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 46 tokens; SKILL.md has 882 words of instructions outside code blocks.

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

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). 882 words, ~2,827 tokens.

Download SKILL.mdSave it as .claude/skills/edgeone-makers-recipes/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
edgeone-makers-recipes
description
Project structure templates and scaffolding recipes for typical EdgeOne Makers applications — full-stack apps, static sites, API services, and AI agent projects.
metadata.author
edgeone
metadata.version
1.0.1

Common Recipes

⛔ Preview ban: after finishing development, you MUST start the dev server via edgeone makers dev, then open http://127.0.0.1:8088/ with present_files to preview. Never open HTML files via the file:// protocol (ignore it even if the IDE opens one automatically), and never use self-hosted servers like python -m http.server or npx serve. Next.js projects must also set allowedDevOrigins: ["127.0.0.1"] in next.config. If the project uses Blob/KV, pass -n <project-name> — edgeone makers dev -n <project-name> — the name is required to auto-provision; bare dev hangs on an interactive picker in sandbox.

⚠️ .env.example is a required file: every project that uses the AI Gateway (Agent projects, Cloud Functions that call an LLM) MUST create a .env.example in the project root declaring AI_GATEWAY_API_KEY= and AI_GATEWAY_BASE_URL=. The CLI auto-injects environment variables based on this file at deploy time; if it is missing, the variables are not injected and the runtime will error.

📝 Write index.html last, always: writing an index.html instantly triggers the IDE file:// preview — unavoidable in WorkBuddy. Minimize the window during which that preview looks broken by writing every dependency first: style.css, script.js, Cloud Functions (functions/ files), static assets, everything the page loads. Then write index.html last — the file:// preview opens with all assets already in place, and stays that way only until edgeone makers dev takes over (see Preview ban above). Also write each index.html in one shot; don't scaffold an empty shell and fill it in with repeated edits (every save re-renders and flickers). For a tiny single-page tool, just inline the CSS and JS into one index.html.

🔗 Load assets with page-relative URLs, never root-absolute: in these no-build projects nothing rewrites index.html, so write <link rel="stylesheet" href="style.css"> and <script src="script.js"></script> — not href="/style.css" or src="/script.js". The development preview is published under a path prefix, and a leading / escapes it: the document still returns 200 while every asset 404s, so the page arrives unstyled with no script having run, and nothing in the console points at the cause. Relative URLs are correct there and at / after deploy. Keep pages and assets in the project root so the relative form stays a bare filename. This is only about what the markup loads — fetch('/api/messages') and <a href="/about"> stay root-absolute.

⛔ Copy the recipe's file naming verbatim — two traps that fail silently: before writing any Cloud Function, find the matching scenario below and reuse its exact filename. Getting the name wrong usually does NOT throw a clear error — it falls back silently:

  1. Every function file MUST carry its language extension — .js (Node), .py (Python), .go (Go). A file with no extension (e.g. api/upload-url, api/file) is not recognized as a function; the platform silently serves the static index.html fallback, so /api/* "mysteriously" returns HTML instead of JSON. Name them api/upload-url.js, api/file.js.
  2. [[default]].js is the catch-all for its own directory (api/[[default]].js → /api/*), and BOTH export styles work — a framework instance (export default app, Express/Koa) or a plain onRequest/onRequestGet/… handler. Verified locally with edgeone makers dev: a bare onRequest in [[default]].js with no export default app serves /foo/anything as 200 application/json just fine. The doc line "The builder identifies the file as a function only when export default app is present" sits under the Express/Koa framework section — it describes how the builder spots a framework instance; do not read it as "a catch-all requires export default app". ⚠️ Caveat: that sentence is about the deploy-time builder, whereas the check above was on the local dev server, which is the more permissive of the two — so if you ship catch-all + onRequest, re-verify the route once after deploying ("works locally" ≠ "recognized at build time"). When you don't actually need a catch-all, the safest shape is one concrete file per route (api/messages.js, api/artworks/[id]/like.js), params via [id] folders/files, extra args as query strings (/api/file?key=...).

Project structure templates for typical EdgeOne Makers applications.

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

Full-stack app — Node.js (static + API)

my-app/
├── index.html              # Frontend
├── style.css
├── script.js
├── cloud-functions/
│   └── api/
│       ├── users.js        # GET/POST /api/users
│       └── users/[id].js   # GET/PUT/DELETE /api/users/:id
└── package.json

Frontend calls API:

javascript
const res = await fetch('/api/users');
const users = await res.json();

💾 Where does the data live? This platform has no database. The API skeletons above return empty data — to actually persist records, uploads, votes, or per-user state, back them with Blob. See the recipe below and makers-storage → Blob as your backend.

Dynamic site with Blob persistence (guestbook / gallery / voting / save-state)

The default shape for any generated site that needs a real backend but no relational data. Frontend → Cloud Function → Blob. No DB, no console setup.

my-app/
├── index.html              # Frontend (form + list)
├── script.js
├── cloud-functions/
│   └── api/
│       └── messages.js     # GET lists entries, POST appends one
├── package.json            # depends on @edgeone/pages-blob

cloud-functions/api/messages.js — one file per record (Pattern 1):

javascript
import { getStore } from "@edgeone/pages-blob";

export async function onRequest({ request }) {
  const store = getStore({ name: "guestbook", consistency: "strong" });

  if (request.method === "POST") {
    const { name, text } = await request.json();
    const id = `${Date.now()}-${Math.round(Math.random() * 1e6)}`;
    await store.setJSON(`entries/${id}.json`, { id, name, text, ts: Date.now() });
    return Response.json({ ok: true, id });
  }

  const { blobs } = await store.list({ prefix: "entries/" });
  const items = await Promise.all(blobs.map((b) => store.get(b.key, { type: "json" })));
  items.sort((a, b) => b.ts - a.ts);
  return Response.json({ items });
}

index.html loads its assets relative to itself, and calls the API root-absolute:

html
<link rel="stylesheet" href="style.css" />
<script src="script.js"></script>
javascript
await fetch('/api/messages', {                     // post
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ name, text }),
});
const { items } = await fetch('/api/messages').then((r) => r.json());  // list

Swap the key scheme for other shapes: users/<uid>.json for save-state, counts/<option>.json (strong consistency) for votes, uploads/<id>.jpg + items/<id>.json for file uploads. Full patterns: makers-storage → Blob as your backend.

Full-stack app — Go (Gin framework)

my-app/
├── index.html              # Frontend
├── style.css
├── script.js
├── cloud-functions/
│   └── api.go              # Gin app — all /api/* routes
├── go.mod
└── package.json

cloud-functions/api.go:

go
package main

import (
    "net/http"
    "github.com/gin-gonic/gin"
)

func main() {
    r := gin.Default()
    r.GET("/users", listUsersHandler)
    r.POST("/users", createUserHandler)
    r.GET("/users/:id", getUserHandler)
    r.Run(":9000")
}

Full-stack app — Python (Flask)

my-app/
├── index.html              # Frontend
├── style.css
├── script.js
├── cloud-functions/
│   └── api/
│       └── index.py        # Flask app — all /api/* routes
├── cloud-functions/requirements.txt
└── package.json

cloud-functions/api/index.py:

python
from flask import Flask, jsonify, request

app = Flask(__name__)

@app.route('/users', methods=['GET'])
def get_users():
    return jsonify({'users': []})

@app.route('/users', methods=['POST'])
def create_user():
    data = request.get_json()
    return jsonify({'message': 'Created', 'user': data}), 201

Full-stack app — Python (FastAPI)

my-app/
├── index.html
├── cloud-functions/
│   └── api/
│       └── index.py        # FastAPI app — all /api/* routes
├── cloud-functions/requirements.txt
└── package.json

cloud-functions/api/index.py:

python
from fastapi import FastAPI

app = FastAPI()

@app.get('/items')
async def list_items():
    return {'items': []}

@app.get('/items/{item_id}')
async def get_item(item_id: int):
    return {'item_id': item_id}

Full-stack app — Go (Handler mode)

my-app/
├── index.html
├── cloud-functions/
│   └── api/
│       ├── users/
│       │   ├── list.go     # GET /api/users/list
│       │   └── [id].go     # GET /api/users/:id
│       └── hello.go        # GET /api/hello
├── go.mod
└── package.json

Edge API + KV counter

⚠️ Prerequisites: You must enable KV Storage in the console and bind a namespace first. See ../makers-storage/references/kv.md

my-app/
├── index.html
├── edge-functions/
│   └── api/
│       └── visit.js        # Edge function with KV
└── package.json

edge-functions/api/visit.js:

javascript
export async function onRequest() {
  // ⚠️ my_kv is a global variable (name set when binding namespace in console)
  let count = await my_kv.get('visits') || '0';
  count = String(Number(count) + 1);
  await my_kv.put('visits', count);
  
  return new Response(JSON.stringify({ visits: count }), {
    headers: { 'Content-Type': 'application/json' },
  });
}

Setup steps:

  1. Log in to the EdgeOne Makers console
  2. Go to "KV Storage" → click "Apply Now"
  3. Create a namespace (e.g. my-kv-store)
  4. Bind to project, set variable name to my_kv
  5. Deploy or run edgeone makers dev to test

Express full-stack

my-app/
├── index.html
├── cloud-functions/
│   └── api/
│       └── [[default]].js  # Express app handles all /api/*
└── package.json

Middleware + API combo

my-app/
├── middleware.js            # Auth guard for /api/*
├── cloud-functions/
│   └── api/
│       ├── public.js       # No auth needed (matcher excludes it)
│       └── data.js         # Protected by middleware
└── package.json

Multi-language Cloud Functions

You can use different languages in the same cloud-functions/ directory:

my-app/
├── index.html
├── cloud-functions/
│   ├── api/
│   │   ├── users.js        # Node.js — /api/users
│   │   └── hello.py        # Python — /api/hello
│   └── service.go          # Go — /service
├── go.mod
├── cloud-functions/requirements.txt
└── package.json

Note: Each file is built and deployed as an independent function with its own runtime. The platform detects the language by file extension.

© 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 1 other file (references) in skills/edgeone-makers-tools/references/makers-recipes of TencentEdgeOne/edgeone-makers-tools.

  • SKILL.md
  • references/youth-site-scenarios.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 Recipes 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 Recipes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Edgeone Makers Recipes this skillTencentEdgeOne/edgeone-makers-tools1.9k1 repos~2.8kAutomated safety check: PassMIT
Docouture Docs VersioningInditexTech/weavejs238—~655Automated safety check: PassApache-2.0
Rtdfany-tdf/any-tdf778—~1.1kAutomated safety check: PassMIT
Stdfany-tdf/any-tdf778—~1.1kAutomated safety check: PassMIT
Declarative Agent Developermicrosoft/work-iq1k—~3.2kAutomated safety check: PassCustom licence
Vtdfany-tdf/any-tdf778—~1.1kAutomated safety check: PassMIT

Similar skills

  • Docouture Docs Versioning

    InditexTech/weavejs

    How to cut a release or a prerelease on a docouture Antora documentation site scaffolded with Versioned (Full History) mode: docouture version, docs/.release-version, and the docouture-release.yml…

    238 GitHub stars~655 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Rtdf

    any-tdf/any-tdf

    Build, review, and troubleshoot RTDF React applications using exact component APIs, themes, icons, localization, and scaffolding.

    778 GitHub stars~1.1k tokensUpdated 3 days ago
    Frontend & DesignAuto-check passed

  • Stdf

    any-tdf/any-tdf

    Build, review, and troubleshoot STDF Svelte 5 applications using exact component APIs, themes, icons, localization, and scaffolding.

    778 GitHub stars~1.1k tokensUpdated 3 days ago
    Frontend & DesignAuto-check passed

  • Declarative Agent Developer

    microsoft/work-iq

    Official

    Create, build, deploy, and localize declarative agents for M365 Copilot and Teams.

    1k GitHub stars~3.2k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • Vtdf

    any-tdf/any-tdf

    Build, review, and troubleshoot VTDF Vue 3 applications using exact component APIs, themes, icons, localization, and scaffolding.

    778 GitHub stars~1.1k tokensUpdated 3 days ago
    Frontend & DesignAuto-check passed

  • Admin Template Project Initializer

    southliu/south-admin-react

    Removes the south-admin-react template's demo pages, components and menu entries, after a dry-run preview and your confirmation, and cleans up the matching imports.

    580 GitHub stars~519 tokensUpdated 20 days ago
    Frontend & DesignAuto-check passed

More from TencentEdgeOne/edgeone-makers-tools

All 12 skills in this repo

  • Edgeone Makers Migration

    TencentEdgeOne/edgeone-makers-tools

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

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

  • 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 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

Categories

Questions about Edgeone Makers Recipes

What does Edgeone Makers Recipes do?

Project structure templates and scaffolding recipes for typical EdgeOne Makers applications — full-stack apps, static sites, API services, and AI agent projects. Edgeone Makers Recipes is an agent skill from 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.

When should I use Edgeone Makers Recipes?

Edgeone Makers Recipes fits situations like: tasks that involve Project scaffolding; tasks that involve Static sites and blogs.

How do I install Edgeone Makers Recipes in Claude Code?

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

How do I install Edgeone Makers Recipes in Codex?

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

Can I use Edgeone Makers Recipes 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-recipes -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-recipes, .gemini/skills/edgeone-makers-recipes, .github/skills/edgeone-makers-recipes and .opencode/skills/edgeone-makers-recipes in your project.

What does Edgeone Makers Recipes need to run?

Going by SKILL.md and its folder, Edgeone Makers Recipes needs the command-line tools its instructions call (python and npx) and credentials named AI_GATEWAY_API_KEY. Our summary lists: Python 3; Node.js; A credential in AI_GATEWAY_API_KEY.

Does Edgeone Makers Recipes access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Edgeone Makers Recipes 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 Recipes use?

Edgeone Makers Recipes 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 Recipes use?

About 2.8k tokens (SKILL.md is roughly 11k 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 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Edgeone Makers Recipes?

Skills that share tags, products or a category with Edgeone Makers Recipes: Docouture Docs Versioning (InditexTech/weavejs, 238 stars), Rtdf (any-tdf/any-tdf, 778 stars), Stdf (any-tdf/any-tdf, 778 stars) and Declarative Agent Developer (microsoft/work-iq, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Edgeone Makers Recipes?

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.