Agent skill

Aliyun Fullstack Deploy

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

MITAuto-check passedDevOps & Cloud

Install Aliyun Fullstack Deploy

skills CLI
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill aliyun-fullstack-deploy -a claude-code

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

GitHub CLI
$ gh skill install FAIRY123456789/human-edge-agent-skills aliyun-fullstack-deploy --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/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-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
aliyun-fullstack-deploy
GitHub stars
103
Token cost
~1.9k tokens
SKILL.md length
934 words
Files
20 (incl. scripts, references)
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Deploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback.

  • Works in 7 steps: Read repository-level agent instructions… → Confirm the project root, SSH host alias… → Confirm the user owns or administers the… → …
  • Production deployment and recovery
  • SKILL.md covers Purpose, Start with a deployment contract, Detect and preflight and Choose a runtime deliberately, plus 5 more sections
  • Runs Python and Shell scripts from its folder; calls python, npm and pnpm

What it does

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.

When your agent uses it

  • Production deployment and recovery
  • Never purchase infrastructure
  • Mutate an unauthorized host

Example prompts

  • “/aliyun-fullstack-deploy”

Requirements

  • Python 3
  • Node.js
  • A Bash shell

Workflow steps

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

  1. Read repository-level agent instructions and deployment documentation.
  2. Confirm the project root, SSH host alias or address, SSH user and port, public route, app and service names, runtime, state locations…
  3. Confirm the user owns or administers the target. Treat inspection as read-only; ask immediately before the first remote mutation unless…
  4. Prefer a dedicated deployment account with access only to the application paths and service controls it needs. Use privilege elevation…
  5. Keep passwords, tokens, private keys, and database URLs in SSH Agent, interactive input, or server-side environment files. Never print or…
  6. Read references/workflow.md. If server capacity or runtime choice is uncertain, also read references/runtime-selection.md.
  7. Create a server profile from references/server-profile-template.md. Re-run preflight instead of trusting an old profile.

What it can do on your machine

Read from SKILL.md and the folder at commit 6ae0196. 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 10 files in scripts/ (Python and Shell, from the files we listed), which the agent can run.

    Shell commands in SKILL.md call:

    • python
    • npm
    • pnpm

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

  • Network

    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.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
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); the scripts in this folder are not scanned.

SKILL.md

The full file from FAIRY123456789/human-edge-agent-skills at commit 6ae0196, republished under its MIT licence (© FAIRY123456789). 934 words, ~1,917 tokens.

Download SKILL.mdSave it as .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.
name
aliyun-fullstack-deploy
description
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.
license
MIT
metadata.author
Joy T <101039451+FAIRY123456789@users.noreply.github.com>
metadata.tags
deployment, alibaba-cloud, devops

Aliyun Full-Stack Deploy

Purpose

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.

Start with a deployment contract

  1. Read repository-level agent instructions and deployment documentation.
  2. Confirm the project root, SSH host alias or address, SSH user and port, public route, app and service names, runtime, state locations, protected existing sites, and validation hooks.
  3. Confirm the user owns or administers the target. Treat inspection as read-only; ask immediately before the first remote mutation unless the user already authorized deployment.
  4. Prefer a dedicated deployment account with access only to the application paths and service controls it needs. Use privilege elevation only for a specifically authorized system change.
  5. Keep passwords, tokens, private keys, and database URLs in SSH Agent, interactive input, or server-side environment files. Never print or copy them into the repository, release, command arguments, or report.
  6. Read references/workflow.md. If server capacity or runtime choice is uncertain, also read references/runtime-selection.md.
  7. Create a server profile from references/server-profile-template.md. Re-run preflight instead of trusting an old profile.

Stop before mutation if the contract lacks a rollback target, persistence plan, protected-site inventory, or success checks.

Detect and preflight

Run:

bash
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.

Choose a runtime deliberately

  • Python: pin an available interpreter by full path and build a new virtual environment when it differs from the artifact runtime. Install through that virtual-environment interpreter, never bare pip. Never ship Windows wheels to Linux.
  • Node.js: honor the lockfile with npm ci, pnpm --frozen-lockfile, or the equivalent command documented by the repository. Prefer building static assets off-server when RAM is tight.
  • Java: verify the JRE major against the built artifact and compare the JAR checksum before launch.
  • Model artifacts: verify Python and library compatibility with the environment that serialized the model; rebuild the artifact when compatibility is not demonstrated.

Do not change the system runtime merely to satisfy one application when an isolated runtime is possible.

Build a clean release

Create a small JSON config with project_name, immutable version, includes, and optional excludes, then run:

bash
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.

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

Canary before production

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.

Promote atomically

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.

Verify and roll back

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.

Report evidence, not confidence

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

Files

SKILL.md and 19 other files (scripts, references) in skills/aliyun-fullstack-deploy of FAIRY123456789/human-edge-agent-skills.

  • SKILL.md
  • README.md
  • agents/openai.yaml
  • references/ai-contract.example.json
  • references/example-small-ecs-baseline.md
  • references/runtime-selection.md
  • references/server-profile-template.md
  • references/workflow.md
  • scripts/build_release.py
  • scripts/check_python_runtime.sh
  • scripts/deploy_canary.sh
  • scripts/inspect_nginx.py
  • scripts/inspect_release.py
  • scripts/preflight_local.py
  • scripts/preflight_remote.sh
  • scripts/promote_release.sh
  • scripts/redact_logs.py
  • scripts/rollback_release.sh
  • … and 2 more

Open the folder on GitHubat commit 6ae0196

Compare with similar skills

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.

Aliyun Fullstack Deploy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Aliyun Fullstack Deploy this skillFAIRY123456789/human-edge-agent-skills103—~1.9kAutomated safety check: PassMIT
Openbkn Deployopenbkn-ai/bkn-foundry645—~1.9kAutomated safety check: NotesCustom licence
Spa Create Configsplunk/splunk-platform-automator138—~3.5kAutomated safety check: PassProprietary
Deploy Observabilityaliyun/alibabacloud-observability-mcp-server166—~2.6kAutomated safety check: NotesNone
Setup Workshopbrevdev/workshop-build-an-agent146—~2.3kAutomated safety check: NotesApache-2.0
Release Allpaperboytm/spool592—~1.1kAutomated safety check: PassCustom licence

Similar skills

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

    645 GitHub stars~1.9k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Spa Create Config

    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…

    138 GitHub stars~3.5k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • Deploy Observability

    aliyun/alibabacloud-observability-mcp-server

    Deploy, start, and update the Alibaba Cloud Observability MCP Server (阿里云可观测 MCP Server).

    166 GitHub stars~2.6k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes
  • Setup Workshop

    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.

    146 GitHub stars~2.3k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Release All

    paperboytm/spool

    Publish the complete Spool CLI release train: synchronized versions, npm packages, the GitHub release, and the matching production web deployment.

    592 GitHub stars~1.1k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • 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…

    2k GitHub stars~4.7k tokensUpdated today
    DevOps & CloudAuto-check passed

More from FAIRY123456789/human-edge-agent-skills

All 18 skills in this repo
  • Skill From Scars

    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.

    103 GitHub stars~856 tokensUpdated 9 days ago
    Auto-check passed
  • Voice Dump To Todo

    FAIRY123456789/human-edge-agent-skills

    Convert a long, messy, repetitive, speech-recognition-heavy task dump into a precise executable to-do list.

    103 GitHub stars~1.1k tokensUpdated 9 days ago
    Auto-check passed
  • Deployment Proof

    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.

    103 GitHub stars~980 tokensUpdated 9 days ago
    Auto-check passed
  • Vibe To Spec

    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…

    103 GitHub stars~997 tokensUpdated 9 days ago
    Auto-check passed
  • Build In Public Launcher

    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.

    103 GitHub stars~708 tokensUpdated 9 days ago
    Auto-check passed
  • Small Server Fit

    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.

    103 GitHub stars~1k tokensUpdated 9 days ago
    Auto-check passed

Categories

Questions about Aliyun Fullstack Deploy

What does Aliyun Fullstack Deploy do?

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.

When should I use Aliyun Fullstack Deploy?

Aliyun Fullstack Deploy fits situations like: production deployment and recovery; never purchase infrastructure; mutate an unauthorized host.

How do I install Aliyun Fullstack Deploy in Claude Code?

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.

How do I install Aliyun Fullstack Deploy in Codex?

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.

Can I use Aliyun Fullstack 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 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.

What does Aliyun Fullstack Deploy need to run?

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.

Does Aliyun Fullstack Deploy access the network?

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.

Is Aliyun Fullstack 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 Aliyun Fullstack Deploy use?

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.

How many tokens does Aliyun Fullstack Deploy use?

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.

What are the alternatives to Aliyun Fullstack Deploy?

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.

Who maintains Aliyun Fullstack Deploy?

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.