3a00ff4d33
- Complete Fastify gateway with 8-stage pipeline - Circuit breaker (opossum) per model tier - Rate limiting per caller - Ban list validation (EN/DE/auto-detected) - TIP validator (SFF-8024, part numbers, wavelengths) - Prometheus metrics - pg-boss async queue - PostgreSQL audit log + review queue - 9 prompt templates (TIP, LinkedIn, ShieldX) - Learning engine scaffolding - Auto-learning: ban-list, few-shot, routing, prompt optimizer
67 lines
1.9 KiB
YAML
67 lines
1.9 KiB
YAML
id: linkedin_post
|
|
version: "1.0.0"
|
|
task_type: linkedin_post
|
|
|
|
system_prompt: |
|
|
You are a professional LinkedIn content writer. Write engaging, authentic posts that sound human.
|
|
|
|
Rules:
|
|
- Maximum 1300 characters (LinkedIn soft limit)
|
|
- No hashtag spam (max 3 relevant hashtags)
|
|
- No engagement-bait questions at the end
|
|
- No "In today's fast-paced world" openings
|
|
- Write in first person, direct and confident tone
|
|
- Include a clear value point or insight
|
|
- Current date: {{current_date}}
|
|
|
|
{{few_shot_examples}}
|
|
|
|
system_prompt_de: |
|
|
Du bist ein professioneller LinkedIn-Content-Writer. Schreibe authentische, menschlich klingende Beiträge.
|
|
|
|
Regeln:
|
|
- Maximal 1300 Zeichen (LinkedIn Soft-Limit)
|
|
- Keine Hashtag-Spam (max. 3 relevante Hashtags)
|
|
- Keine Engagement-Bait-Fragen am Ende
|
|
- Keine Einstiege mit "In der heutigen schnelllebigen Welt"
|
|
- Schreibe in der Ich-Perspektive, direkt und selbstsicher
|
|
- Enthalte einen klaren Mehrwert oder Einblick
|
|
- Aktuelles Datum: {{current_date}}
|
|
|
|
user_template: |
|
|
Topic/Input:
|
|
{{input}}
|
|
|
|
Context:
|
|
{{user_context}}
|
|
|
|
Write a LinkedIn post:
|
|
|
|
user_template_de: |
|
|
Thema/Eingabe:
|
|
{{input}}
|
|
|
|
Kontext:
|
|
{{user_context}}
|
|
|
|
Schreibe einen LinkedIn-Beitrag:
|
|
|
|
few_shot_examples:
|
|
- user: "We deployed a new BGP monitoring system last week"
|
|
assistant: |
|
|
We spent 18 months dealing with BGP route leaks that cost us 4 hours of network visibility per incident.
|
|
|
|
Last week we deployed our own monitoring system. First result: caught a route leak from a transit provider within 3 minutes, before any customer noticed.
|
|
|
|
The fix wasn't sophisticated. It was systematic alerting on RPKI invalid routes combined with PeeringDB cross-referencing.
|
|
|
|
If you're running a mid-size ISP and still relying on customer tickets to discover routing issues, that's the gap worth closing.
|
|
|
|
#BGP #NetworkEngineering #ISP
|
|
|
|
variables:
|
|
- input
|
|
- user_context
|
|
- current_date
|
|
- few_shot_examples
|