Skip to content

borghei/Claude-Skills / tools/linkedin/linkedin-engagement-analytics

linkedin-engagement-analytics

Verified

Segments who reacted to and commented on a post from a CSV or JSON export, and says whether it reached the intended audience. Use when reviewing a post's engagers, checking audience fit, or building a baseline.

assets/post_readout_template.md

View on GitHub
# Post Audience Readout

One page. Describes an audience; identifies no one. Delete the raw export once
this is written and the baseline counts are recorded.

Author: ______________________  Readout date: ____________

## 1. The post

| | |
|---|---|
| Post (title or first line) | |
| Published on | |
| Written for (one sentence, as decided before publishing) | |
| What you hoped that reader would do | |

## 2. The target, as written beforehand

| Dimension | Values |
|-----------|--------|
| Seniority bands | |
| Functions | |
| Title keywords | |
| Named organisations (optional) | |
| Own-company names excluded | |
| Goal for core share (your own number) | |

Was the target written before the export was read? yes / no. If no, say so in
section 7.

## 3. The export

| | |
|---|---|
| How it was produced | |
| Taken on (days after publishing) | |
| Rows read / skipped for blank headline / duplicates merged | |
| Columns removed before analysis | |

## 4. Volume and coverage

| Measure | Count | Share |
|---------|-------|-------|
| Engagers | | 100% |
| From own company | | |
| External | | |
| External and classified (coverage) | | |
| Commenters among classified | | |

## 5. Fit

| Fit | Count | Share of classified |
|-----|-------|---------------------|
| Core | | |
| Adjacent | | |
| Off | | |

Core share: ____%   95% interval: ____% to ____%

Core among commenters: ____ of ____   Core among reaction-only: ____ of ____

Engagers from named organisations (count only): ____

## 6. Against your own history

| Reference | Value | Built from | Reading (above / in line with / below) |
|-----------|-------|------------|-----------------------------------------|
| Trailing baseline | | ____ posts, ____ classified engagers | |
| Goal | | Set on ____ | |

Sample adequate for a verdict (classified external at or above the minimum)? yes / no

Verdict in one sentence, using the three-way wording:

> 

## 7. Segments

Largest three by seniority:

| Band | Count | Share |
|------|-------|-------|
| | | |
| | | |
| | | |

Largest three by function:

| Function | Count | Share |
|----------|-------|-------|
| | | |
| | | |
| | | |

Organisations with two or more engagers (optional; omit if not needed):

| Organisation | Count |
|--------------|-------|
| | |

## 8. What this suggests

What matched expectations:

What did not:

One hypothesis to test with the next post (subject, framing or format):

## 9. Limits

- [ ] The export lists people who acted, not people who saw the post
- [ ] Headlines are self-described and may be out of date
- [ ] Sample size and coverage are stated above
- [ ] Unusual circumstances that week: ______________________
- [ ] Classification patterns changed since the baseline was built? yes / no (if yes, the baseline was re-run)

## 10. Handling record

- [ ] No names, individual headlines or attributed comments in this readout
- [ ] No cell describes a single person
- [ ] Nothing was looked up or added about any engager
- [ ] Baseline counts updated in the target file
- [ ] Raw export deleted on: ____________

## Baseline log

Roll this forward. Keep counts, not exports.

| Post | Date | Classified external | Core | Core share | In baseline window? |
|------|------|---------------------|------|------------|---------------------|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| **Pooled** | | | | | |
deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall