thesmokedev/geo-skills/tokenmax-fleet-orchestrator

Claude Code and agent skill by thesmokedev/geo-skills

Trust tier 3
  • community
  • ext:[{"type":"hook","description":"Pre/post lifecycle hooks"}]
Source check pending

Checking that the SKILL.md file is still in the repository.

Run multiple TokenMax SEO/GEO sites as a resumable, fail-closed fleet. Use when Codex needs to audit a site queue, execute one isolated site at a time, preserve deterministic quality/build/deploy gates, resume interrupted runs, install a server-side scheduler, or report production and indexing state without hard-coding one website into the controller.

Install

npx vskill@latest install thesmokedev/geo-skills/tokenmax-fleet-orchestrator

Semi-extensibleMentions customization, but needs skill-specific knowledge. Read the extensible skills standard

SKILL.md

The same SKILL.md was published earlier as thesmokedev/geo-skills/tokenmax-fleet-orchestrator.

TokenMax Fleet Orchestrator

Use this skill above tokenmax-site-factory. The site factory discovers and generates one site; this skill sequences many sites and records what actually passed, shipped, and reached production.

Start

  1. Read the target repo's deploy manual and its existing TokenMax/fleet files.
  2. Inspect active processes, worktrees, schedules, disk, and available memory.
  3. Read references/stage-contract.md and validate the fleet YAML against

references/fleet-config.schema.json.

  1. Run a dry plan before any mutation:
bash
python scripts/fleet_controller.py --config /path/to/fleet.yaml validate-config
python scripts/fleet_controller.py --config /path/to/fleet.yaml init
python scripts/fleet_controller.py --config /path/to/fleet.yaml run-next --dry-run
  1. Forward-test one unproven site through production before installing a

recurring timer.

Controller

The controller is generic. Fleet-specific behavior belongs in YAML stage commands and a versioned repo driver. Commands receive site/stage context via environment variables and write an optional JSON stage result.

bash
python scripts/fleet_controller.py --config /path/to/fleet.yaml status
python scripts/fleet_controller.py --config /path/to/fleet.yaml run-next --max-sites 1
python scripts/fleet_controller.py --config /path/to/fleet.yaml resume --site <id>
python scripts/fleet_controller.py --config /path/to/fleet.yaml retry --site <id>
python scripts/fleet_controller.py --config /path/to/fleet.yaml pause
python scripts/fleet_controller.py --config /path/to/fleet.yaml index-queue

Required Gates

  • One clean, isolated worktree per site.
  • Scan/profile confidence before content writes.
  • A small rendered pilot before the full batch.
  • Per-page and full-batch word, uniqueness, fact, structure, and prohibited

claim validation.

  • Exact app build before any commit or deploy.
  • Rendered HTTP, canonical, JSON-LD, internal-link, text/HTML, robots, and

sitemap validation.

  • Scoped staging and the target platform's required commit identity.
  • Merge current remote base and rerun affected gates before pushing.
  • Production content and sitemap proof after deploy.

Pre-deploy quality failures may block one site while leaving the remaining queue eligible. Any uncertain post-push or live-production state freezes the fleet. Search Console quota exhaustion defers indexing and never weakens the build or production gates.

Indexing Boundary

Automate sitemap submission when an authorized Search Console write client is available. For ordinary pages, create a ranked top-URL queue for a persistent browser worker; do not misuse Google's restricted Indexing API. Browser quota, authentication, or UI drift is a deferred operation, not proof that a deploy failed.

Scheduling

Use the bundled systemd templates only after the canary passes. Keep one site per invocation by default, retain the process lock, and inspect existing timers before installation. A monitor may report status from another machine, but generation and builds remain on the configured server.

Rules

  • Never place secrets in fleet YAML, command arguments, logs, or state JSON.
  • Do not deploy from the generation skill; shipping is a separate stage here.
  • Retries are for transient failures. Quality failures retain evidence and

stop after their configured rewrite budget.

  • Do not trust stale completion lists. Reconcile repo artifacts, live routes,

sitemap state, and deployment evidence.

  • Do not claim rankings, indexing, or production state from a successful local

build.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
25
Repository forks
6
7-day trend score
16

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Extension points

  • hookPre/post lifecycle hooks

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/thesmokedev/geo-skills/tokenmax-fleet-orchestrator/badge)](https://verified-skill.com/skills/thesmokedev/geo-skills/tokenmax-fleet-orchestrator)

Something wrong with this skill or its page? Tell us.