用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/oyi77/1ai-skills --skill deploy-agent命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Android and mobile application security testing — emulators, rooting, traffic interception, dynamic instrumentation. Use when testing mobile apps for vulnerabilities, reversing APKs, or bypassing security controls on Android.
Self-reflection + Self-criticism + Auto-learning from corrections + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when working with self improving.
Plan and execute a comprehensive red team engagement covering reconnaissance through post-exploitation using MITRE ATT&CK-aligned TTPs to evaluate an organization's detection and response capabilities. Use when working with conducting full scope red team engagement.
基于 SOC 职业分类
正在显示 SKILL.md
| name | deploy-agent |
| description | Use when ship code through controlled pipeline with verification gates and rollback plans. |
| domain | agents |
| author | oyi77 |
| license | Apache-2.0 |
| subdomain | ai-agents |
| tags | ["agent","ai-agent","automation","deploy","autonomous"] |
| version | 1.0.0 |
Quick Reference — see parent for full agent ecosystem.
The Deploy Agent ships artifacts to staging and production through a controlled pipeline with health checks, migration execution, automated rollbacks, and post-deploy monitoring. Its core design principle is reversibility: every deploy must have a tested rollback path before it begins.
# Refer to the skill's usage section for specific commands
# Adapt these to your workflow
"""Minimal deploy agent pattern — ship with verification."""
import json, subprocess, sys
from pathlib import Path
def deploy(target: str, tag: str, strategy: str = "rolling") -> dict:
# 1. Pre-deploy checks
assert subprocess.run(["git", "diff", "--quiet"], cwd=".").returncode == 0, "Dirty working tree"
assert subprocess.run([sys.executable, "-m", "pytest", "-x", "-q"]).returncode == 0
# 2. Build artifact
build = subprocess.run(["docker", "build", "-t", f"app:{tag}", "."], capture_output=True, text=True)
if build.returncode != 0:
return {"status": "failed", "error": build.stderr}
# 3. Run migrations (dry-run first)
dry = subprocess.run([sys.executable, "-m", "alembic", "upgrade", "--sql", "head"], capture_output=True, text=True)
print()
push = subprocess.run([, , ])
target == :
subprocess.run([, , , ])
subprocess.run([, , , ])
{
: target, : tag, : strategy,
: , :
}
__name__ == :
result = deploy(sys.argv[], sys.argv[], sys.argv[] (sys.argv) > )
(json.dumps(result, indent=))
downgrade)| Rationalization | Reality |
|---|---|
| "I will fix it if something goes wrong" | Manual recovery during an incident is slower and more error-prone than an automated rollback |
| "It works in staging, production will be fine" | Staging never matches production data volume, traffic pattern, or dependency versions |
| "Just one quick hotfix, skip the checks" | Skipping gates is how config drift and silent regressions enter production |
Use when shipping code to staging or production, running database migrations, performing rollbacks, deploying hotfixes, or setting up CI/CD pipelines. Do NOT use for experimental features needing manual verification first, changes requiring coordinated multi-service releases without a release train, or when the target environment is unreachable by the agent.