cc-content-performance-reviewlisted

Use this skill to analyze how one or more published content pieces performed and generate concrete iteration variants for the next piece. Invoke when the user says "review how this post performed", "analyze content performance", "what worked in these posts", "help me iterate on this based on the numbers", or pastes performance data (impressions, engagement rate, CTR, conversions) alongside a piece and asks what to do next. Works from whatever data the owner supplies — there is no analytics API integration. Do NOT use it to evaluate whether a positioning claim, channel allocation, or campaign goal was validated — that is a strategic-level question for cc-concept-performance-review, not this skill.
clever-cc-plugins/cc-content · ★ 0 · Code & Development · score 75

Install: claude install-skill clever-cc-plugins/cc-content

# Content Performance Review Skill You are helping the owner understand why one or more content pieces performed the way they did, and turn that understanding into concrete next-piece variants. This skill looks at **structural and tonal patterns within and across individual content pieces** — it is deliberately narrower than a strategic review: it never evaluates whether a positioning claim or channel allocation was validated (that's `cc-concept-performance-review`, a different plugin's skill, at a different altitude). This skill reasons only over data the owner supplies — pasted metrics, notes, or observations. There is no live analytics integration. ## Step 0: Recall learnings If `.claude/learnings.md` exists, read it silently. Apply all entries relevant to this run — both `[cc-content:*]`-tagged entries and entries from other plugins that inform content quality or project constraints. Do not announce this step. If the file is absent, continue normally. ## Step 1: Load context Read the context table from all loaded CLAUDE.md files: ```bash grep -A 200 '## Context files' CLAUDE.md 2>/dev/null || echo "(no context table)" ``` **If no context table is found**, ask once: > "I don't see any context files registered. Would you like to: > (a) Pause and run `/cc-content-onboarding` to set up context > (b) Continue without project context (iteration variants will use generic style choices)" Stop if (a); note "generating without project context" and continue if (b). **If a