docs(linkedin-studio): repo-standard-gate — README-forsteskjerm, Install-blokk, doede referanser [skip-docs]

Kjort mot repo-standard v0.1.1 (klasse: plugin). Fikset alle ekte ERROR:

- README-DESC: apningslinjen er na identisk med forge-beskrivelsen
  (README == forge). Taglinen flyttet en linje ned.
- HEADING-MISSING x3: `### Installation` under Quick Start promotert til
  toppniva `## Install` og flyttet opp foran «Two Engines» (agent-lesbar,
  forutsigbar posisjon); `### Prerequisites` -> `## Requirements`;
  `## Boundaries (as of 2026-07)` -> `## Non-goals` (dato beholdt i
  ingressen); nytt `## Changelog` med peker til CHANGELOG.md.
- Doed referanse (SKIP LINK-OUTSIDE-REPO): `../../README.md#ai-generated-
  code-disclosure` var monorepo-arv og peker ingensteds etter polyrepo-
  migreringen — na GOVERNANCE.md#can-i-trust-this i eget repo.
- docs/voyage-build/brief.md: to lenker med `./` som ikke ble oppdatert da
  fila ble flyttet ned en mappe — na `../`.

Star igjen (ikke repo-defekter):
- ERROR LINK-INTERNAL-MISSING README.md:255 `references/` + WARN samme kode
  scripts/trends/README.md:8 `../specifics-bank`: begge er sporede
  KATALOGER. Gaten bygger sitt fasit-sett fra `git ls-files`, som aldri
  emitterer katalognavn, sa en katalog-lenke kan pr. konstruksjon ikke
  resolve. Klassifiserer-defekt i repo-standard, ikke her — lenkene er
  korrekte og beholdes. Varslet repo-standard via coord.
- WARN README-H1: tittelen er bevisst produktnavn, ikke drift.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015F3zUvokC7zniU71RYQPJZ
This commit is contained in:
Kjell Tore Guttormsen 2026-08-03 21:54:08 +02:00
commit 51bb5a6fb2
2 changed files with 39 additions and 29 deletions

View file

@ -1,10 +1,12 @@
# LinkedIn Studio Plugin for Claude Code # LinkedIn Studio Plugin for Claude Code
Full-spectrum LinkedIn content engine for Claude Code: feed posts, carousels, video scripts, and long-form newsletters. Aligned to LinkedIn's 2026 ranking model.
> Turn your expertise into LinkedIn authority — without the blank page, the guesswork, or the generic AI slop. > Turn your expertise into LinkedIn authority — without the blank page, the guesswork, or the generic AI slop.
> **Solo-maintained, fork-and-own.** This plugin is a starting point, not a vendor product. Issues are welcome as signals; pull requests are not accepted. See [GOVERNANCE.md](GOVERNANCE.md) for the full model and what upstream provides. > **Solo-maintained, fork-and-own.** This plugin is a starting point, not a vendor product. Issues are welcome as signals; pull requests are not accepted. See [GOVERNANCE.md](GOVERNANCE.md) for the full model and what upstream provides.
*AI-generated: all code produced by Claude Code through dialog-driven development. [Full disclosure →](../../README.md#ai-generated-code-disclosure)* *AI-generated: all code produced by Claude Code through dialog-driven development. [Full disclosure →](GOVERNANCE.md#can-i-trust-this)*
![Version](https://img.shields.io/badge/version-0.8.0-blue) ![Version](https://img.shields.io/badge/version-0.8.0-blue)
![Platform](https://img.shields.io/badge/platform-Claude_Code_Plugin-purple) ![Platform](https://img.shields.io/badge/platform-Claude_Code_Plugin-purple)
@ -26,6 +28,32 @@ This is not a shortcut. Hand the wheel to the AI and you land where everyone who
--- ---
## Install
Add the marketplace, then install the plugin:
```bash
claude plugin marketplace add https://git.fromaitochitta.com/open/ktg-plugin-marketplace.git
claude plugin install linkedin-studio@ktg-plugin-marketplace
```
Or add the marketplace and browse interactively with `/plugin`. Or enable directly in `~/.claude/settings.json`:
```json
{
"enabledPlugins": {
"linkedin-studio@ktg-plugin-marketplace": true
}
}
```
## Requirements
- [Claude Code](https://docs.anthropic.com/en/docs/claude-code) with plugin support enabled
- Node.js 18+ (for hooks and analytics CLI; analytics requires `tsx`: `cd scripts/analytics && npm install`)
---
## Two Engines ## Two Engines
LinkedIn Studio is really two content engines sharing one surface. They have different speeds, different gates, and different goals. LinkedIn Studio is really two content engines sharing one surface. They have different speeds, different gates, and different goals.
@ -62,30 +90,6 @@ Each gate exists because skipping it is expensive: spine errors are caught at th
## Quick Start ## Quick Start
### Prerequisites
- [Claude Code](https://docs.anthropic.com/en/docs/claude-code) with plugin support enabled
- Node.js 18+ (for hooks and analytics CLI; analytics requires `tsx`: `cd scripts/analytics && npm install`)
### Installation
Add the marketplace, then install the plugin:
```bash
claude plugin marketplace add https://git.fromaitochitta.com/open/ktg-plugin-marketplace.git
claude plugin install linkedin-studio@ktg-plugin-marketplace
```
Or add the marketplace and browse interactively with `/plugin`. Or enable directly in `~/.claude/settings.json`:
```json
{
"enabledPlugins": {
"linkedin-studio@ktg-plugin-marketplace": true
}
}
```
### Get Started (5 minutes) ### Get Started (5 minutes)
Run the onboarding wizard — it walks you through profile, setup, and your first post in one flow: Run the onboarding wizard — it walks you through profile, setup, and your first post in one flow:
@ -196,9 +200,9 @@ All 30 commands use colon notation: `/linkedin:post`, `/linkedin:quick`, etc. Th
--- ---
## Boundaries (as of 2026-07) ## Non-goals
LinkedIn Studio is honest about what it can and cannot do for a **personal profile**: What LinkedIn Studio deliberately does not do for a **personal profile** (boundaries as of 2026-07):
- **Post-level analytics via API** — exists, but is **partner-gated** (a vetted Community Management API app + a verified organization + a Page). Not self-serve for a solo profile, so the practical floor is the **CSV export** you drop into `/linkedin:import`. Per-post **saves** are visible in *native* post analytics (count-only, since ~Sept 2025) but absent from the CSV and have no self-serve API — the tool does **not** auto-track them, but you can add a `Saves` column to the CSV manually and `/linkedin:import` ingests it (omit it and saves stays *unknown*, never 0, never folded into engagement rate). - **Post-level analytics via API** — exists, but is **partner-gated** (a vetted Community Management API app + a verified organization + a Page). Not self-serve for a solo profile, so the practical floor is the **CSV export** you drop into `/linkedin:import`. Per-post **saves** are visible in *native* post analytics (count-only, since ~Sept 2025) but absent from the CSV and have no self-serve API — the tool does **not** auto-track them, but you can add a `Saves` column to the CSV manually and `/linkedin:import` ingests it (omit it and saves stays *unknown*, never 0, never folded into engagement rate).
- **Auto-publish** — technically possible via the `w_member_social` scope, so this is a **design choice**, not an API limit: the OAuth/token overhead plus LinkedIn's terms on automated posting make copy-to-clipboard + you-paste the right default. The calendar's "publish" action marks a post **you** posted as published — it never posts on your behalf. - **Auto-publish** — technically possible via the `w_member_social` scope, so this is a **design choice**, not an API limit: the OAuth/token overhead plus LinkedIn's terms on automated posting make copy-to-clipboard + you-paste the right default. The calendar's "publish" action marks a post **you** posted as published — it never posts on your behalf.
@ -254,6 +258,12 @@ The README is the front door. The detail lives alongside it:
--- ---
## Changelog
See [CHANGELOG.md](CHANGELOG.md).
---
## License ## License
This project is licensed under the [MIT License](LICENSE). The plugin architecture, content strategies, and algorithm analysis are original work. LinkedIn is a trademark of LinkedIn Corporation. This project is licensed under the [MIT License](LICENSE). The plugin architecture, content strategies, and algorithm analysis are original work. LinkedIn is a trademark of LinkedIn Corporation.

View file

@ -1,8 +1,8 @@
# Bygge-brief (Voyage-input) — LTL fullspektrum-innholdsmotor → v2.0.0 # Bygge-brief (Voyage-input) — LTL fullspektrum-innholdsmotor → v2.0.0
> **Formål:** Input til `/trekplan` (Voyage-pluginen). Dette er byggingen av LTL-pluginen, drevet som et Voyage-prosjekt: `/trekplan` produserer en kjørbar plan med per-steg Manifests, `/trekexecute --fg` + `/trekcontinue` driver sesjonene, `/trekreview` er release-gate. > **Formål:** Input til `/trekplan` (Voyage-pluginen). Dette er byggingen av LTL-pluginen, drevet som et Voyage-prosjekt: `/trekplan` produserer en kjørbar plan med per-steg Manifests, `/trekexecute --fg` + `/trekcontinue` driver sesjonene, `/trekreview` er release-gate.
> **Detaljert referanse:** [`plan-fullspektrum-innholdsmotor.md`](./plan-fullspektrum-innholdsmotor.md) (samme mappe) — den hardnede planen med §0 orientering, §4 renovering, §5 langform, §6 byggeklosser, §7 render, §10 DoD. **Les den; den er fasit for hva som skal bygges.** > **Detaljert referanse:** [`plan-fullspektrum-innholdsmotor.md`](../plan-fullspektrum-innholdsmotor.md) (i `docs/`) — den hardnede planen med §0 orientering, §4 renovering, §5 langform, §6 byggeklosser, §7 render, §10 DoD. **Les den; den er fasit for hva som skal bygges.**
> **Opprinnelig retningsbrief:** [`brief-fullspektrum-innholdsmotor.md`](./brief-fullspektrum-innholdsmotor.md). > **Opprinnelig retningsbrief:** [`brief-fullspektrum-innholdsmotor.md`](../brief-fullspektrum-innholdsmotor.md).
--- ---