Search Optimizer

Search Optimizer

One invocation for "optimize for SEO / AI-bot search / app-store search". This skill does no auditing of its own: it detects the target type; evidence is captured once, the live scan runs at most once, overlapping checks are skipped where the member supports skip-checks, and remaining overlaps are merged into one row per defect in one prioritized report. It is audit-first: every write happens inside a member's own approval gate. This file stays short to protect the context budget; load references/ files only at the phase that names them.

Members

Matrix, fallback cases and per-member skip-checks: references/check-ownership.md.

Detect the target

Prerequisites

• A target: URL, repo path, or store listing. Ask when none is given.
• curl and python3 for web intake.
• Output dir: user-supplied, else ${TMPDIR:-/tmp}/search-optimizer/<slug>-<UTC stamp>/ — outside the checkout, so the orchestrator itself never writes into the repo.

Dependency Preflight (mandatory)

This skill invokes the four members declared in frontmatter dependencies. Run this once, in Phase 1 after branch detection and before intake:

if command -v asm >/dev/null && asm deps --help >/dev/null 2>&1; then
  asm deps discover search-optimizer --json || echo "discover failed; acquire still runs" >&2
  echo "so_mode=lease"
else
  echo "asm deps unavailable: npm install -g agent-skill-manager@latest" >&2
  echo "so_mode=installed"
fi
printf 'so_session=%s\n' "search-optimizer-$(date +%s)-$$"   # record it; reuse it verbatim

1. Check only the members of the detected branch: web → seo-ai-optimizer, viral-product-evaluator, and website-agent-readiness when the target has a public URL; store → aso-marketing, viral-product-evaluator; both → the union. Never acquire a member whose branch the run does not reach.
2. With so_mode=lease, run asm deps acquire <member> --session <so_session> --json for each member from step 1. Record each returned skillMdPath and read that file directly.
3. With so_mode=installed, test each member from step 1 with test -f "$HOME/.claude/skills/<member>/SKILL.md" || test -f "$HOME/.agents/skills/<member>/SKILL.md", falling back to asm list -p claude --json | grep '"<member>"', because same-repo skills can be installed without the registry knowing the bare name. Record the path that exists.
4. seo-ai-optimizer (web) and aso-marketing (store) are required for their branch. If one fails step 2 or 3, print Missing skill: <member> — install: asm install github:luongnv89/skills:skills/<member> -p claude --yes and stop before intake; write nothing. In a "both" run, offer to rerun with only the branch whose required member is installed.
5. website-agent-readiness and viral-product-evaluator are optional: a miss is fail-soft. Skip the member, fall back per references/check-ownership.md, and list its checks under "Not covered" with the install line.
6. Release in finally. If any acquire ran, run asm deps release --session <so_session> --json once at every terminal outcome, stops included, before the Final response. List a failed release under Uncertainty:.

Never substitute one member for another or hand-run a member's workflow inline. Members run their own preflights for their own dependencies (seo-ai-optimizer checks website-agent-readiness for its Step 8); this preflight covers only what search-optimizer invokes directly.

Repo Sync Before Edits (mandatory)

The orchestrator writes only to the output dir. Members that write into a git repo (seo-ai-optimizer Step 6, aso-marketing Phase 4) — or an output dir the user placed in a repo — sync first:

git remote get-url origin >/dev/null || { echo "No origin remote — stop and ask" >&2; exit 1; }
branch="$(git rev-parse --abbrev-ref HEAD)"
stashed=0
if [ -n "$(git status --porcelain)" ]; then
  git stash push -u -m "pre-search-optimizer" || { echo "Stash failed — stop and ask" >&2; exit 1; }
  stashed=1
fi
git fetch origin && git pull --rebase origin "$branch" || {
  echo "Sync failed — stop and ask (stashed=$stashed: changes are in the pre-search-optimizer stash)" >&2; exit 1; }
if [ "$stashed" = 1 ]; then
  git stash pop || { echo "Stash pop conflict — stop and ask" >&2; exit 1; }
fi

On any stop and ask line, stop before the member writes and ask the user; never resolve the conflict or drop the stash yourself. If the user ends the run there, close with the Final response. Members still run their own Repo Sync; never skip theirs because this one ran.

Workflow

Phase 1 — Scope & preflight

Detect the branch, resolve the output dir, run the Dependency Preflight, and confirm scope in one line.

Phase 2 — Intake once (web branch)

Follow references/intake.md: capture page.html, head.json, robots.txt, sitemap.xml, llms.txt into <output>/evidence/ and write manifest.json with a provisional owners map. The store branch has no web intake; record the store metadata paths found in the manifest.

Phase 3 — Web audit

Pass each member the orchestrated-run block (references/check-ownership.md):

1. website-agent-readiness (public URL only), with evidence-dir and output-dir. Its G1 asks the user before sending the URL to isitagentready.com. After it returns, check evidence/agent-readiness/scan.json exists for the same URL and finalize owners (case A, B or C).
2. seo-ai-optimizer with skip-checks from the case; it always keeps crawler-access (audit and fix of AI-bot directives). In case A its Step 8 records the reused scan.json as REUSED and does not invoke website-agent-readiness again. In B/C pass agent-readiness-scan so Step 8 does not repeat a declined or failed scan; if seo-ai-optimizer still offers the Step 8 handoff, remind the user of their G1 decision and let them answer. Its Step 5 plan approval and Step 6 diff approval stay in force (a URL-only run applies nothing; fixes are listed as "needs source repo").
3. viral-product-evaluator with skip-checks: meta-tags.

Phase 4 — Store audit

Invoke aso-marketing normally (no orchestrated block — it is not a contract member). Its post-Phase-3 plan approval gate is kept; nothing is written to store metadata before the user approves. It takes no output-dir, so save its Phase 7 Summary Report (or the latest phase report, if it stopped earlier) and its Final Report into <output>/reports/aso-marketing/summary.md. In a store-only run, invoke viral-product-evaluator here with output-dir (no evidence dir); in a "both" run it already ran in Phase 3 — do not run it again.