agentleFS
nicojunknicojunk/claude-ig/skills/ig-analyze/SKILL.md

ig-analyze

Skill17 starsChanged 8 months agoMITView on GitHub

API-driven Instagram post and account performance analysis. Pulls live data via Instagram MCP tools, calculates engagement metrics, detects performance patterns, and benchmarks against account baselines.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Hook category analysis: If hook-library.md categories are identifiable in captions, group performance by category.

    line 89
  2. Distinctive:

    Before delivering the report, verify:

    line 108
  3. Distinctive:

    If the user requests a specific post analysis (single post), skip account-level metrics and deliver only per-post analysis with benchmark …

    line 156

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

IG Analyze -- API-driven Instagram performance analysis

Key references:

  • references/account-baseline.md -- current benchmarks, follower count, historical averages
  • references/scoring-system.md -- metric definitions, scoring thresholds, weighted formulas

CRITICAL RULE: This skill MUST use live API data. Never guess, estimate, or fabricate metrics. If an API call fails, report the failure. Do not fill in placeholder numbers.


Phase 1: Data Collection

Pull data using Instagram MCP tools in this order:

  1. Account overview:
    mcp__claude_ai_Instagram_MCP__get_user_info
    Capture: follower count, following count, media count, bio, profile pic.
  2. Recent media:
    mcp__claude_ai_Instagram_MCP__get_user_media
    Fetch the most recent 25 posts. For each, capture: id, type (carousel/reel/image), timestamp, caption, like count, comment count.
  3. Post-level insights (for each post):
    mcp__claude_ai_Instagram_MCP__get_post_insights
    Capture: reach, impressions, saves, shares, video views (if reel), profile visits.
  4. Account-level insights:
    mcp__claude_ai_Instagram_MCP__get_user_insights
    Capture: reach, impressions, follower growth, profile visits over the requested period.

Bundle independent API calls in parallel where possible. Do not make serial calls when parallel is available.

Phase 2: Metric Calculation

Calculate the following metrics from the collected data:

Per-Post Metrics

MetricFormula
Engagement Rate(likes + comments + saves + shares) / reach * 100
Save Ratesaves / reach * 100
DM-Send Rateshares / reach * 100
Completion Rate (Reels)average watch time / duration * 100
Reach-to-Follower Ratioreach / follower_count * 100

Account-Level Metrics

MetricFormula
Average Engagement Ratemean of per-post engagement rates
Save Rate Trendsave rate comparison: last 7 posts vs prior 7
Reach Growth(current period reach - prior period reach) / prior * 100
Content Mix% reels vs % carousels vs % single images

Round all percentages to 2 decimal places.

Phase 3: Pattern Detection

Analyze the calculated metrics to identify patterns:

  1. Best performers: Top 3 posts by engagement rate. Note format, hook category, posting day/time.
  2. Worst performers: Bottom 3 posts. Note format, hook category, posting day/time.
  3. Format comparison: Average engagement rate per format (reel, carousel, image).
  4. Hook category analysis: If hook-library.md categories are identifiable in captions, group performance by category.
  5. Posting time analysis: Group by day of week and hour. Identify best and worst windows.
  6. Save rate leaders: Top 3 posts by save rate (these indicate high-value content).

Phase 4: Benchmark Comparison

Load references/account-baseline.md and compare current metrics:

MetricBaselineCurrentDeltaStatus
Engagement RateX%Y%+/-Z%Above/Below
Save RateX%Y%+/-Z%Above/Below
Reach-to-FollowerX%Y%+/-Z%Above/Below
Reel CompletionX%Y%+/-Z%Above/Below

Flag any metric that is more than 20% below baseline as a warning.

Phase 5: Quality Check

Before delivering the report, verify:

  • All metrics are based on actual API data (no estimates)
  • Per-post and account-level metrics are both included
  • At least one actionable insight per pattern detected
  • Benchmark comparison uses current account-baseline.md values
  • Numbers are internally consistent (engagement rate matches component metrics)

Phase 6: Report Output

Deliver as a structured Markdown report:

## Instagram Performance Report

**Period:** [date range]
**Posts analyzed:** [count]
**Follower count:** [current]

### Key Metrics (Account Average)
| Metric | Value | vs Baseline |
|--------|-------|-------------|
| Engagement Rate | X% | +/-Y% |
| Save Rate | X% | +/-Y% |
| Reach-to-Follower | X% | +/-Y% |

### Top Performers
1. [Post description] -- [engagement rate] -- [why it worked]
2. ...
3. ...

### Format Breakdown
| Format | Avg Engagement | Avg Save Rate | Count |
|--------|---------------|---------------|-------|

### Patterns Detected
- [pattern 1 with actionable recommendation]
- [pattern 2 with actionable recommendation]

### Warnings
- [any metric >20% below baseline]

### Recommendations
1. [specific, actionable recommendation]
2. [specific, actionable recommendation]
3. [specific, actionable recommendation]

If the user requests a specific post analysis (single post), skip account-level metrics and deliver only per-post analysis with benchmark comparison.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.