open/linkedin-studio
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity Actions

feat(linkedin-studio): de-niche rest-sweep — vary KTG-beat examples across surfaces (B-S2b) [skip-docs]

Browse source 
The last de-niche slice: recast the 10 sites where the vendor/sector beat
(Microsoft|Azure|Copilot|public sector) sat as the PRIVILEGED/default example,
varying each to a concrete cross-domain example instead of sterilizing
(plugin-is-domain-general — domain comes from user config, never hardcoded).

Recast (10): url-processing-templates (news worked-example Copilot->Figma),
opportunity-generation (3 headline examples + About block -> varied/ops persona),
profile (3 "good example" headlines/impact -> healthcare/e-commerce/support),
first-comment-strategy (drop "Microsoft" from research-paper example),
poll-strategy-guide (Copilot option -> generic AI assistants),
engagement-frameworks (1 of 3 direct-address audiences -> RevOps/SaaS),
setup (audience e.g. -> two varied examples), post (invocation e.g. -> SaaS pricing),
network-builder (tagline example -> ops/manufacturing),
video-scripter (2 filename slugs -> neutral topics).

Kept as false positives (would sterilize): content-angles.md (Public Sector is
1 of 6 balanced industry tables + Industry-Agnostic section), outreach.md
(Microsoft Build/Ignite/Azure UG = 3 of ~20 varied real conferences),
linkedin-growth-playbook (biographical fact in a real case study), the
Gemini/Tavily/Perplexity MCP tool-name examples, and the algorithm-signals
"Gemini provenance" SSOT citation. AI-as-topic kept (not a niche token; the
de-AI/AI-slop mechanic is the plugin's legit subject).

Gate scripts/test-runner.sh 87/0/0 (no lint touches these files yet; §17-guard
extension to content-planner is the deferred next step). 10 files, 26/26.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RBMKqPSVbvSZHtQ4heM1UY
This commit is contained in:
Kjell Tore Guttormsen 2026-06-23 10:50:28 +02:00
commit e75cd42bed
10 changed files with 26 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

10
references/url-processing-templates.md
View file

@ -37,22 +37,22 @@ Comment #1: [Link to original article]
**Example transformation:**
Source: "Microsoft announces new Copilot pricing tiers"
Source: "Figma announces new pricing tiers"
```
The new Copilot pricing isn't about the money. It's about strategy.
The new Figma pricing isn't about the money. It's about strategy.
Microsoft just restructured their Copilot licensing. Most headlines focus on the $30/user price point.
Figma just restructured its licensing. Most headlines focus on the per-seat price point.
Here's what they're missing:
The real story is differentiation. By splitting Copilot into tiers, Microsoft is:
The real story is differentiation. By splitting its plans into tiers, Figma is:
1. Creating an upgrade path (land and expand)
2. Protecting high-margin enterprise deals
3. Addressing the "too expensive for testing" problem
For organizations evaluating Copilot, this changes the conversation from "can we afford it?" to "which tier makes sense?"
For organizations evaluating Figma, this changes the conversation from "can we afford it?" to "which tier makes sense?"
My prediction: Expect competitors to follow with similar tiered models within 6 months.