all publishers

guillaumemeyer

@guillaumemeyer source repo

24 published skills

  1. ▌
    Scoring · guillaumemeyer
    Trendy scoring stage (PRD §4.2). Assigns per-dimension scores (velocity/sensitivity/competition/sustainability, each 0–10), the weighted total_score, per-category risk scores (copyright/political/adult/health/ sensitivity), the global risk_score (max of categories), lifecycle, and potential bucket for every reported trend. Run after detection/reporting; weights come from PocketBase settings (settings.scoring.weights).
    1 repo stars
  2. ▌
    X Trends · guillaumemeyer
    X API v2 trends source (PRD §4.1, §6.8). Calls GET /2/trends/by/woeid (default WOEID 1 = worldwide) with Bearer auth from X_API_KEY. Skips gracefully when the key is absent. Capped at 20 trends per run; hashtag-only entries are filtered out.
    1 repo stars
  3. ▌
    Impeccable · guillaumemeyer
    Trendy adapter of memo `design/impeccable` (PRD §10.1). Design critique and polish pass before a store moves to store review: hierarchy, spacing, color contrast, and conversion focus.
    1 repo stars
  4. ▌
    Store Build · guillaumemeyer
    Trendy Build stage (PRD §4.6). Builds the actual storefront deliverables for a store in `building`: final HIGH-DEF assets + print files (correct DPI per Printful specs), final blog posts, SEO/AEO/GEO first pass, GA4 wiring, and a store review package. Advances `building → store_review` on completion.
    1 repo stars
  5. ▌
    Brand Strategy · guillaumemeyer
    Trendy adapter of memo `brand/brand-strategy` (PRD §10.1). Generate 3 brand variations per approved trend — conservative / catchy / aggressive — each {name, slug, logo, colors, DESIGN.md}.
    1 repo stars
  6. ▌
    Creative Chat · guillaumemeyer
    Chat-based refinement for the Strategy approval chat (PRD §4.5 AC3). Proxies operator messages from the back-office dashboard to Hermes /v1/chat/ completions with the trend's full context; interprets refinement requests and triggers stage re-runs (branding, creatives, products, site, blog drafts).
    1 repo stars
  7. ▌
    Store Strategy · guillaumemeyer
    Trendy Strategy Approval stage (PRD §4.5). For each approved trend, generate a preview-only strategy package: 3 brand variants, 6 illustration concepts per variant (LOW-RES previews), Printful product selection with pricing, site preview, and 6 draft blog articles. Nothing is live, no Printful sync, no route. Kicked off by the build-check cron every 15 min.
    1 repo stars
  8. ▌
    Daily SEO Analysis · guillaumemeyer
    Trendy adapter of memo `seo/daily-seo-analysis` (PRD §10.1). Weekly SEO/AEO review per store after live: meta/tags/sitemap/schema health, Search Console data when available, and actionable fixes written back to the store's seo fields.
    1 repo stars
  9. ▌
    Google News Rss · guillaumemeyer
    Key-free Google News RSS source (PRD §4.1, §6.6). Fetches https://news.google.com/rss (hl=en-US&gl=US&ceid=US:en), parses item/entry blocks, and returns signals for clustering. Budget-aware: one feed fetch per run, capped at 25 items.
    1 repo stars
  10. ▌
    Google Analytics · guillaumemeyer
    Trendy adapter of memo `google/google-analytics` (PRD §10.1). GA4 wiring: one shared property, gtag.js on every storefront page, store identity as a custom dimension, and the 8 custom events (PRD §6.3).
    1 repo stars
  11. ▌
    Trendy Detection · guillaumemeyer
    Trendy detection stage (PRD §4.1). Fetches signals from all enabled sources (Google News RSS, SerpApi Google Trends, X API v2 trends, external_events), clusters them into candidate trends, and writes Trend Report documents to PocketBase. Daily cadence via Hermes gateway cron. Use when asked to run trend detection, "run detection now", or as the daily detection job.
    1 repo stars
  12. ▌
    Images Generation · guillaumemeyer
    Trendy adapter of memo `images/images-generation` (PRD §10.1). Generate LOW-RES previews at Strategy and final HIGH-DEF assets + print files at Build, with bounded cost: previews first, HD only after approval.
    1 repo stars
  13. ▌
    Marketing Analysis · guillaumemeyer
    Trendy marketing analysis stage (PRD §4.3). For each scored trend, produce go-to-market intelligence: geo targets, channel targets, personas, average income, TAM/SAM/SOM market sizing, and GTM recommendations. Loads the marketing-strategist agent profile for framing. Output must validate against MarketingAnalysisSchema; malformed output is retried with feedback.
    1 repo stars
  14. ▌
    Trend Reassessment · guillaumemeyer
    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.
    1 repo stars
  15. ▌
    Creative Concepts · guillaumemeyer
    Trendy adapter of memo `creative/creative-concepts` (PRD §10.1). Generate 6 illustration concepts per brand variant (18 per trend at Strategy), each a single dominant motif that keeps the trend legible on a tshirt/mug/tote.
    1 repo stars
  16. ▌
    Media Asset Tagging · guillaumemeyer
    Trendy adapter of memo `medias/media-asset-tagging` (PRD §10.1). Tag every generated asset with store, trend, product-type and usage tags so assets are queryable across stores and stages.
    1 repo stars
  17. ▌
    Aeo Geo Optimization · guillaumemeyer
    Trendy adapter of memo `aeo-geo/aeo-geo-optimization` (PRD §10.1). First AEO/GEO pass at Build: schema markup, structured Q&A content, entity coverage — making store pages answerable by AI assistants and search engines.
    1 repo stars
  18. ▌
    External Events Manager · guillaumemeyer
    Manages the curated external_events collection in PocketBase (PRD §4.1, §5.4) and feeds events as signals. Tier filter: Tier 1/2 for candidate trends, Tier 3 optional. Key-free. Also used to add/update events from the back-office manual entry form.
    1 repo stars
  19. ▌
    Creative Brief Organic · guillaumemeyer
    Trendy adapter of memo `creative/creative-brief-organic` (PRD §10.1). Build the organic-content brief for the blog drafts: angle, audience, SEO target, and CTA that ladder up to the store's products.
    1 repo stars
  20. ▌
    Organic Content Pipeline · guillaumemeyer
    Trendy adapter of memo `content/organic-content-pipeline` (PRD §10.1). End-to-end organic blog content: 6 drafts at Strategy → final at Build → publish 3/week after live, each with SEO/AEO/GEO meta and an Unsplash illustration.
    1 repo stars
  21. ▌
    Creative Image Tech Specs · guillaumemeyer
    Trendy adapter of memo `creative/creative-image-tech-specs` (PRD §10.1). Printful production specs for generated assets: DPI, file format, size and safe-zone rules per product type (tshirt/mug/tote), used by the Build stage when finalizing HIGH-DEF assets + print files (PRD §4.6 AC2).
    1 repo stars
  22. ▌
    Creative Image Art Direction · guillaumemeyer
    Trendy adapter of memo `creative/creative-image-art-direction` (PRD §10.1). Art-direct the image prompts for each concept: composition, color, lighting, and mood boards consistent with the selected brand variant's DESIGN.md.
    1 repo stars
  23. ▌
    Remove AI Marks · guillaumemeyer bundle
    Remove multi-vendor AI provenance marks: invisible Unicode (Layer A), statistical text watermarks via rewrite (Layer B, always offer), and C2PA/EXIF/XMP/container metadata on PNG/JPEG/WebP/SVG/PDF/DOCX/ODT/HTML/MD/TEX. Covers Claude, Gemini/SynthID-class, OpenAI provenance, and open-LLM sampling marks. Use when the user asks to strip watermarks, remove C2PA/Content Credentials, clean AI metadata, remove invisible Unicode, anti-detect clean AI output, or runs /remove-ai-marks (aliases: /remove-claude-marks).
    1 repo stars
  24. ▌
    Clean User Facing Text · guillaumemeyer bundle
    Clean and finalize authorized natural-language text intended for readers by auditing suspicious invisible Unicode and rewriting prose while preserving facts, meaning, and the writer's voice. Use when the user asks to clean, humanize, polish, or finalize articles, manuscripts, reports, documentation, emails, product copy, UI text, Markdown, or HTML prose, or when a project rule or instruction file explicitly requires this workflow. Don't use for code-only tasks or undisclosed authorship evasion; leave code, commands, identifiers, paths, APIs, formulas, citations, required disclosures, and verbatim quotations unchanged.
    1 repo stars