all publishers

rebelytics

@rebelytics source repo

5 published skills

  1. ▌
    Pagination Independence Architecture · rebelytics bundle
    Design category and listing architecture so that a site's indexable value does not depend on paginated pages, using demand-backed indexable subcategories as the alternative to deep pagination. Load this skill when the user asks whether to noindex, canonicalise, block or prune paginated URLs (`?page=`, `?p=`, `/page/2/`); when they mention pagination handling, page-2+ indexation, infinite scroll and crawlability, orphaned product or article pages, "products only reachable from page 7", crawl budget wasted on listing pages, thin or duplicate category pages, faceted navigation index bloat, or splitting a large category into subcategories. Also load for "how do we cut paginated URLs without losing products" and listing-page taxonomy redesign for large catalogues. Applies to e-commerce catalogues, editorial archives and directories.
    0 installs
  2. ▌
    Peec AI Tracking Strategy Builder · rebelytics bundle
    Peec AI companion to the platform-agnostic `ai-visibility-tracking-strategy-builder` skill — build or refine a Peec AI tracking strategy as an iterative workflow (Intake → Strategy → Write → Analyse, plus an optional stakeholder presentation), with this skill holding everything Peec-specific: MCP reads and gaps, brand/topic/tag fields, plan-tier engine gating, write waves and verification, Analyse recipes over Peec reports. Load whenever the user mentions Peec setup, Peec onboarding, "what should we track in Peec", Peec prompt rationalisation, or Peec rebuild; also on Phase B / retrospective requests about an existing Peec strategy ("explain our Peec setup", "document our tracking strategy"). Requires the core skill `ai-visibility-tracking-strategy-builder` loaded alongside; companion to `peec-ai-mcp` (recommended; tool mechanics).
    0 installs
  3. ▌
    AI Visibility Tracking Strategy Builder · rebelytics bundle
    Build or refine an AI visibility tracking strategy — the prompt set, grouping structure, brand roster and reporting split that measure how a brand appears in ChatGPT, Gemini, Perplexity, AI Overviews and similar — on any AI visibility monitoring platform. Runs as an iterative loop (Intake → Strategy → Write → Analyse) with an optional stakeholder presentation. Load whenever the user mentions AI visibility, GEO (generative engine optimisation), AI brand monitoring, prompt tracking, "what prompts should we track", "how are we showing up in ChatGPT / Gemini / Perplexity", AI mention tracking, a prompt set for an AI monitoring tool, or a tracking strategy review. This is the platform-agnostic core of a skill family: load it together with the companion for the platform in use (Peec AI: `peec-ai-tracking-strategy-builder`; SISTRIX: `sistrix-tracking-strategy-builder`; searchVIU: `searchviu-tracking-strategy-builder`; LLM Pulse: `llmpulse-tracking-strategy-builder`), or alone for any other tool.
    0 installs
  4. ▌
    Peec AI MCP · rebelytics bundle
    Companion skill for the Peec AI MCP server (https://api.peec.ai/mcp). Load when the user does Peec reporting, analysis, or multi-step work — visibility reports, per-engine comparisons, competitive gap analysis, source-authority audits, project tune-ups (brands, prompts, topics, tags), or Peec slash commands (`peec_weekly_pulse`, `peec_competitor_radar`, `peec_engine_scorecard`, `peec_topic_heatmap`, `peec_prompt_grader`, `peec_source_authority`, `peec_campaign_tracker`). Also load for Peec data interpretation (sentiment, position, visibility, share of voice, retrieval vs citation, `get_actions` two-step workflow, `list_prompts.volume` ordinals, `get_url_content` 5-day refresh cadence) or when combining two or more Peec tools. Skip for trivial single-tool lookups like `list_projects`, `list_brands`, `list_topics` where Peec's own tool descriptions suffice. Teaches agents the real behaviour of the Peec MCP, including gotchas the official docs omit or get wrong.
    8 installs
  5. ▌
    Task Observer · rebelytics bundle
    > Monitors task execution for skill improvement opportunities. Use this skill during ANY multi-step task, agentic workflow, or substantive work session where the agent is using tools and producing deliverables. It captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable skills. Also triggers during post-task feedback discussions and when the user explicitly mentions skill observations, improvements, the observation log, skill taxonomy, or asks the agent to watch for skill opportunities. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: this skill should be invoked at the start of every task-oriented session — if you are about to use tools to produce deliverables, invoke this skill first. For reliable activation, pair this description with a CLAUDE.md instruction or harness-level session-start hook (see...
    7 installs