analytics-dashboard

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# LinkedIn Analytics Dashboard

## Inputs

Accept LinkedIn exports in CSV or spreadsheet form. Use only fields actually present.

## Analysis

When Python or another deterministic data tool is available:

1. inspect schema and date range
2. clean missing values and obvious type issues
3. calculate post-level and period-level metrics
4. separate totals from rates
5. identify outliers
6. compare formats, topics, posting times, and structural features only where data supports the comparison

## Dashboard path

If the current host provides a coding workspace and the user wants a dashboard, create a simple local React or static HTML dashboard with:

- summary KPIs
- trend view
- top and bottom posts
- filterable post table
- format/topic breakdown when fields support it
- recommendation panel

If no coding workspace exists, return the analysis as tables and narrative instead.

## Recommendations

Give 5 recommendations. Every recommendation must cite a specific pattern from the uploaded data and include the relevant metric or comparison.

Do not present correlation as proof of causation.

## Visual handoff

If a local dashboard, comparison board, or report is created, use `show-me` principles for the final artifact and verify the generated file when the host supports preview.

## Creator Workspace handoff

Use `sandbox-python-executor` for calculations. Hand the verified findings to `show-me` when the user wants a dashboard or visual comparison.

<!-- written-as-spoken:links start (generated by scripts/sync-links.mjs, do not edit by hand) -->

## Linked to Written as Spoken

This skill is a node in the Written as Spoken suite. The front door is `written-as-spoken` (`../../../../SKILL.md`), and the graph lives in `../../../../references/routing-map.json`.

When a request reaches this skill through `written-as-spoken`, Mamdouh's voice rules in `../../../../references/voice-dna.md` and `../../../../references/anti-slop.md` outrank this skill's own style defaults, the house profile is active, and facts come only from the user or from `story-researcher`.

Routes that pass through here:

- `analytics` (what is working in the published posts): first step, returns to `written-as-spoken`

Hand your output to the next node in the route. When this skill is the last node, return the result to `written-as-spoken` so the draft goes through `../../../../scripts/lint.mjs` before the user sees it. When this skill is called directly, outside the suite, ignore this block.

<!-- written-as-spoken:links end -->

From imMamdouhaboammar/written-as-spoken, MIT.

More from imMamdouhaboammar/written-as-spoken