Agent Skills › Shape-Machine/tusk-macos › tusk-make-run

tusk-make-run

GitHub

在 Tusk 项目中执行 make run 构建并启动应用，捕获输出。若成功则报告；若失败，分析编译、链接或签名等错误根因，提供错误摘要和修复建议，不进行自动修复。

.claude/skills/tusk-make-run/SKILL.md Shape-Machine/tusk-macos

Trigger Scenarios

需要构建并启动 Tusk 应用时 make run 命令执行失败需诊断错误时

Install

npx skills add Shape-Machine/tusk-macos --skill tusk-make-run -g -y

More Options

Non-standard path

npx skills add https://github.com/Shape-Machine/tusk-macos/tree/main/.claude/skills/tusk-make-run -g -y

Use without installing

npx skills use Shape-Machine/tusk-macos@tusk-make-run

指定 Agent (Claude Code)

npx skills add Shape-Machine/tusk-macos --skill tusk-make-run -a claude-code -g -y

安装 repo 全部 skill

npx skills add Shape-Machine/tusk-macos --all -g -y

预览 repo 内 skill

npx skills add Shape-Machine/tusk-macos --list

SKILL.md

Frontmatter

{
    "name": "tusk-make-run",
    "description": "Run `make run` on the Tusk project (builds then launches the app) and diagnose any errors",
    "allowed-tools": "Bash, Read, Grep",
    "disable-model-invocation": false
}

Tusk Make Run

Run make run to build and launch the Tusk app. This will kill any running Tusk instance, build the project, and open the freshly built app.

Steps

1. Run

make run

Capture the full output.

2. Evaluate result

If the command succeeds (** BUILD SUCCEEDED ** appears and the app opens):

Report success concisely. No further action needed.

If the command fails or produces errors:

Read the error output carefully.
Identify the root cause. Common failure categories for this project:
- Compile errors — Swift/ObjC syntax or type errors; pinpoint the file and line.
- Linker errors — missing frameworks or libraries.
- Code signing / provisioning — expired certificate, missing entitlement.
- Missing generated files — project.yml out of sync; xcodegen generate may be needed first.
- xcodebuild not found — Xcode not installed or xcode-select not pointing to the right path.
- App launch failure — built OK but open failed (wrong APP path, sandbox issue).
Present the user with:
1. A clear one-line summary of what went wrong.
2. The specific error line(s) from the output (file path and line number if available).
3. Concrete recommended actions to resolve it.
Do NOT attempt to auto-fix — just diagnose and recommend.