How do I install the Trend Reassessment skill?

Run npx skillmds@latest add guillaumemeyer/trend-reassessment in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Trend Reassessment safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Trend Reassessment?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Trend Reassessment free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Trend Reassessment?

guillaumemeyer (@guillaumemeyer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Trend Reassessment by guillaumemeyer

Name: Trend Reassessment
Author: guillaumemeyer

Trend Reassessment

Weekly trend reassessment (PRD §4.10.1). For each LIVE store, re-evaluate the trend behind it on current data (signals + GA4 + orders KPIs), re-score dimensions/risk/lifecycle, and write a SUGGEST-ONLY refresh proposal (refresh_proposals). Nothing on a live store changes until the operator approves a proposal.

File contents

Trend Reassessment (weekly)

Role

Every week, for each store in status live (or paused), re-check whether the trend still holds and propose updates. Suggest-only: writing a proposal never mutates the live store.

Flow (per store)

Pull the store's trend + current state (branding, products, blog, KPIs: GA4 events, orders, customers).
Re-check signals on current data (SerpApi / Google News / X / external events + GA4 + Search Console + orders): re-score the four dimensions, total_score, lifecycle, and per-category risks (reuse the scoring skill rules).
Write a refresh proposal (refresh_proposals, status proposed):
- trend_evolution summary (what changed vs original report).
- Suggestions: brand copy/visual tweaks, store page updates, blog topics, product additions/retirements, new products and new concept+SKU combinations — each new concept includes a LOW-RES preview (image gen, bounded cost); final HD assets only after approval.
If the trend has declined sharply or the store's KPIs are flat/bad, say so explicitly in the proposal and recommend retirement or pause — still suggest-only.

Persist

One refresh_proposals record per store per cycle (idempotent on store+week).
One agent_runs row: {stage: "analyze", status: "ok", summary, metadata: {proposal_id}}.

Operator actions (back-office, not you)

Approve → proposal applied (build-check picks it up).
Dismiss → proposal archived, store untouched.

Completion contract (final output)

skill: trend-reassessment
status: ok|partial|failed
stores_reassessed: N
proposals: N
agent_run_id: <pb_id>

---name: trend-reassessmentdescription: Weekly trend reassessment (PRD §4.10.1). For each LIVE store, re-evaluate the trend behind it on current data (signals + GA4 + orders KPIs), re-score dimensions/risk/lifecycle, and write a SUGGEST-ONLY refresh proposal (refresh_proposals). Nothing on a live store changes until the operator approves a proposal.---# Trend Reassessment (weekly)## RoleEvery week, for each store in status `live` (or `paused`), re-check whether thetrend still holds and propose updates. **Suggest-only**: writing a proposalnever mutates the live store.## Flow (per store)1. Pull the store's trend + current state (branding, products, blog, KPIs: GA4 events, orders, customers).2. Re-check signals on current data (SerpApi / Google News / X / external events + GA4 + Search Console + orders): re-score the four dimensions, `total_score`, lifecycle, and per-category risks (reuse the `scoring` skill rules).3. Write a **refresh proposal** (`refresh_proposals`, status `proposed`): - `trend_evolution` summary (what changed vs original report). - Suggestions: brand copy/visual tweaks, store page updates, blog topics, product additions/retirements, **new products** and **new concept+SKU combinations** — each new concept includes a LOW-RES preview (image gen, bounded cost); final HD assets only after approval.4. If the trend has declined sharply or the store's KPIs are flat/bad, say so explicitly in the proposal and recommend retirement or pause — still suggest-only.## Persist- One `refresh_proposals` record per store per cycle (idempotent on store+week).- One `agent_runs` row: `{stage: "analyze", status: "ok", summary, metadata: {proposal_id}}`.## Operator actions (back-office, not you)- **Approve** → proposal applied (build-check picks it up).- **Dismiss** → proposal archived, store untouched.## Completion contract (final output)```textskill: trend-reassessmentstatus: ok|partial|failedstores_reassessed: Nproposals: Nagent_run_id: <pb_id>```

Frequently asked questions