Add high-demand-low-quality-finder skill

[norightsforlis]

Summary

Adds the high-demand-low-quality-finder skill: Finds products in a category with high demand but a low rating — openings to enter with a better offer.

Lives in skills/high-demand-low-quality-finder/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: a few issues to fix before merge.

• The skill mixes demand units: it gathers monthly demand, ranks by “demand”, shows weekly sales/revenue in the table, and sums monthly demand in cards. Please use one demand unit consistently and expose the sort metric in the table.
• It references new-and-growing-products and uncontested-niche, but those skills are not in this catalog. Please remove those handoffs or add the skills.
• The empty-result suggestion can be wrong when the threshold is already >= 4.5; make it relative to the chosen threshold.
• KISS: the visualization/card/chart/palette section is unsupported presentation complexity for a public Markdown skill. The table + disclaimer are enough.

[profunctor]

Review — high-demand-low-quality-finder

Summary: Given a Mercado Livre (Brasil) category and a user-chosen rating threshold, uses JoomPulse to find active listings that sell well but are rated at/below the threshold — "proven sellers weak on quality" a seller could beat. Markdown product table ranked by demand, optional cards + demand×rating bubble chart, standard disclaimer. Read-only, pt-BR default.

Findings:

• minor — Weekly vs monthly demand inconsistency. Step 2 gathers "estimated monthly demand" and the cards/chart speak of monthly demand, but the table columns are weekly ("Vendas estimadas (semana)" / "Receita estimada (semana)"), and "rank by demand" doesn't say which. The agent could rank on a metric it doesn't display. Pick one cadence or state both columns explicitly.
• minor — Cross-references three skills by informal name ("new-and-growing-products", "uncontested-niche", "single-product analysis"); only the last (= ml-product-analysis) exists. The other two are dangling.
• nit — Internal H1 is "High-Demand, Low-Quality Finder" while siblings prefix with "Mercado Livre …". Cosmetic.
• nit — "category identifier" is referenced but never defined; a seller is unlikely to know a JoomPulse category id. Step 1.2 handles name lookup, so workable but under-specified.

No bugs, secrets, or leaked field/service names; frontmatter, sections, README row, and disclaimer match conventions. Finding #1 is the one worth addressing before merge.