Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
This skill deploys frontend and full-stack projects to EdgeOne Makers (Tencent EdgeOne).
Install Edgeone Makers Deploy
$ npx skills add infometa/workbuddyskills --skill edgeone-makers-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install infometa/workbuddyskills edgeone-makers-deploy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/connectors/edgeone-pages/skills/references/makers-deploy .claude/skills/edgeone-makers-deploy && rm -rf skills-srcUse ~/.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/
Install the "edgeone-makers-deploy" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/edgeone-pages/skills/references/makers-deploy into .claude/skills/edgeone-makers-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgeone-makers-deploy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/infometa/workbuddyskills/tree/main/connectors/edgeone-pages/skills/references/makers-deployType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add infometa/workbuddyskills --skill edgeone-makers-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install infometa/workbuddyskills edgeone-makers-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/connectors/edgeone-pages/skills/references/makers-deploy .agents/skills/edgeone-makers-deploy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "edgeone-makers-deploy" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/edgeone-pages/skills/references/makers-deploy into .agents/skills/edgeone-makers-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgeone-makers-deploy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add infometa/workbuddyskills --skill edgeone-makers-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install infometa/workbuddyskills edgeone-makers-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/connectors/edgeone-pages/skills/references/makers-deploy .cursor/skills/edgeone-makers-deploy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "edgeone-makers-deploy" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/edgeone-pages/skills/references/makers-deploy into .cursor/skills/edgeone-makers-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgeone-makers-deploy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/infometa/workbuddyskills.git --path connectors/edgeone-pages/skills/references/makers-deploy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add infometa/workbuddyskills --skill edgeone-makers-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install infometa/workbuddyskills edgeone-makers-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/connectors/edgeone-pages/skills/references/makers-deploy .gemini/skills/edgeone-makers-deploy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "edgeone-makers-deploy" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/edgeone-pages/skills/references/makers-deploy into .gemini/skills/edgeone-makers-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgeone-makers-deploy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install infometa/workbuddyskills edgeone-makers-deployInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add infometa/workbuddyskills --skill edgeone-makers-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/connectors/edgeone-pages/skills/references/makers-deploy .github/skills/edgeone-makers-deploy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "edgeone-makers-deploy" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/edgeone-pages/skills/references/makers-deploy into .github/skills/edgeone-makers-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgeone-makers-deploy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add infometa/workbuddyskills --skill edgeone-makers-deploy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install infometa/workbuddyskills edgeone-makers-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/connectors/edgeone-pages/skills/references/makers-deploy .opencode/skills/edgeone-makers-deploy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "edgeone-makers-deploy" agent skill from https://github.com/infometa/workbuddyskills/tree/main/connectors/edgeone-pages/skills/references/makers-deploy into .opencode/skills/edgeone-makers-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgeone-makers-deploy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
edgeone-makers-deploy- GitHub stars
- 346
- Token cost
- ~5.8k tokens
- SKILL.md length
- 2,715 words
- Files
- 3 (incl. scripts, references)
- Skills in repo
- 218
- Repo updated
- First seen
- Licence
- None found
At a glance
This skill deploys frontend and full-stack projects to EdgeOne Makers (Tencent EdgeOne).
- Works in 4 steps: Explain the registration/login step → Ask the user to choose a site, then… → Login methods reference → …
- This skill whenever deployment is part of the task — whether as the primary intent
- SKILL.md covers ⛔ Critical Rules (never skip), Environment Setup, Deployment Flow and Install CLI, plus 5 more sections
- Runs JavaScript scripts from its folder; calls npm and node; reaches console.cloud.tencent.com; needs EDGEONE_PAGES_API_TOKEN
What it does
Edgeone Makers Deploy is an agent skill from infometa/workbuddyskills. This skill deploys frontend and full-stack projects to EdgeOne Makers (Tencent EdgeOne). Trigger this skill whenever deployment is part of the task — whether as the primary intent or a secondary step. Examples: "deploy my app", "publish this site", "push this live", "create a preview deployment", "deploy to EdgeOne", "ship to production", "go live", "release", "publish a new version", "redeploy", "上线", "发布", "发一版", "重新部署", "搭建并部署", "开发并上线", "build and deploy", "create and deploy". ⚠️ Also trigger when any agent…
Its SKILL.md is about 5.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/command-reference.md`).
It sits in DevOps & Cloud, covering Deployment. The repository describes itself as: WorkBuddy skills / connectors / experts archive for offline study.
When your agent uses it
- This skill whenever deployment is part of the task — whether as the primary intent
- A secondary step
- Any agent is about to execute edgeone makers deploy
- Edgeone makers deploy commands — the skill contains critical rules for parsing deploy output and presenting access URLs
Example prompts
- “deploy my app”
- “publish this site”
- “push this live”
- “/edgeone-makers-deploy”
Requirements
- Node.js
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Explain the registration/login step
- Ask the user to choose a site, then ALWAYS pass --site
- Login methods reference
- Offer to save the token locally
What it can do on your machine
Read from SKILL.md and the folder at commit 692b3eb. 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
Ships 1 file in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
npmnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
console.cloud.tencent.com
Also links to:
console.intl.cloud.tencent.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
EDGEONE_PAGES_API_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Edgeone Makers Deploy loads about 5.8k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 212 tokens; SKILL.md has 2,715 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 2,715 words (~5,794 tokens).
“Deploy any project to EdgeOne Makers.”
- name
- edgeone-makers-deploy
- pathPatterns
- *.sh, .github/workflows/**
- metadata.author
- edgeone
- metadata.version
- 2.2.0
Files
SKILL.md and 2 other files (scripts, references) in connectors/edgeone-pages/skills/references/makers-deploy of infometa/workbuddyskills.
- SKILL.md
- references/command-reference.md
- scripts/deploy.mjs
Open the folder on GitHubat commit 692b3eb
Compare with similar skills
Edgeone Makers Deploy 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Edgeone Makers Deploy this skillinfometa/workbuddyskills | 346 | — | ~5.8k | Automated safety check: Pass | None | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercelremotion-dev/remotion | 63k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
- Official
Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
More from infometa/workbuddyskills
All 218 skills in this repoCampus Event Playbook
infometa/workbuddyskills
This skill should be used when planning, coordinating, running, or reviewing student-led campus events, including club recruitment, freshman mixers, welcome activities, small talks, competitions…
Teachany
infometa/workbuddyskills
K-12 interactive courseware creation. An agent skill from infometa/workbuddyskills.
Weight Management HTML
infometa/workbuddyskills
A skill your agent uses when the adult weight-management MCP needs to be installed/set up in WorkBuddy (connector) or its result must be rendered as a standalone Chinese HTML plan.
Agent Browser
infometa/workbuddyskills
A skill your agent uses when the user needs browser automation, including opening web pages, taking screenshots, extracting page content, clicking elements, filling forms, or testing web flows.
AI Research Radar
infometa/workbuddyskills
定时任务：每日研究简报。漏掉重要论文和行业报告？每天帮你盯着，关键信息一条不漏 This skill should be used when the user asks about 定时任务：每日研究简报.
Check Deck
infometa/workbuddyskills
Investment banking presentation quality checker. An agent skill from infometa/workbuddyskills.
Related
Categories
Questions about Edgeone Makers Deploy
What does Edgeone Makers Deploy do?
This skill deploys frontend and full-stack projects to EdgeOne Makers (Tencent EdgeOne). Edgeone Makers Deploy is an agent skill from infometa/workbuddyskills. This skill deploys frontend and full-stack projects to EdgeOne Makers (Tencent EdgeOne).
When should I use Edgeone Makers Deploy?
Edgeone Makers Deploy fits situations like: this skill whenever deployment is part of the task — whether as the primary intent; A secondary step; any agent is about to execute edgeone makers deploy; edgeone makers deploy commands — the skill contains critical rules for parsing deploy output and presenting access URLs.
How do I install Edgeone Makers Deploy in Claude Code?
Run `npx skills add infometa/workbuddyskills --skill edgeone-makers-deploy -a claude-code`. Or copy the skill folder (connectors/edgeone-pages/skills/references/makers-deploy in infometa/workbuddyskills) into .claude/skills/edgeone-makers-deploy in your project. Claude Code loads it when a task matches its description.
How do I install Edgeone Makers Deploy in Codex?
Run `npx skills add infometa/workbuddyskills --skill edgeone-makers-deploy -a codex`. Or copy the skill folder (connectors/edgeone-pages/skills/references/makers-deploy in infometa/workbuddyskills) into .agents/skills/edgeone-makers-deploy in your project. Codex loads it when a task matches its description.
Can I use Edgeone Makers Deploy 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 infometa/workbuddyskills --skill edgeone-makers-deploy -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-deploy, .gemini/skills/edgeone-makers-deploy, .github/skills/edgeone-makers-deploy and .opencode/skills/edgeone-makers-deploy in your project.
What does Edgeone Makers Deploy need to run?
Going by SKILL.md and its folder, Edgeone Makers Deploy needs JavaScript for the scripts in its folder, the command-line tools its instructions call (npm and node) and credentials named EDGEONE_PAGES_API_TOKEN. Our summary lists: Node.js.
Does Edgeone Makers Deploy access the network?
SKILL.md names 2 domains. In commands or code: console.cloud.tencent.com; the agent is likely to contact it when it follows the instructions. As links in the text: console.intl.cloud.tencent.com. This is read from the text; nothing was executed.
Is Edgeone Makers Deploy 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Edgeone Makers Deploy use?
No licence was found for Edgeone Makers Deploy or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Edgeone Makers Deploy use?
About 5.8k tokens (SKILL.md is roughly 23k 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 855 tokens, read only when the agent opens those files.
What are the alternatives to Edgeone Makers Deploy?
Skills that share tags, products or a category with Edgeone Makers Deploy: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars) and Vercel (remotion-dev/remotion, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Edgeone Makers Deploy?
infometa (a GitHub user) maintains it in infometa/workbuddyskills, which has 346 GitHub stars. The repository holds 218 skills in this directory. The repository was last updated on October 8, 2026.
Source: infometa/workbuddyskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.