self-improver skill
✓ VerifiedAnalyzes affiliate campaign results using diagnostic frameworks to identify root causes and generate prioritized improvement plans.
- GitHub stars
- 779
- Files
- 2
- Last commit
- Oct 19, 2026
- License
- MIT
- Allowed tools
- —
What does the self-improver skill do?
self-improver analyzes affiliate campaign results using diagnostic frameworks to identify root causes and generate prioritized improvement plans.
Summary generated from the skill's SKILL.md.
About the self-improver skill
Affiliate marketers who need to understand why their campaigns are underperforming use this tool to conduct structured retrospectives. It analyzes campaign data such as clicks, conversions, revenue, and traffic to identify the specific reasons behind performance gaps. By comparing actual results against industry benchmarks or user expectations, the tool pinpoints whether issues stem from poor offer-market fit, mismatches between traffic and content, or leaks within the sales funnel.
An agent should load this skill when a user asks questions like "what went wrong?" or "how to improve my strategy?", especially after running a performance report. The skill produces a prioritized improvement plan that ranks actions by impact and effort. It provides concrete instructions for the next iteration, including specific prompt modifications and recommendations for which other specialized skills to re-run to fix identified problems.
What an agent can do with it
- 1Analyze social media engagement gapsDetermine why social media posts receive high engagement but fail to drive link clicks.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the self-improver skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the self-improver skill in Plugin
/plugin marketplace add Affitor/affiliate-skills /plugin install meta-skills@affiliate-skills
Install the self-improver skill in Claude Code
~/.claude/skills/self-improver/SKILL.md
$ npx degit Affitor/affiliate-skills/skills/meta/self-improver ~/.claude/skills/self-improverInstall the self-improver skill in Claude Code (project)
.claude/skills/self-improver/SKILL.md
$ npx degit Affitor/affiliate-skills/skills/meta/self-improver .claude/skills/self-improverInstall the self-improver skill in Codex
~/.agents/skills/self-improver/SKILL.md
$ npx degit Affitor/affiliate-skills/skills/meta/self-improver ~/.agents/skills/self-improverInstall the self-improver skill in Gemini CLI
~/.gemini/skills/self-improver/SKILL.md
$ npx degit Affitor/affiliate-skills/skills/meta/self-improver ~/.gemini/skills/self-improverInstall the self-improver skill in Claude.ai
npx degit Affitor/affiliate-skills/skills/meta/self-improver self-improver && zip -r self-improver.zip self-improver # claude.ai → Customize → Skills → + → Create skill → Upload a skill → self-improver.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachableaffitor/affiliate-skills/skills/meta/self-improver is public and reachablegithub.com/affitor/affiliate-skills/tree/HEAD/skills/meta/se ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-10-19github.com/affitor/affiliate-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/affitor/affiliate-skills/blob/HEAD/skills/meta/se ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/affitor/affiliate-skills/blob/HEAD/skills/meta/se ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 229 linesgithub.com/affitor/affiliate-skills/blob/HEAD/skills/meta/se ↗Pass
SKILL.md
View on GitHubSelf-Improver
Review affiliate campaign results, diagnose what worked and what didn't, and generate a prioritized improvement plan. Uses affiliate-specific diagnostic frameworks (offer-market fit, traffic-content match, funnel leak analysis) to identify root causes and actionable fixes.
Stage
S8: Meta — Most affiliates repeat the same mistakes because they never do structured retrospectives. Self-Improver closes the feedback loop: it takes your results, compares them to expectations, diagnoses gaps using affiliate-specific frameworks, and produces concrete actions that feed back into S1-S7 for the next iteration.
When to Use
- User has run a campaign and wants to understand results
- User's affiliate content isn't converting and wants to diagnose why
- User wants to compare actual vs expected results
- User says "what went wrong?", "why no conversions?", "how to improve?"
- User wants a structured retrospective on their affiliate efforts
- Chaining from S6.3 (performance-report) — analyze the data and plan improvements
Input Schema
campaign:
description: string # REQUIRED — what was done (e.g., "Published 3 blog reviews
# of AI video tools, shared on LinkedIn and Reddit")
duration: string # OPTIONAL — how long (e.g., "2 weeks", "1 month")
skills_used: string[] # OPTIONAL — which Affitor skills were used
channels: string[] # OPTIONAL — where content was distributed
results:
clicks: number # OPTIONAL — total clicks on affiliate links
conversions: number # OPTIONAL — total signups/purchases
revenue: number # OPTIONAL — total commission earned
traffic: number # OPTIONAL — total page views / impressions
feedback: string # OPTIONAL — qualitative feedback received
expectations:
expected_clicks: number # OPTIONAL — what was expected
expected_conversions: number # OPTIONAL
expected_revenue: number # OPTIONAL
benchmark: string # OPTIONAL — "industry average" or specific number
context:
niche: string # OPTIONAL — product category
experience: string # OPTIONAL — "first campaign" | "experienced"
budget: string # OPTIONAL — money spent (if any)
Chaining context: If S6.3 (performance-report) was run in the same conversation, pull KPIs directly. If S1-S5 outputs exist in context, reference them for gap analysis.
Workflow
Step 1: Establish Baseline
Collect campaign description and results. If numbers are missing, work with whatever is available. State assumptions clearly: "You didn't share click data, so I'll focus on qualitative analysis."
Step 2: Compare Results vs Expectations
Calculate gaps:
- Traffic gap: Expected vs actual impressions/visits
- Click gap: Expected vs actual CTR
- Conversion gap: Expected vs actual conversion rate
- Revenue gap: Expected vs actual earnings
Use industry benchmarks if user doesn't have expectations:
- Affiliate blog CTR: 2-5%
- Affiliate conversion rate: 1-3%
- Social post engagement: 1-3% of impressions
- Email click rate: 2-5%
Step 3: Diagnose Root Causes
Apply affiliate-specific diagnostic frameworks:
Offer-Market Fit: Is the product right for the audience?
- Wrong audience for the product
- Product too expensive for the audience's budget
- Product solves a problem the audience doesn't have
Traffic-Content Match: Is the traffic source aligned with the content?
- Blog content promoted on TikTok (format mismatch)
- Reddit post that reads like an ad (platform mismatch)
- Cold traffic sent to a hard sell (temperature mismatch)
Funnel Leaks: Where do people drop off?
- High impressions but low clicks → weak headline/hook
- High clicks but low conversions → landing page or product issue
- High conversions but low revenue → wrong product (low commission)
Step 4: Prioritize Improvements
Rank each improvement by:
- Impact: How much would this change move the needle? (1-5)
- Effort: How hard is it to implement? (1-5)
- Priority: Impact / Effort ratio
Step 5: Create Iteration Plan
For each top improvement, specify:
- What to change
- Which Affitor skill to re-run
- Exact prompt modification for better results
- Expected improvement (realistic estimate)
Step 6: Self-Validation
Before presenting output, verify:
- Gap calculations accurate: expected minus actual
- Root causes are evidence-based, not speculation
- Impact (1-5) and effort (1-5) scores are justified with reasoning
- Next steps reference specific Affitor skills by name
- Iteration plan has concrete timeline and measurable success metric
If any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.
Output Schema
output_schema_version: "1.0.0" # Semver — bump major on breaking changes
retrospective:
campaign: string
period: string
overall_assessment: string # "strong" | "average" | "needs_work" | "failing"
gaps:
- metric: string # e.g., "conversion_rate"
expected: string
actual: string
gap: string # e.g., "-2.5%"
diagnosis:
root_causes:
- cause: string # e.g., "Traffic-content mismatch"
evidence: string # what indicates this
severity: string # "high" | "medium" | "low"
improvements:
- action: string # what to do
skill: string # which Affitor skill to use
prompt: string # exact prompt for the skill
impact: number # 1-5
effort: number # 1-5
priority: number # impact / effort
iteration_plan:
next_steps: string[] # ordered list of actions
timeline: string # e.g., "1 week"
success_metric: string # how to measure improvement
Output Format
- Campaign Summary — what was done, results achieved
- Gap Analysis — table comparing expected vs actual metrics
- Root Cause Diagnosis — what's causing the gaps, with evidence
- Improvement Actions — prioritized table with action, skill, impact, effort
- Next Iteration Plan — ordered steps with timeline and success metrics
Error Handling
- No results data at all: "I need at least one data point to diagnose. Do you have: clicks, conversions, revenue, or even qualitative feedback (comments, reactions)? Even 'I got zero conversions' is useful data."
- Only qualitative data: Shift to qualitative analysis. "Without numbers, I'll focus on content quality, offer fit, and platform alignment. Here's what I can diagnose from your description."
- Unrealistic expectations: "You expected 100 sales from a single blog post in week 1. Industry average conversion rate is 1-3%, so 100 sales would require 3,000-10,000 clicks. Let me recalibrate your expectations and plan from there."
Examples
Example 1: Blog campaign with low conversions
User: "I wrote 3 blog reviews of AI tools last month. Got 2,000 visitors but only 2 conversions ($14 total). What went wrong?" Action: Conversion rate 0.1% vs benchmark 1-3%. Diagnose: possible funnel leak (weak CTAs? disclosure too prominent? wrong products for audience?). Check traffic sources (SEO cold traffic needs more warming). Recommend: S6 (ab-test-generator) on CTAs, S6 (seo-audit) on content quality, S4 (landing-page-creator) as intermediate step.
Example 2: Social campaign with zero clicks
User: "Posted 10 LinkedIn posts about Semrush. Lots of likes but nobody clicked my link." Action: Traffic-content mismatch. LinkedIn engagement ≠ clicks. Diagnose: link placement (probably in comments where nobody looks), content may be too educational without clear CTA, audience may not be in buying mode on LinkedIn. Recommend: S2 (viral-post-writer) with CTA-focused brief, S3 (affiliate-blog-builder) to create destination content, S7 (content-repurposer) to adapt for click-friendly platforms.
Example 3: Chained from performance-report
Context: S6.3 performance-report shows EPC of $0.02 across 5 programs, with one program at $0.15 EPC. User: "How do I improve these numbers?" Action: One program is 7x more profitable. Diagnose: concentrate effort on the winner. For the four underperformers, check offer-market fit (are these the wrong products?). Recommend: S7 (multi-program-manager) to restructure portfolio, S7 (content-repurposer) to create more content for the winning program, S6 (ab-test-generator) to optimize existing content.
References
shared/references/ftc-compliance.md— Referenced when reviewing content quality. Read in Step 3.docs/affiliate-funnel-overview.md— Funnel stage definitions for gap analysis. Read in Step 3.shared/references/flywheel-connections.md— master flywheel connection map
Flywheel Connections
Feeds Into
- All skills —
improvement_suggestionsdrive quality upgrades across the system
Fed By
performance-report(S6) — performance data revealing what needs improvementconversion-tracker(S6) — conversion trends for diagnosiscompliance-checker(S8) — compliance issues to address
Feedback Loop
- Each improvement cycle feeds back into the next self-improver run → track improvement trajectory over time
chain_metadata:
skill_slug: "self-improver"
stage: "meta"
timestamp: string
suggested_next:
- "funnel-planner"
- "performance-report"
- "skill-finder"
Files in this skill
2self-improver skill questions
How do I install the self-improver skill in Claude Code?
Run npx degit Affitor/affiliate-skills/skills/meta/self-improver ~/.claude/skills/self-improver. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the self-improver skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What kind of data does the skill need to perform an analysis?
The skill works best with clicks, conversions, revenue, and traffic data, but can also perform qualitative analysis if only descriptive feedback is provided.
Can this skill help if I don't have industry benchmarks?
Yes, the skill uses industry benchmarks like affiliate blog CTR (2-5%) and conversion rates (1-3%) to calculate gaps if you don't provide your own expectations.