Agents & OrchestrationSûr100100/100
Pov Line Generator (Microsoft)
Use this skill when the user asks for a point of view, punchy line, positioning sentence, provocative statement, headline angle, opinion line, or concise strategic stance.
ou envoie-le directement à ton agent.
Installer dans ton projet
$ curl -fsSL https://arboristhree.xyz/cli/install-skill.mjs -o /tmp/arboris-install-skill.mjs && node /tmp/arboris-install-skill.mjs pov-line-generator__microsoft-cat-agent-skills__submissions-57d7e5d1b44eMicrosoft
microsoft/cat-agent-skills
Contenu à copier
--- name: pov-line-generator description: Use this skill when the user asks for a point of view, punchy line, positioning sentence, provocative statement, headline angle, opinion line, or concise strategic stance. metadata: origin: Microsoft --- # POV Line Generator Use this skill to generate concise, distinctive point-of-view lines that help a user frame an argument, post, slide, campaign, or talk. ## What makes a good POV line A strong POV line should: - Take a clear stance. - Be specific enough to be meaningful. - Avoid generic trend commentary. - Create useful tension without becoming clickbait. - Be easy to reuse as a post opener, slide headline, talk premise, campaign angle, or executive summary line. ## Inputs to look for - Topic or theme. - Audience. - Desired stance or tension. - Channel: LinkedIn, slide, keynote, blog, proposal, campaign, workshop. - Tone: practical, provocative, premium, accessible, technical, executive, conversational. - Words to include or avoid. ## Workflow 1. Identify the underlying argument, not just the topic. 2. Look for a tension: common belief vs better belief, adoption vs transformation, activity vs value, tooling vs operating model, speed vs control, scale vs quality. 3. Generate one recommended line first. 4. Provide alternatives grouped by style. 5. Keep each line concise and useful. 6. Do not invent evidence or claims. ## Output format ```markdown ## Recommended POV line [One strong line] ## Alternatives ### More direct - [Line] - [Line] ### More provocative - [Line] - [Line] ### More executive - [Line] - [Line] ## Why the recommended line works [One short explanation] ``` ## References This skill includes supporting reference material. Read the relevant reference file when the task needs additional structure, rubric detail, examples, or checklist support. - `references/pov-patterns.md` - use this when additional structure, examples, or checks are useful for the task. ## Quality checklist Before responding, check: - The line has a clear point of view. - It is not interchangeable with any other topic. - It avoids empty hype. - It can plausibly open a post, slide, talk, or section. - The alternatives are meaningfully different, not minor rewrites.
Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.
Ce que fait Pov Line Generator (Microsoft)
Take a clear stance.
Be specific enough to be meaningful.
Avoid generic trend commentary.
Create useful tension without becoming clickbait.
Comment utiliser Pov Line Generator (Microsoft)
1
Copie le prompt
Un clic copie le prompt packagé (ou l'envoie à ton agent).
2
L'agent installe le skill
Il ajoute le SKILL.md et ses ressources à ton projet.
3
Activation automatique
Le skill s'active dès que le contexte correspond.
Déclencheurs pour Pov Line Generator (Microsoft)
Dis simplement à ton agent quelque chose comme :
Applique le skill pov-line-generator__microsoft-cat-agent-skills__submissions-57d7e5d1b44e à cette tâche
Utilise pov-line-generator__microsoft-cat-agent-skills__submissions-57d7e5d1b44e pour améliorer cette implémentation
Passe en revue ce sujet avec pov-line-generator__microsoft-cat-agent-skills__submissions-57d7e5d1b44e
Skills liés à Pov Line Generator (Microsoft)
Acceleration (Microsoft)
Compare synthetic acceleration options and clearly separate scenario value from forecast commitments.Account Overview (Microsoft)
Create a synthetic Acme account overview and identify evidence that merits seller attention.Acroform Writer (Microsoft)
Use this skill whenever the user wants values written INTO an existing PDF form that lives in the connected SharePoint knowledge source — filling out, completing, populating, or submitting a fillable PDF (application, intake sheet, contract, government form) from data they supply, a spreadsheet row, or the conversation. Triggers include "fill out the job application form", "complete the intake form for [person]", "populate our standard NDA template", and "make this ready to send / non-editable" (flatten). The source form should be found via knowledge search; only ask the user to upload it if knowledge search turns up nothing plausible. different task), and do NOT use it on scanned/image-only PDFs that have no real fillable fields — those need OCR or manual overlay instead, which this skill explicitly detects and reports rather than silently failing.