profit-autopilot
Run a fact-checked monetization pipeline that upgrades the landing page, builds Shopify launch assets, validates storefront/admin state, and optionally publishes products live with evidence reports. Use when the user asks for money progress, product launch automation, website-to-store pipelines, or end-to-end sell-from-terminal execution.
Best use case
profit-autopilot is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run a fact-checked monetization pipeline that upgrades the landing page, builds Shopify launch assets, validates storefront/admin state, and optionally publishes products live with evidence reports. Use when the user asks for money progress, product launch automation, website-to-store pipelines, or end-to-end sell-from-terminal execution.
Teams using profit-autopilot should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/profit-autopilot/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How profit-autopilot Compares
| Feature / Agent | profit-autopilot | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run a fact-checked monetization pipeline that upgrades the landing page, builds Shopify launch assets, validates storefront/admin state, and optionally publishes products live with evidence reports. Use when the user asks for money progress, product launch automation, website-to-store pipelines, or end-to-end sell-from-terminal execution.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Profit Autopilot ## Overview Use this skill when the goal is measurable monetization progress from terminal, not brainstorming. It enforces a fact gate first, then runs launch automation, then outputs artifact reports with blockers. ## When To Trigger Trigger this skill when requests include: - "make money", "ship products", "post to Shopify", "launch offers" - "automate full flow" from website to checkout delivery - "progress now" where the expected output is a run report and concrete next action Do not use this skill for pure narrative writing or non-monetization coding. ## Workflow 1. Run fact gate before live publish: - Required files exist (`product-landing.html`, `scripts/system/shopify_store_launch_pack.py`, `scripts/shopify_bridge.py`). - Landing page contains conversion sections and store links. 2. Run launch pack: - Generate product media + scoring report. - Run Shopify both-side smoke test (admin + storefront status). 3. Optional live publish: - Only when tokens are available and user wants live sync. 4. Emit evidence: - Save JSON + markdown report under `artifacts/profit-autopilot/<timestamp>/`. - Surface blockers explicitly (for example missing token, storefront password gate). ## Commands From repo root: ```powershell pwsh -ExecutionPolicy Bypass -File scripts/system/run_profit_autopilot.ps1 ``` Live publish attempt: ```powershell pwsh -ExecutionPolicy Bypass -File scripts/system/run_profit_autopilot.ps1 -PublishLive ``` Direct Python mode: ```powershell python scripts/system/profit_autopilot.py --publish-live ``` ## Resource Usage - Script runner: `scripts/run_profit_autopilot.ps1` - Repo pipeline: `C:/Users/issda/SCBE-AETHERMOORE/scripts/system/profit_autopilot.py` - Launch pack dependency: `C:/Users/issda/SCBE-AETHERMOORE/scripts/system/shopify_store_launch_pack.py` ## Execution Rules - Prefer dry-run/fact gate first when environment is uncertain. - Never claim publish success without reading generated report JSON. - If live sync fails, return exact blocker and the one command needed next. - Keep runs deterministic and artifact-backed.
Related Skills
scbe-research-publishing-autopilot
Build and operate multi-hour SCBE research-to-publishing loops for articles and social posts with retrigger logic, evidence gates, and performance monitoring. Use when repeatable growth execution must stay lore/code accurate and avoid invention misrepresentation.
scbe-admin-autopilot
Operate SCBE in admin mode through the Issac Command Center, watchdog loops, service launchers, cross-talk relay commands, and verified storage or sync runs. Use when the user asks for always-on agent workflows, command-center automation, repo or system health checks, backup or prune lanes, service bootstrapping, or admin-level orchestration.
scbe-revenue-autopilot
One-command revenue automation — check Stripe balance, npm/PyPI downloads, post articles to all platforms, run sell pipeline, generate daily revenue reports. Use when the user says "revenue", "money check", "daily report", "post everywhere", "sell", or "how are we doing financially".
scbe-training-pair-authoring
Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.
scbe-spin-conversation-engine
Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.
scbe-research-training-bridge
Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.
scbe-document-management
Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.
scbe-colab-bridge
Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.
scbe-claim-to-code-evidence
Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.
scbe-autonomous-worker-productizer
Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.
multi-agent-cloud-offload
Deterministically sort, bundle, verify, and offshore local files through multiple AI/model lanes while capturing training rows and method evidence. Use when Codex needs to inventory folders, batch-process files, upload them to cloud targets such as rclone-backed Google Drive, Hugging Face, or GitHub, and only delete sources after the configured number of verified targets succeed.
long-form-work-orchestrator
Run long-form engineering work in checkpointed phases with deterministic artifacts, resilience handling, and end-of-run reliability reporting.