jpgz-dl

name	jpgz-dl
description	Use when OpenClaw or another model-driven agent needs to work on this repository, start the local Amazon competitor dashboard, test Sorftime or SellerSprite MCP connectivity, inspect snapshot or analysis behavior, or update the monitoring UI without introducing secrets or browser-local cache into the repo.

Amazon Competitor Monitor OpenClaw Skill

This is a repository-local skill for operating and maintaining the Amazon competitor monitoring dashboard in the current workspace.

Use this skill when the task involves:

• Starting or verifying the local dashboard server
• Testing Sorftime or SellerSprite MCP connectivity
• Inspecting snapshot capture, saved browser state, or analysis flow
• Updating the monitoring UI, server proxy, or export behavior
• Investigating data gaps such as price, bullets, ratings, or review count fields

Project entrypoints

The main project files are:

• index.html
• styles.css
• script.js
• server.js
• package.json

The local app runs with:

npm start

Default local URL:

http://127.0.0.1:5200

OpenClaw prompt template

Use this template when asking OpenClaw to work on this repository:

Use the jpgz-dl skill for this repository.

1. Start the local dashboard with the repo-local script.
2. Verify /api/health before making changes.
3. Work only inside this repository.
4. Treat browser localStorage and encrypted local config as runtime-only data, not repository data.
5. Never commit real MCP keys, API keys, passwords, account data, or browser cache.
6. If Sorftime or SellerSprite fields are missing, report them as “没有返回” unless a verified fallback is explicitly implemented.
7. Report changed files, local verification results, and any MCP/data-source limitations at the end.

Short version:

Use the jpgz-dl skill. Start the local dashboard, verify /api/health, keep secrets and browser-local data out of the repo, then inspect or update the monitoring workflow and report verification results.

Recommended workflow

1. Choose the platform-specific startup script:
   • Windows: scripts/start_local_server_windows.bat
   • macOS: scripts/start_local_server_macos.sh
   • Ubuntu: scripts/start_local_server_ubuntu.sh
   • Generic fallback: scripts/start_local_server.sh These scripts now start the local app through a guarded supervisor that auto-restarts the Node server if it exits unexpectedly or repeatedly fails health checks. If the user needs the dashboard to stay available in the background after terminals close, use the platform install scripts:
   • Windows: scripts/install_background_service_windows.ps1
   • macOS: scripts/install_background_service_macos.sh
   • Ubuntu: scripts/install_background_service_ubuntu.sh
2. Run scripts/healthcheck.sh.
3. Inspect the relevant UI or API flow.
4. Make the requested change in this repository only.
5. Re-run syntax checks or health checks after edits.

Data-source notes

• Sorftime connectivity is usually stable, but field completeness can vary by ASIN.
• Sorftime may omit long-form listing fields such as bullets or product description for some ASINs.
• SellerSprite tends to return more structured listing fields, but availability may be limited by remaining usage.
• MCP-returned price may not always match the current Amazon front-end price. Do not silently treat it as authoritative if the source differs.

Read the reference files when needed:

• For repository structure and runtime behavior: references/project-map.md
• For safety and secret-handling rules: references/safety-and-secrets.md
• For Windows startup, dependency, and environment notes: references/windows.md
• For macOS startup, dependency, and environment notes: references/macos.md
• For Ubuntu startup, dependency, and environment notes: references/ubuntu.md

Validation checklist

• The server starts with npm start.
• The guarded entry npm run start:guarded keeps the local service alive by restarting it after abnormal exit or repeated health failure.
• The background install scripts register the guarded entry with the local operating system so the dashboard can survive terminal closure and restart automatically after login.
• http://127.0.0.1:5200/api/health returns ok: true.
• The dashboard loads.
• MCP testing still uses the local proxy in server.js.
• No real keys, passwords, account identifiers, or browser cache files are added to the repository.

Platform notes

• All three platforms need Node.js and npm available in PATH.
• The server entry is still npm start, which runs node server.js.
• Browser-local dashboard data stays in the browser runtime and must not be treated as repository data.
• Platform-specific setup belongs in the matching reference file instead of being guessed ad hoc.