Add growing-leaf-category-tracker skill

[norightsforlis]

Summary

Adds the growing-leaf-category-tracker skill: Finds the fastest-growing deep sub-categories under a chosen category, ranked by month-over-month revenue growth.

Lives in skills/growing-leaf-category-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: two concerns before merge.

1. This skill routes users to opportunity-index, category-monitor, and new-products, but those skills are not in this catalog, so the installed plugin can promise unavailable handoffs.
2. It says the data prerequisite is only “growth direction” while later requiring numeric growth %, averages, and chart axes, which risks invented precision.

Please either add the missing skills / exact MoM growth contract, or delete the unsupported handoffs and visualization extras.

[profunctor]

Review — growing-leaf-category-tracker

Summary: Takes one Mercado Livre (Brasil) parent category and surfaces deep "leaf" sub-categories (below the 3rd tree level) ranked by month-over-month estimated-revenue growth, to help a seller pick a niche to expand into. Read-only, JoomPulse estimates, pt-BR default, markdown table + optional cards/bubble chart.

Findings:

• major — Cross-references to skills that don't exist (opportunity-index, category-monitor, new-products). Remove or match to actual skill names before merge.
• minor — Underspecified ranking/threshold. The tree-level counting convention (0- vs 1-indexed, where the parent sits) is never pinned down, so "deeper than the third level" is ambiguous. No minimum revenue/sales floor or top-N cap, so a tiny noisy niche with huge % growth can top the ranking — a common MoM pitfall. Add a size floor or list cap.
• minor — Self-contradiction on time: it's framed as "a snapshot, not a tracker over time", yet the core metric is month-over-month growth (inherently a period comparison). Tighten the wording.
• nit — Example table headers are hardcoded pt-BR with no note to translate for an English seller, unlike product-change-monitor ("You may translate the column headers").
• nit — Emoji markers (🟢/⚠️) match product-change-monitor, so consistent with the repo; flagging only for a deliberate confirmation that emoji-in-output is the intended convention.

No credential/path leaks, no write operations; directory name matches name. Only finding #1 is gating.

[profunctor]

Approving. Cross-references all resolve: opportunity-index → #6 (category-opportunity-index), category-monitor → #18, new-products → #8 (new-growing-products-in-category). Prior flags addressed: 'deep sub-category' is now concretely defined as leaf niches deeper than the third level, with a flat-category guardrail; the snapshot-vs-tracker tension is explicitly clarified ('niche-discovery snapshot, not a tracker over time') and time-series use is routed to category-monitor. The change column is correctly kept as a filter rather than a displayed table column.

One minor, non-blocking note for a follow-up: ranking purely on MoM revenue growth with no minimum-size floor lets tiny-base niches dominate (small denominators inflate growth %). The size columns and the size-vs-growth bubble chart mitigate this visually, so it's not blocking — consider a minimum revenue/sales threshold later.