Server Autopilot

Read connection credentials from a user-provided file, test FTP and MySQL connectivity, then optionally upload code and execute SQL — with confirmation required before any write operation.

Quick Start — How to Trigger

Just say any of these in natural language:

• "帮我上传代码到服务器" / "上传网站" / "发布代码"
• "测试一下服务器连接" / "FTP能不能连上"
• "帮我跑个SQL" / "执行这个SQL文件"
• "同步文件到FTP" / "推送到服务器"
• "deploy my code" / "upload to server" / "run SQL"

The agent will automatically load this skill, read your config file (or recall previously noted credentials), test connections, and guide you through the deployment step by step.

Workflow Overview

Phase 1: Load credentials (recalled memory -> config file)
Phase 2: Test connectivity (read-only, safe)
Phase 3: Save non-secret metadata (for future sessions)
Phase 4: Deploy operations (write, requires confirmation)

Cross-Platform Note

This skill is platform-agnostic. It describes capabilities, not specific tool names.

• "Persistent memory" means whatever persistent-recall capability the current Agent platform provides (for example a built-in memory store, project notes, or a user-managed file). Do not assume a specific tool name such as memory_search or memory action=replace exists.
• "User confirmation" means whatever confirmation mechanism the current Agent platform provides (for example a built-in approval prompt, an inline yes/no question, or a UI dialog). Do not assume a specific tool name such as AskUserQuestion exists.
• If the platform provides no persistent memory, credentials may be used only within the current session and must be re-read from the config file in the next session.
• If the platform provides no confirmation mechanism, the agent MUST ask the user inline (plain text question) and wait for an explicit reply before any write operation.
• Do not assume all Agent platforms offer the same tool names. Map the capabilities below to the tools that are actually available in the current environment.

Phase 1: Load Credentials

Step 1.1 — Check recalled memory first

Use the platform's persistent-recall capability (whatever it is called locally) to look for previously saved server metadata:

• Query for an entry tagged [server-autopilot] containing FTP/MySQL host, port, username, remote dir, and database name.
• Passwords are NOT recalled from memory by default (see Phase 3). The agent should expect to re-read the password from the config file each session, unless the user has explicitly opted in to saving passwords.
• If non-secret metadata is found -> show the user a summary (mask any password with ****) and ask: "I found saved connection info. Use it (you'll still need to provide the password), or re-read everything from file?"
• If nothing is found -> proceed to Step 1.2

Step 1.2 — Read config file

Ask the user for the config file path if not provided. Then read and parse it.

Smart parsing rules — the agent must identify these fields regardless of format:

Supported formats — detect and parse automatically:

• key=value (ftp_host=1.2.3.4)
• JSON ({"ftp_host": "1.2.3.4"})
• YAML (ftp_host: 1.2.3.4)
• INI sections ([ftp] / [mysql])
• Freeform text — use context to infer; if ambiguous, list candidates and ask user to confirm

Step 1.3 — Present parsed result

Show the user a clean summary with passwords masked:

Parsed credentials:

FTP:
  Host: 192.168.1.100:21
  User: deploy_user
  Pass: ****
  Remote dir: /www/site/ (未指定时默认为 / — FTP 当前目录)

MySQL:
  Host: 192.168.1.100:3306
  User: root
  Pass: ****
  Database: myapp

Correct? Or need to adjust?

Wait for user confirmation before proceeding.

Phase 2: Test Connectivity

Test connections using read-only commands. These are safe and require no confirmation. Report results clearly.

FTP connectivity test

Prefer SFTP or FTPS where available. Plain FTP transmits credentials and data in cleartext — if the server only supports plain FTP, you MUST warn the user before proceeding:

> ⚠️ Plain FTP is an unencrypted protocol. Credentials and file contents will be transmitted in cleartext. Prefer SFTP/FTPS if the server supports it.

Do NOT pass credentials via --user "USER:PASS" on the command line — after shell variable expansion the password still ends up in the process argv and is visible in process listings (ps), other processes, and audit logs. The same applies to PowerShell variables: $ftpPass expansion still puts the password into the child process command line.

Instead, write credentials to a temporary curl config file with permission 0600, reference it with --config, and clean up via trap so the file is removed even if the command is interrupted:

# Generate a temporary curl config file (permission 0600)
CurlConfig=$(mktemp)
chmod 0600 "$CurlConfig"
cat > "$CurlConfig" <<EOF
user = "USER:PASS"
connect-timeout = 10
EOF

trap 'rm -f "$CurlConfig"' EXIT INT TERM

curl -s -o /dev/null -w "HTTP_CODE:%{http_code}" --config "$CurlConfig" ftp://HOST:PORT/

rm -f "$CurlConfig"
trap - EXIT INT TERM

Never log the contents of the curl config file. Never echo the password to stdout, logs, or the user.

On Windows (PowerShell), the same risk applies — PowerShell variable expansion does NOT prevent the password from appearing in the child process argv. Use a temporary config file with restrictive ACL and clean it up in finally:

$curlConfig = [System.IO.Path]::GetTempFileName()
# Restrict ACL to current user only
icacls $curlConfig /inheritance:r /grant:r "$($env:USERNAME):(R,W)"
"user = `"USER:PASS`"`nconnect-timeout = 10" | Set-Content -Path $curlConfig -NoNewline
try {
    curl.exe -s -o NUL -w "HTTP_CODE:%{http_code}" --config $curlConfig ftp://HOST:PORT/
} finally {
    Remove-Item -Force $curlConfig -ErrorAction SilentlyContinue
}

If curl is unavailable, fall back to a manual ftp session (read credentials from a temp file or stdin, never from argv — same masking rules apply):

ftp -n -v HOST PORT <<EOF
user USER PASS
quit
EOF

MySQL connectivity test

Do NOT pass the password on the command line (-p'PASS' is visible in process listings and shell history). Use a temporary defaults file with permission 0600, and clean it up via trap so the file is removed even if the command is interrupted:

# Generate a temporary defaults file (permission 0600)
MYSQLDefaultsFile=$(mktemp)
chmod 0600 "$MYSQLDefaultsFile"
cat > "$MYSQLDefaultsFile" <<EOF
[client]
host=HOST
port=PORT
user=USER
password=PASS
EOF

trap 'rm -f "$MYSQLDefaultsFile"' EXIT INT TERM

mysql --defaults-extra-file="$MYSQLDefaultsFile" -e "SELECT 1 AS connection_test;" --connect-timeout=10

rm -f "$MYSQLDefaultsFile"
trap - EXIT INT TERM

Never log the contents of the defaults file. Never echo the password to stdout, logs, or the user.

Report results

Connectivity test results:

FTP  (192.168.1.100:21)  -> OK Connected
MySQL (192.168.1.100:3306) -> FAIL: Access denied for user 'root'

Please check the failed credentials and try again.

If any test fails, stop and ask the user to correct credentials. Do NOT proceed to Phase 4 until all required connections pass.

Phase 3: Save Non-Secret Metadata

After successful connectivity tests, optionally save connection metadata using the platform's persistent-recall capability (whatever it is called locally).

Default policy — secrets are NOT persisted:

• Save ONLY non-secret fields: host, port, username, remote_dir, database, and a tag like [server-autopilot].
• Do NOT save passwords by default. The user will be asked to re-enter the password (or re-read it from the config file) in the next session.
• Only if the user explicitly opts in (e.g. replies "yes, save the password too") may the password be stored — and only via the most secure mechanism the platform offers:
• Prefer the operating system keychain / secret storage (macOS Keychain, Windows Credential Manager, libsecret on Linux) if the platform exposes it.
• If no secret storage is available and the user still insists, store the password in the platform's memory — but explicitly warn the user that it may be synced, exported, or readable by other processes depending on the platform.

Do NOT claim that all platforms' memory is local, encrypted, or never synced. Memory behavior is platform-dependent. State plainly what is known and what is not.

When saving, use whatever update/replace capability the platform provides (e.g. an edit/replace operation on a stored note). If the platform only supports append, deduplicate by the [server-autopilot] tag when reading.

If the platform provides no persistent memory at all, skip this phase — credentials will be used only in the current session.

Phase 4: Deploy Operations (Confirmation Required)

HARD RULE: Every write operation requires explicit user confirmation before execution. Use whatever confirmation mechanism the current Agent platform provides. If the platform provides no built-in confirmation tool, ask the user inline in plain text and wait for an explicit reply. No exceptions.

Read-only operations (connectivity tests, SHOW TABLES, SHOW COLUMNS, ls of a remote dir) do NOT require confirmation.

4A — FTP Upload

Before uploading, present a detailed plan:

FTP Upload Plan:

Source (local):  ./dist/
Target (remote): /www/site/dist/
Files to upload: 12 files (total 3.4 MB)

File list:
  dist/index.html
  dist/app.js
  dist/style.css
  ...

Action: Upload all files via FTP to 192.168.1.100

Ask the user to confirm with one of:
- "Confirm upload" / "Preview only" / "Cancel"

Upload commands — do NOT pass credentials via --user on the command line (the password ends up in process argv after variable expansion). Use a temporary curl config file with permission 0600 and trap cleanup, same as the connectivity test. Do NOT echo the full command back to the user.

Single file:

CurlConfig=$(mktemp)
chmod 0600 "$CurlConfig"
cat > "$CurlConfig" <<EOF
user = "USER:PASS"
EOF
trap 'rm -f "$CurlConfig"' EXIT INT TERM

curl --config "$CurlConfig" -T "local_file" ftp://HOST:PORT/REMOTE_PATH/

# Verify the upload BEFORE cleanup (reuse the same config file)
curl -s --config "$CurlConfig" ftp://HOST:PORT/REMOTE_PATH/

rm -f "$CurlConfig"
trap - EXIT INT TERM

Directory (recursive — use a loop, reuse the same config file):

CurlConfig=$(mktemp)
chmod 0600 "$CurlConfig"
cat > "$CurlConfig" <<EOF
user = "USER:PASS"
ftp-create-dirs
EOF
trap 'rm -f "$CurlConfig"' EXIT INT TERM

for file in $(find LOCAL_DIR -type f); do
  relative="${file#LOCAL_DIR/}"
  curl --config "$CurlConfig" -T "$file" "ftp://HOST:PORT/REMOTE_DIR/$relative"
done

# Verify the upload BEFORE cleanup (reuse the same config file)
curl -s --config "$CurlConfig" ftp://HOST:PORT/REMOTE_DIR/

rm -f "$CurlConfig"
trap - EXIT INT TERM

On Windows (PowerShell) — PowerShell variable expansion does NOT prevent the password from appearing in the child process argv. Use a temporary config file with restrictive ACL:

$curlConfig = [System.IO.Path]::GetTempFileName()
icacls $curlConfig /inheritance:r /grant:r "$($env:USERNAME):(R,W)"
"user = `"USER:PASS`"`nftp-create-dirs" | Set-Content -Path $curlConfig -NoNewline
try {
    Get-ChildItem -Recurse -File "LOCAL_DIR" | ForEach-Object {
        $relative = $_.FullName.Substring("LOCAL_DIR".Length).Replace("\","/")
        curl.exe --config $curlConfig -T $_.FullName "ftp://HOST:PORT/REMOTE_DIR/$relative"
    }
    # Verify the upload BEFORE cleanup
    curl.exe -s --config $curlConfig ftp://HOST:PORT/REMOTE_DIR/
} finally {
    Remove-Item -Force $curlConfig -ErrorAction SilentlyContinue
}

4B — SQL Execution

Before executing, present the SQL content and target:

SQL Execution Plan:

Target: MySQL 192.168.1.100:3306 / myapp

SQL to execute:
---
ALTER TABLE users ADD COLUMN avatar VARCHAR(255);
UPDATE users SET avatar = 'default.png' WHERE avatar IS NULL;
---

Warning: This will modify table structure and update 150 rows.

Ask the user to confirm with one of:
- "Execute SQL" / "Dry run (explain only)" / "Cancel"

Execution command — use a temporary defaults file (permission 0600) instead of -p'PASS'. Clean up via trap so the file is removed even if interrupted.

From string:

MYSQLDefaultsFile=$(mktemp)
chmod 0600 "$MYSQLDefaultsFile"
cat > "$MYSQLDefaultsFile" <<EOF
[client]
host=HOST
port=PORT
user=USER
password=PASS
EOF
trap 'rm -f "$MYSQLDefaultsFile"' EXIT INT TERM

mysql --defaults-extra-file="$MYSQLDefaultsFile" DATABASE -e "SQL_STATEMENT"

rm -f "$MYSQLDefaultsFile"
trap - EXIT INT TERM

From file:

MYSQLDefaultsFile=$(mktemp)
chmod 0600 "$MYSQLDefaultsFile"
cat > "$MYSQLDefaultsFile" <<EOF
[client]
host=HOST
port=PORT
user=USER
password=PASS
EOF
trap 'rm -f "$MYSQLDefaultsFile"' EXIT INT TERM

mysql --defaults-extra-file="$MYSQLDefaultsFile" DATABASE < "path/to/file.sql"

rm -f "$MYSQLDefaultsFile"
trap - EXIT INT TERM

Always capture and display the result. Never log the defaults file contents.

SQL executed successfully.
Rows affected: 150

Error Handling

SQL Error Diagnosis

When SQL execution fails, follow these steps:

1. Show the full MySQL error message — it usually contains error code and line number
2. Identify the error type:
   - ERROR 1064 (Syntax error) — highlight the problematic clause, suggest corrected SQL
   - ERROR 1054 (Unknown column) — check if column name has typos, suggest SHOW COLUMNS FROM table
   - ERROR 1146 (Table doesn't exist) — suggest SHOW TABLES to verify table name
   - ERROR 1062 (Duplicate entry) — explain the unique constraint conflict, suggest ON DUPLICATE KEY UPDATE
   - ERROR 1452 (Foreign key constraint) — explain the reference issue, suggest checking parent table
3. Offer to run a diagnostic query (read-only, no confirmation needed). Use the same defaults-file + trap approach:
   ```bash
   MYSQLDefaultsFile=$(mktemp)
   chmod 0600 "$MYSQLDefaultsFile"
   cat > "$MYSQLDefaultsFile" <<EOF
   [client]
   host=HOST
   port=PORT
   user=USER
   password=PASS
   EOF
   trap 'rm -f "$MYSQLDefaultsFile"' EXIT INT TERM

mysql --defaults-extra-file="$MYSQLDefaultsFile" DATABASE -e "SHOW TABLES; SHOW COLUMNS FROM problematic_table;"

rm -f "$MYSQLDefaultsFile"
trap - EXIT INT TERM
```
4. Present the corrected SQL and ask for explicit confirmation before re-executing
5. Do NOT auto-retry — always let the user review and approve the fix. A modified SQL statement is a new write operation and requires fresh confirmation.

Credential Cleanup

When the user says "clear credentials" (or "清除凭据"):

1. Use the platform's persistent-recall capability to locate the [server-autopilot] entry.
2. Remove the entry using whatever delete/remove operation the platform provides.
3. If a password was saved to the OS keychain / secret storage, remove it there too.
4. Confirm to the user: "Server connection info has been cleared."

If the platform provides no persistent memory, simply tell the user that nothing was persisted and credentials were only held in-session.

Troubleshooting FAQ

Q: FTP 连接超时怎么办？
A: 通常是防火墙或网络问题。按顺序检查：1) 服务器是否开放了 21 端口；2) 服务器防火墙是否放行了你的 IP；3) 尝试被动模式（Skill 会自动尝试 curl --ftp-pasv）；4) 确认服务器 FTP 服务是否正在运行。

Q: MySQL 提示 "Access denied" 或 "Host not allowed"？
A: MySQL 的用户权限通常绑定了来源 IP。需要在 MySQL 服务器上执行 GRANT ALL ON db.* TO 'user'@'your_ip' IDENTIFIED BY 'password'; 来授权你的 IP。也可能是密码错误，先确认密码是否正确。

Q: 上传成功但网站没有更新？
A: 检查以下几点：1) 上传的远程目录是否正确（确认 remote_dir 是网站的根目录）；2) 服务器是否有缓存（如 CDN 或 PHP OPcache），需要手动清除；3) 文件权限是否正确（通常需要 644 或 755）。

Q: 配置文件格式太乱，AI 识别错了怎么办？
A: Skill 会展示识别结果让你确认。如果发现错误，直接告诉 Agent 哪个字段识别错了，它会修正。也可以把配置文件整理成 key=value 格式再重新读取。

Q: 跨对话后凭据失效了？
A: 默认情况下密码不会跨会话保存，每次新会话都需要重新提供密码（或重新读取配置文件）。非秘密信息（host、port、username、远程目录、数据库名）如果当前平台支持持久化记忆则会保留；如果不支持，则所有信息都仅在当前会话有效。重新提供配置文件即可，Skill 会重新解析。说"清除凭据"可以手动重置已保存的非秘密信息。

Q: SQL 文件太大，执行超时怎么办？
A: 对于大型 SQL 文件，建议：1) 拆分文件，分批执行；2) 增加 MySQL 的 max_allowed_packet 和 net_read_timeout 参数；3) 在服务器本地执行而不是远程连接执行。

Q: 配置文件里没写远程目录怎么办？
A: 不指定时默认是 /，也就是 FTP 登录后所在的当前目录（通常是用户主目录或网站根目录，取决于服务器配置）。如果需要上传到特定子目录，在配置文件里加一行如 ftp_path=/www/site/ 即可。

Q: 只想测试连接，不想上传或执行 SQL？
A: 没问题。Skill 分阶段执行，Phase 1-2（读取凭据 + 测试连通性）是只读操作，完全安全。测试完你可以随时停止，不会执行任何写操作。

Q: 我想让 Agent 记住密码，下次免输入？
A: 默认不保存密码。如果你明确同意保存，Agent 会优先使用系统钥匙串（如 macOS Keychain、Windows Credential Manager）；若平台无此能力，则按你确认的方式存入平台记忆。注意：是否本地存储、是否加密、是否同步取决于具体平台，请按平台文档判断风险。

Security Reminders

• Never echo passwords in plain text to the user; always mask with ****
• Never write credentials to project files, logs, or git-tracked files
• Never put passwords on the command line (-p'PASS', ftp://USER:PASS@HOST/, or --user "USER:PASS") — they are visible in process listings (ps), shell history, and audit logs even after variable expansion
• For MySQL, use a temporary --defaults-extra-file with permission 0600 and trap cleanup on EXIT INT TERM
• For FTP, use a temporary curl config file (--config) with permission 0600 and trap cleanup — do NOT use --user on the command line
• On Windows (PowerShell), variable expansion does NOT prevent the password from appearing in child process argv — use a temporary config file with restrictive ACL and finally cleanup
• Prefer SFTP or FTPS over plain FTP (plain FTP transmits credentials and data in cleartext)
• Never log the contents of any temporary credential file (curl config or MySQL defaults file)
• Passwords are NOT persisted by default. Only non-secret metadata is saved.
• Do not claim that the platform's memory is always local, encrypted, or never synced — this is platform-dependent
• Remind users to clear saved credentials when working on shared machines