Openbkn Deploy
openbkn-ai/bkn-foundry
Deploy or upgrade OpenBKN on a customer-authorized Linux server through the repository's deploy scripts, with preflight checks, explicit confirmation, secret handling, and post-deployment…
Deploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill aliyun-fullstack-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills aliyun-fullstack-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/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/aliyun-fullstack-deploy .claude/skills/aliyun-fullstack-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 "aliyun-fullstack-deploy" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/aliyun-fullstack-deploy into .claude/skills/aliyun-fullstack-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aliyun-fullstack-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/FAIRY123456789/human-edge-agent-skills/tree/main/skills/aliyun-fullstack-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 FAIRY123456789/human-edge-agent-skills --skill aliyun-fullstack-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills aliyun-fullstack-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/aliyun-fullstack-deploy .agents/skills/aliyun-fullstack-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 "aliyun-fullstack-deploy" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/aliyun-fullstack-deploy into .agents/skills/aliyun-fullstack-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aliyun-fullstack-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 FAIRY123456789/human-edge-agent-skills --skill aliyun-fullstack-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills aliyun-fullstack-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/aliyun-fullstack-deploy .cursor/skills/aliyun-fullstack-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 "aliyun-fullstack-deploy" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/aliyun-fullstack-deploy into .cursor/skills/aliyun-fullstack-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aliyun-fullstack-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/FAIRY123456789/human-edge-agent-skills.git --path skills/aliyun-fullstack-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 FAIRY123456789/human-edge-agent-skills --skill aliyun-fullstack-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills aliyun-fullstack-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/aliyun-fullstack-deploy .gemini/skills/aliyun-fullstack-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 "aliyun-fullstack-deploy" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/aliyun-fullstack-deploy into .gemini/skills/aliyun-fullstack-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aliyun-fullstack-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 FAIRY123456789/human-edge-agent-skills aliyun-fullstack-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 FAIRY123456789/human-edge-agent-skills --skill aliyun-fullstack-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/aliyun-fullstack-deploy .github/skills/aliyun-fullstack-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 "aliyun-fullstack-deploy" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/aliyun-fullstack-deploy into .github/skills/aliyun-fullstack-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aliyun-fullstack-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 FAIRY123456789/human-edge-agent-skills --skill aliyun-fullstack-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 FAIRY123456789/human-edge-agent-skills aliyun-fullstack-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/aliyun-fullstack-deploy .opencode/skills/aliyun-fullstack-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 "aliyun-fullstack-deploy" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/aliyun-fullstack-deploy into .opencode/skills/aliyun-fullstack-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aliyun-fullstack-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.
aliyun-fullstack-deployDeploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback.
Aliyun Fullstack Deploy is an agent skill from FAIRY123456789/human-edge-agent-skills. Deploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback. Use for production deployment and recovery; never purchase infrastructure or mutate an unauthorized host.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 22 other files, including scripts and reference files (for example `README.md`, `agents/openai.yaml` and `references/ai-contract.example.json`).
It sits in DevOps & Cloud, covering Deployment. It works with Alibaba Cloud and Linux. The repository describes itself as: 18 portable Agent Skills for voice-native AI, human judgment, microbets, social tact, writing, life systems, and safe deployment. The licence is MIT.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 6ae0196. It shows what the files ask for, not the result of running them.
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.
Ships 10 files in scripts/ (Python and Shell, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
pythonnpmpnpmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm and pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Aliyun Fullstack Deploy loads about 1.9k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 934 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.
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.
The full file from FAIRY123456789/human-edge-agent-skills at commit 6ae0196, republished under its MIT licence (© FAIRY123456789). 934 words, ~1,917 tokens.
.claude/skills/aliyun-fullstack-deploy/SKILL.md (or your agent's skills folder). This skill also uses 19 other files; get the full folder from GitHub.Turn a repository and an authorized ECS into a reproducible, rollback-ready release. Move through explicit evidence gates: inspect, contract, preflight, package, canary, promote, verify, and report.
This Skill subsumes the earlier safe-shared-vps-deploy workflow: preserve existing sites and services as explicit protected assets, even when the target is not Alibaba Cloud.
Stop before mutation if the contract lacks a rollback target, persistence plan, protected-site inventory, or success checks.
Run:
python scripts/preflight_local.py <project-root>Use the report to classify single-page and static assets, Python, Node.js, or Java APIs, root or subpath routing, state, model artifacts, and AI-provider integration. Resolve missing lockfiles, production build outputs, runtime incompatibility, secret matches, CRLF deployment scripts, and absolute development-machine paths before packaging.
Run scripts/preflight_remote.sh over SSH with environment variables that describe the intended app paths. Save its output locally, redact it with scripts/redact_logs.py, and inspect captured nginx -T output with scripts/inspect_nginx.py.
Create a rollback point before every remote mutation. Do not create a second wildcard Nginx server block. Modify only the server block proven to own the route, then require nginx -t before reload.
pip. Never ship Windows wheels to Linux.npm ci, pnpm --frozen-lockfile, or the equivalent command documented by the repository. Prefer building static assets off-server when RAM is tight.Do not change the system runtime merely to satisfy one application when an isolated runtime is possible.
Create a small JSON config with project_name, immutable version, includes, and optional excludes, then run:
python scripts/build_release.py <project-root> --config <config.json>
python scripts/inspect_release.py <release.zip>Require portable ZIP entries, UTF-8 LF deployment text, a manifest, checksums, required static and model assets, and no local environment-secret file, private key, Git data, local state, dependency directory, cache, or absolute Windows path.
For AI-enabled apps, copy references/ai-contract.example.json, define an explicit JSON contract, and run scripts/validate_ai_contract.py. The contract must cover the backend client, route registration, frontend entry, environment-variable names, and offline and failure behavior without containing secret values.
Upload the verified archive by checksum and extract it outside the production path. Use a unique loopback port and isolated temporary state or a safe read-only snapshot.
The bundled scripts/deploy_canary.sh is a Python and FastAPI adapter. For Node.js or Java, preserve the same invariants: isolated directory, loopback binding, one disposable process, bounded readiness check, isolated state, and captured logs.
Canary proof must include the homepage, actual JavaScript and CSS assets, core APIs, one complete user flow, persistence or report export when applicable, AI offline behavior, and AI online behavior only when a key is already configured on the server. A health endpoint alone is never sufficient.
Use version directories such as /opt/<app>/releases/<version>, shared state outside releases, and an atomic current symlink. Preserve the existing server-side environment file. Back up systemd and Nginx configuration before a validated, idempotent edit.
Use scripts/promote_release.sh for its supported Python layout only after the canary passes. For other runtimes, implement the same atomic switch and automatic service-health rollback rather than editing the active release in place.
For a subpath, align the frontend build base, client router base, API base, upload and download URLs, Nginx location semantics, deep-route fallback, health URL, and documentation.
Run bounded GET checks; do not treat a HEAD 405 as a GET failure. scripts/verify_deployment.sh verifies real asset bodies and MIME types and supports a project-specific VERIFY_HOOK.
Verify systemd state, one intended backend process, loopback binding, writable shared state, page HTML, actual hashed assets, deep-route refresh, browser console and network activity, mobile layout, core data and API flows, report or upload flows, AI fallback, protected existing sites, idempotent redeploy, rollback, and post-rollback data preservation.
Automatically roll back for service or readiness failure, JavaScript-as-HTML, core API 500, Nginx validation failure, protected-site regression, missing model or AI import, unwritable persistence, failed export, or browser white screen. Do not restore shared state unless corruption is proven and data recovery is separately authorized.
Mark every gate PASS, FAIL, NOT TESTED, or EXTERNALLY BLOCKED. Include the public URL, active version and checksum, rollback target, redacted validation evidence, changed files, cleanup, remaining risks, and exact external action required.
Never claim completion while an in-scope check remains unresolved. After deployment, update the redacted server profile, version matrix, failure catalog, and validation record only with lessons demonstrated by evidence.
© FAIRY123456789, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 19 other files (scripts, references) in skills/aliyun-fullstack-deploy of FAIRY123456789/human-edge-agent-skills.
Open the folder on GitHubat commit 6ae0196
Aliyun Fullstack 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 |
|---|---|---|---|---|---|---|
| Aliyun Fullstack Deploy this skillFAIRY123456789/human-edge-agent-skills | 103 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Openbkn Deployopenbkn-ai/bkn-foundry | 645 | — | ~1.9k | Automated safety check: Notes | Custom licence | |
| Spa Create Configsplunk/splunk-platform-automator | 138 | — | ~3.5k | Automated safety check: Pass | Proprietary | |
| Deploy Observabilityaliyun/alibabacloud-observability-mcp-server | 166 | — | ~2.6k | Automated safety check: Notes | None | |
| Setup Workshopbrevdev/workshop-build-an-agent | 146 | — | ~2.3k | Automated safety check: Notes | Apache-2.0 | |
| Release Allpaperboytm/spool | 592 | — | ~1.1k | Automated safety check: Pass | Custom licence |
openbkn-ai/bkn-foundry
Deploy or upgrade OpenBKN on a customer-authorized Linux server through the repository's deploy scripts, with preflight checks, explicit confirmation, secret handling, and post-deployment…
splunk/splunk-platform-automator
A skill your agent uses when creating or updating splunkconfig.yml, designing Splunk Enterprise lab topology, multisite IDXC, SHC layout, architecture plan before config, or AWS Terraform block for…
aliyun/alibabacloud-observability-mcp-server
Deploy, start, and update the Alibaba Cloud Observability MCP Server (阿里云可观测 MCP Server).
brevdev/workshop-build-an-agent
This skill should be used when the user wants to set up, install, deploy, bootstrap, or "spin up" the Build-an-Agent workshop (a.k.a.
paperboytm/spool
Publish the complete Spool CLI release train: synchronized versions, npm packages, the GitHub release, and the matching production web deployment.
blotcms/blot
Work out why the blot-container-{blue,green,yellow} Docker containers from the most recent production deployment have restarted — distinguishing a normal deploy-triggered restart from a crash (V8…
FAIRY123456789/human-edge-agent-skills
Mine repeated pain from transcripts, project retrospectives, debugging logs, failed prompts, deployment notes, or work history and decide whether it deserves to become a reusable Agent Skill.
FAIRY123456789/human-edge-agent-skills
Convert a long, messy, repetitive, speech-recognition-heavy task dump into a precise executable to-do list.
FAIRY123456789/human-edge-agent-skills
Convert deployment logs, validation reports, Git history, and comparison notes into a redacted GitHub case study, portfolio entry, interview story, and evidence-backed resume bullets.
FAIRY123456789/human-edge-agent-skills
Convert messy voice input, imperfect speech recognition, half-formed product ideas, and iterative corrections into an implementation-ready software specification for Codex, Claude Code, Copilot…
FAIRY123456789/human-edge-agent-skills
Turn a finished or nearly finished Skill, plugin, repository, micro-tool, research utility, or AI project into a credible public launch that can earn real users and feedback.
FAIRY123456789/human-edge-agent-skills
Assess whether a web application and its build and runtime plan fit a low-cost Linux VPS or Alibaba Cloud ECS before purchase, implementation, or deployment.
Works with
Categories
Deploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback. Aliyun Fullstack Deploy is an agent skill from FAIRY123456789/human-edge-agent-skills. Deploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback.
Aliyun Fullstack Deploy fits situations like: production deployment and recovery; never purchase infrastructure; mutate an unauthorized host.
Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill aliyun-fullstack-deploy -a claude-code`. Or copy the skill folder (skills/aliyun-fullstack-deploy in FAIRY123456789/human-edge-agent-skills) into .claude/skills/aliyun-fullstack-deploy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill aliyun-fullstack-deploy -a codex`. Or copy the skill folder (skills/aliyun-fullstack-deploy in FAIRY123456789/human-edge-agent-skills) into .agents/skills/aliyun-fullstack-deploy in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FAIRY123456789/human-edge-agent-skills --skill aliyun-fullstack-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/aliyun-fullstack-deploy, .gemini/skills/aliyun-fullstack-deploy, .github/skills/aliyun-fullstack-deploy and .opencode/skills/aliyun-fullstack-deploy in your project.
Going by SKILL.md and its folder, Aliyun Fullstack Deploy needs Python and a shell for the scripts in its folder and the command-line tools its instructions call (python, npm and pnpm). Our summary lists: Python 3; Node.js; A Bash shell.
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Aliyun Fullstack Deploy is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.7k 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 2.4k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Aliyun Fullstack Deploy: Openbkn Deploy (openbkn-ai/bkn-foundry, 645 stars), Spa Create Config (splunk/splunk-platform-automator, 138 stars), Deploy Observability (aliyun/alibabacloud-observability-mcp-server, 166 stars) and Setup Workshop (brevdev/workshop-build-an-agent, 146 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
FAIRY123456789 (a GitHub user) maintains it in FAIRY123456789/human-edge-agent-skills, which has 103 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on September 30, 2026.
Source: FAIRY123456789/human-edge-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.