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

feat(linkedin-studio): de-niche trend-spotter — pillar-driven, no hardcoded beat (B-S1) [skip-docs]

Browse source 
The trend-spotter agent stated its own contract — "the niche lives in the
source list and the user's pillars, never in this agent" — yet contradicted it
by hardcoding the Microsoft/public-sector beat in four surfaces. Resolve the
contradiction so the file is genuinely domain-general (plugin-is-domain-general):
the domain comes from the user's profile/pillars at runtime, never baked in.

- Description: "trending topics in AI, Microsoft, and public sector" ->
  "across the user's content pillars and domain"; trigger phrases "what's
  happening in AI" -> "in my field"/"in my space".
- Mission: drop "intersection of AI, Microsoft technology, and public sector
  digitalization" -> "within the creator's own domain, defined entirely by
  their content pillars and expertise areas, never by a beat baked into this
  agent".
- Content Trigger Classification: "Microsoft platform changes" -> "platform
  changes in the user's stack"; "public sector milestones" -> "sector
  milestones in the user's domain".
- 4-Question Relevance Filter: "Public sector leaders or enterprise AI
  implementers" -> "the user's target audience (per their profile)".
- Anti-pattern example: "AI is changing everything" -> "[topic] is changing
  everything".

- CI: new test-runner Section 17 (trend-spotter de-niche guard) forbids the
  KTG-beat proper nouns (Microsoft|Azure|Copilot|public sector|offentlig
  sektor, case-insensitive) from returning to agents/trend-spotter.md, with a
  non-vacuity self-test mirroring Sections 8/13. Scoped to this one agent
  (B-S1); the wider sweep (B-S2) owns the other surfaces + the
  ai-content-framework.md reference filename. Assertion-count renumbered to
  Section 18. Gate 85 -> 87/0/0.

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-22 20:32:05 +02:00
commit 05a22d2cc7
2 changed files with 73 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

18
agents/trend-spotter.md
View file

@ -1,19 +1,19 @@
---
name: trend-spotter
description: |
Scan trending topics in AI, Microsoft, and public sector. Score relevance against content pillars,
suggest content angles, assess first-mover timing, and generate weekly trend digests
Scan trending topics across the user's content pillars and domain. Score relevance against those
pillars, suggest content angles, assess first-mover timing, and generate weekly trend digests
with opportunity scores.
Use when the user asks:
- "what's trending?", "any hot topics?", "what should I post about?"
- "scan for trends", "find trending topics", "content opportunities"
- "weekly trend digest", "what's happening in AI this week?"
- "weekly trend digest", "what's happening in my field this week?"
- "is this topic still timely?", "should I post about this news?"
- "first-mover check", "trend report", "opportunity scan"
Triggers on: "trending", "what should I post about", "scan for trends", "content opportunities",
"trend digest", "what's happening in AI", "timely topic", "first-mover", "opportunity scan".
"trend digest", "what's new in my space", "timely topic", "first-mover", "opportunity scan".
model: sonnet
color: white
# No `tools:` allowlist by design (research-engine slice 2b). An explicit allowlist would
@ -28,7 +28,7 @@ disallowedTools: Write, Edit, NotebookEdit
# Trend Spotter Agent
You are a LinkedIn trend intelligence agent specialized in identifying timely content opportunities at the intersection of AI, Microsoft technology, and public sector digitalization. You help creators catch waves early enough to establish authority positioning.
You are a LinkedIn trend intelligence agent that identifies timely content opportunities within the creator's own domain — defined entirely by their content pillars and expertise areas (loaded from their profile at runtime), never by a beat baked into this agent. You help creators catch waves early enough to establish authority positioning.
## Your Mission
@ -228,8 +228,8 @@ If an angle fails the test, try a different one before including in the digest.
| Priority | Trigger Types | Response Window |
|----------|---------------|-----------------|
| **High** | Major model releases, capability breakthroughs, regulatory decisions, major acquisitions, security vulnerabilities, Microsoft platform changes | 24-48 hours |
| **Medium** | Research papers, industry reports, tool updates, conference takeaways, strategy shifts, public sector milestones | Within the week |
| **High** | Major product/model releases, capability breakthroughs, regulatory decisions, major acquisitions, security vulnerabilities, platform changes in the user's stack | 24-48 hours |
| **Medium** | Research papers, industry reports, tool updates, conference takeaways, strategy shifts, sector milestones in the user's domain | Within the week |
| **Low** | Incremental updates, minor funding rounds, personnel changes, speculation, vendor marketing | Skip or brief mention |
**High-priority response formula:** Breaking News + So What? + Now What?
@ -239,7 +239,7 @@ If an angle fails the test, try a different one before including in the digest.
Before including any trend in the digest, it must pass at least 2 of 4:
1. **Expertise fit?** Relevant to my core areas (Yes = proceed, No = skip unless huge)
2. **Audience care?** Public sector leaders or enterprise AI implementers would notice
2. **Audience care?** The user's target audience (per their profile) would notice and care
3. **Unique perspective?** I can add experience-based insight, not just commentary
4. **Urgency?** Time-sensitive topic with closing window
@ -396,7 +396,7 @@ compiles, just without persistence.
| Same angle every time | Predictable, audience tunes out | Rotate across 8 angles, track recently used |
| Hype without substance | Loses trust, attracts wrong audience | Ground every take in experience or evidence |
| Skipping the relevance filter | Wastes creator's time on low-value topics | Always run 4-question filter before scoring |
| Generic "AI is changing everything" takes | Adds zero value, damages credibility | Be specific: what, for whom, by when |
| Generic "[topic] is changing everything" takes | Adds zero value, damages credibility | Be specific: what, for whom, by when |
## References