Menu
Quick status check without API calls. Shows current state from data files + session info.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Complete reference for the linkedin-cli tool. Load this skill when you need to call the CLI via Bash to fetch LinkedIn data, manage connections, or send messages.
Morning Check / Session Entry Point. Delta pipeline: Stage 1 COLLECT → Stage 2 DETECT (+ Feed parallel). On-the-fly engagement analysis, no stored contacts.
Complete data schema for LinkedIn tracking. Markdown file-per-record with YAML frontmatter. Naming conventions, schemas for all 11 record types, Glob/Read/Write/Edit access patterns.
Generate personalized outreach message for a LinkedIn contact.
Deep onboarding for LinkedIn Commander. Interview + historical post analysis + competitor deep dives + system generation. The system starts "warmed up", not empty.
Analyze post performance. Compares with baseline, detects patterns, evaluates experiments, analyzes comments, updates ICP. Lifecycle-aware.
| name | check |
| description | Quick status check without API calls. Shows current state from data files + session info. |
| user-invocable | true |
| allowed-tools | ["Read","Edit","Glob","Grep"] |
Shows the current state without API calls or updates. Only reads data files and config.json.
Load config: config.json (incl. session block)
Read data files (no agent needed, read directly):
Glob("data/posts/*.md") → count per lifecycleGlob("data/posts/archive/*.md") → countGlob("drafts/*.md") → count per statusGrep("status: New", path="data/signals/")Grep("status: Active", path="data/strategy/")Grep("experiment:", path="data/posts/")Show session info:
Display compact:
LinkedIn Commander Status (@username)
SESSION:
Last session: 18h ago (yesterday 08:00)
Last report: CW 10 (4 days ago)
Last evolve: 11 days ago
Last competitor check: 8 days ago
CONTENT:
Posts tracked: 5 active + 3 cooling + 42 archived
Ideas: 3 | Drafts: 1
Last post: 1 day ago
Strategy: v1.2 (since Mar 03)
Experiment: hook-type-v1 (7/10 posts)
SIGNALS:
New: 3 (1 High, 2 Medium)
RECOMMENDATION:
→ /auto for Morning Check (18h since last session)
If user asks to update a signal (e.g., "mark signal as acted", "dismiss signal X"):
Grep("<search term>", path="data/signals/") → find matching signal fileEdit(file, "status: New", "status: Acted") (or Acknowledged/Dismissed as requested)This is the ONLY write operation /check performs — all other data is read-only.