analytics-tracking-automation

Agent Install Guide

Use this guide when you want to install the exported skill bundles into a local agent skills directory.

This is the shared installation path across agent runtimes.

If you are packaging a public marketplace release for ClawHub, do not upload the full repository or the normal installer-oriented bundle set. Export the public bundle instead:

npm run export:skills:clawhub

Publish from dist/clawhub-skill-bundles/<skill-name>. Those bundles keep only the published skill surface (skill docs + references) and omit bundled executable runtime files, telemetry transport, and auto-update runtime.

Before running any event-tracking command from a ClawHub-installed bundle, install the published skill first:

npx skills add jtrackingai/analytics-tracking-automation

This installer path assumes you already cloned this repository locally and are running commands from the repository root.

If you do not want a local checkout, use npx skills add jtrackingai/analytics-tracking-automation on the root skill instead.

From a local checkout:

git clone https://github.com/jtrackingai/analytics-tracking-automation.git
cd analytics-tracking-automation
npm run install:skills

That keeps the default install surface minimal by installing only the umbrella skill into the default install target. You do not need npm ci just to install the exported skill bundles.

If you want the full phase-oriented family installed together:

npm run install:skills -- --with-phases

Use that when your agent runtime benefits from loading the phase skills separately.

If you also want the repo-local CLI and development checks prepared in one pass:

./setup --install-skills --with-phases

Use ./setup only when you also want dependencies, the repo-local CLI, and local development checks.

Default Install Target

Today the installer resolves the default target like this:

If your agent runtime uses a different skills directory, install directly into it:

npm run install:skills -- --target-dir /path/to/agent/skills

To install the full family into a custom directory:

npm run install:skills -- --target-dir /path/to/agent/skills --with-phases

Copy mode is the default:

npm run install:skills

Use this for normal users.

Copy-mode installs are the recommended auto-update path. The installed skill bundle can check the GitHub VERSION file during use and reinstall the same selected bundle set when a newer version is available.

Portable installs such as npx skills add ... on the root skill or manual copies of exported bundles can also self-check for updates as long as the installed directory includes runtime/skill-runtime/. On the first successful self-update, the updater rewrites that portable install into the repo’s normal copy-mode layout.

Link mode keeps the installed skills pointed at dist/skill-bundles/ inside this repository:

npm run install:skills -- --mode link

Use this during local iteration only. After changing skill text or metadata, rerun:

npm run export:skills

The linked install keeps the same target path, so exported bundle refreshes show up without another copy step.

Link mode intentionally does not auto-update from GitHub and is not the recommended end-user install path.

To link the full phase-oriented family during local iteration:

npm run install:skills -- --mode link --with-phases

Common Variants

Install into a custom skills directory:

npm run install:skills -- --target-dir /tmp/agent-skills

Install only selected skills:

npm run install:skills -- --skill analytics-tracking-automation --skill tracking-schema

Install the full skill family explicitly:

npm run install:skills -- --with-phases

Run the full setup and install linked bundles:

./setup --install-skills --mode link --with-phases

Inspect the generated install plan without changing anything:

npm run install:skills -- --dry-run

Updating

If this repo is already cloned locally:

git pull
npm run export:skills

If your installer-managed copy predates the installed auto-update bootstrap, reinstall once first:

npm run install:skills

If you use copy mode, rerun the installer after exporting:

npm run install:skills

If you use link mode, exporting is usually enough because the installed skills already point at dist/skill-bundles/.

After that one-time reinstall, normal copy-mode usage can self-check for updates during skill invocation.

Verification

Default installs should contain:

If you used --with-phases, the installed directory should also contain:

This site is open source. Improve this page.