Add seller-overview-tracker skill

[norightsforlis]

Summary

Adds the seller-overview-tracker skill: Weekly snapshot tracker for one Mercado Livre seller, reporting what changed since last week (revenue, sales, listings, reputation, medal, cancellation rate).

Lives in skills/seller-overview-tracker/SKILL.md and is registered in the README skills table. Public behavior and user-visible workflow only — no internal service names, schema, or implementation details.

Public-Safety Checklist

• No credentials, tokens, keys, or secrets.
• No internal filesystem paths.
• No private Slack, Jira, Notion, admin, or service URLs.
• No private service names or implementation details.
• No customer data or private product data.
• Skill directory name matches SKILL.md frontmatter name.

🤖 Generated with Claude Code

[profunctor]

KISS review: this needs tightening before merge.

The skill currently promises setup/future weekly monitoring and reading previous runs, but a public skill has no persistence or scheduler, so it can falsely tell users monitoring has begun. Please scope it to “compare against a prior baseline when provided” or add a real storage/automation mechanism.

Also remove handoffs to category seller-ranking/top-100 skills unless those ship in this plugin, and collapse the output to one markdown-table contract; the card/chart section is unsupported and duplicates the Output section.

[profunctor]

Review — seller-overview-tracker

Summary: A weekly per-seller snapshot tracker for one Mercado Livre (Brasil) seller (fixed at setup by store link / seller ID). Each run pulls a JoomPulse snapshot (revenue, sales, listings, reputation, medal, cancellation rate, categories), compares against the previous run's recorded table using explicit thresholds, and re-emits the full table as the next baseline. pt-BR default, surface-aware (cards + trend line where supported), with the estimates disclaimer. Read-only.

Findings:

• major — Cross-referenced sibling skills don't exist. The description/body point to a "category seller-ranking skill", a "category top-100 change-tracker skill", and a "single-product analysis skill". The single-product one should map to ml-product-analysis; the two category skills have no counterpart on main. Rename to existing skills or drop the references.
• major — Baseline mechanism diverges from repo convention and is fragile. product-change-monitor derives its week-ago baseline from JoomPulse's own history; this skill asserts seller snapshots have no built-in history and must rebuild the baseline from "the previous run's recorded table" read out of prior chat output — even though "each run is its own chat." Please verify seller-level history really is unavailable via JoomPulse, and clarify how the baseline persists across sessions.
• minor — Tooling is described abstractly ("Use JoomPulse to pull the current snapshot") with no concrete field mapping for "sales trend", "rolling 60/365-day sales", etc. Acceptable as a style choice but leaves field resolution to the agent.
• nit — Frontmatter/structure/naming consistent (name == directory, folded description with EN+pt-BR triggers); README row matches.

Read-only by design; no credentials, paths, or internal URLs. Findings #1 and #2 are worth resolving before merge.