macOS install prompt
Install Curly Harness on my macOS machine from `https://curly.ng`. You are operating on my local machine, so treat this as a cautious install. Do not assume I have developer tooling installed. Do not require Node.js, Python, Git, Homebrew, npm, pnpm, jq, or any project-specific CLI. ## Goal Install the Harness-managed skills library into my shared agent directory so Claude and Codex can use the same curated skills, concepts, knowledge references, scripts, and local ownership ledger. ## First, inspect before running 1. Read the installer source from `https://curly.ng/api/harness/skills/install.sh`. 2. Summarize what the script does in plain language. 3. Confirm it uses only common macOS shell tools such as `bash`, `curl`, `mkdir`, `ln`, `mktemp`, `mv`, `rm`, and `shasum`. 4. Confirm it performs SHA-256 verification before trusting downloaded content. 5. Confirm where it will install Harness-managed files, normally under `~/.agents/skills`. 6. Confirm whether it creates symlinks or pointers for Claude and Codex, and where those paths are. 7. Confirm whether it keeps a local ledger of Harness-owned files so future updates only touch Harness-owned files. 8. Point out anything surprising, unsafe, unclear, or destructive before running any command. ## Then run dry-run only Run the installer in dry-run mode first: ```bash curl -fsSL https://curly.ng/api/harness/skills/install.sh | bash -s -- --dry-run ``` Do not apply changes yet. ## Explain the dry-run result After the dry run, explain: 1. Which directories will be created. 2. Which files will be added. 3. Which files will be updated. 4. Which Harness-owned files will be removed. 5. Which existing files would be backed up. 6. Which files are outside Harness ownership and will not be touched. 7. Where the Harness ledger will live. 8. How Claude will discover the shared skills directory. 9. How Codex will discover the shared skills directory. 10. What rollback or backup path exists if something looks wrong. ## Ask before applying After explaining the dry run, stop and ask me for confirmation before applying changes. If I approve, run the real install command recommended by the installer. If I do not approve, do not modify files. ## After install If I approve and the install succeeds: 1. Summarize exactly what changed. 2. Show the final Harness skills directory path. 3. Confirm the ownership ledger exists. 4. Confirm Claude and Codex integration paths were created or updated. 5. Tell me any warnings or manual follow-up steps. Keep the explanation direct and practical. Do not hide command output if it contains warnings.
