ktg-plugin-marketplace/plugins/linkedin-studio/assets/analytics/README.md
Kjell Tore Guttormsen b6bb61246b refactor(linkedin)!: rename plugin linkedin-thought-leadership → linkedin-studio (v3.0.0)
BREAKING CHANGE: the marketplace slug, the agent namespace
(linkedin-studio:<agent>), and the runtime state-file path
(~/.claude/linkedin-studio.local.md) all change. Reinstall required;
existing state migrated in place (post metrics, streak, history preserved).
The /linkedin:* commands are unchanged — the command namespace is set
per-command in frontmatter and was always independent of the plugin slug.
Functionality is byte-identical to v2.4.0; this release is pure identity.

- dir + manifests: plugins/linkedin-studio + plugin.json + root marketplace.json
- agent namespace updated in commands/newsletter.md (only functional invoker)
- state path updated in 4 hook scripts + topic-rotation prompt + state template
- catch-all skill dir renamed skills/linkedin-studio (5 functional skills unchanged)
- docs + version bump to 3.0.0 across README badge, CHANGELOG, root README/CLAUDE.md
- historical records (CHANGELOG past entries, docs/ build artifacts,
  config-audit v5.0.0 snapshots) intentionally retain the old slug

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-05-29 11:32:02 +02:00

78 lines
2 KiB
Markdown

# LinkedIn Analytics Data
This directory contains imported analytics data from LinkedIn CSV exports.
## How to Import
1. Go to [LinkedIn Creator Analytics](https://www.linkedin.com/analytics/creator/content/)
2. Click **Export** to download a CSV of your content analytics
3. Save the CSV file to `exports/` directory
4. Run `/linkedin:import` in Claude Code
## Directory Structure
```
analytics/
├── exports/ # Place LinkedIn CSV exports here
├── posts/ # Auto-generated: imported post data (JSON)
├── weekly-reports/ # Auto-generated: weekly performance reports (JSON)
└── README.md # This file
```
## Data Format
### Post Analytics (posts/*.json)
Each file contains a batch of imported posts:
```json
{
"batchId": "batch-...",
"importedAt": "2026-01-29T...",
"exportFilename": "content-analytics.csv",
"dateRange": { "from": "2026-01-13", "to": "2026-01-28" },
"postCount": 8,
"posts": [
{
"id": "abc123",
"title": "First 100 chars of post...",
"publishedDate": "2026-01-28",
"metrics": {
"impressions": 4523,
"reactions": 87,
"comments": 23,
"shares": 12,
"clicks": 156,
"engagementRate": 6.15
}
}
]
}
```
### Weekly Reports (weekly-reports/*.json)
Generated via `/linkedin:report`. Contains:
- Summary metrics (totals, averages)
- Top and underperforming posts
- Week-over-week trends
- Performance alerts (spikes, drops)
## CLI Usage
The analytics CLI can also be invoked directly:
```bash
# Import a CSV export
ANALYTICS_ROOT=./assets/analytics node --import tsx scripts/analytics/src/cli.ts import <filename>
# Generate weekly report
ANALYTICS_ROOT=./assets/analytics node --import tsx scripts/analytics/src/cli.ts report --week 2026-W05
# Analyze trends
ANALYTICS_ROOT=./assets/analytics node --import tsx scripts/analytics/src/cli.ts trends --period month --metric impressions
```
## Privacy
All data in this directory (except this README) is gitignored. Your analytics data stays local.