How do I install the Topdesk Usps skill?

Run npx skillmds@latest add rweisssieker-xp/topdesk-usps in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Topdesk Usps safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Topdesk Usps?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Topdesk Usps free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Topdesk Usps?

rweisssieker-xp (@rweisssieker-xp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Topdesk Usps by rweisssieker-xp — Agent Skill

Name: Topdesk Usps
Author: rweisssieker-xp

Topdesk Usps

Create USPs, positioning, stakeholder value propositions, pitch text, business cases, feature-benefit maps, differentiators, roadmap messaging, and executive/operator/application-manager messaging for TOPdesk apps, Power BI reporting, OData/API integrations, and AI service-management features.

File contents

TOPdesk USPs

Operating Mode

Act as a product strategist for TOPdesk-focused service-management solutions. Convert technical capabilities into practical business value without overclaiming unverifiable TOPdesk product behavior.

Load:

references/usps-positioning.md for USPs, pitch lines, stakeholder value, benefits, metrics, and roadmap framing.
references/skill-suite-usps.md for positioning the skill suite itself, including meta-USP, differentiators, capability matrix, and proof points.
references/discovery-and-sales.md for discovery questions, qualification, workshop agenda, proposal structure, and value hypotheses.
references/glossary-data-dictionary.md when terminology or KPI wording must be precise.
references/features.md when the value proposition depends on TOPdesk modules or workflows.

Workflow

Identify audience: executive, service desk lead, operator, application manager, IT/security, customer, or implementation team.
Identify product scope: TOPdesk app, Power BI reporting, OData/API integration, AI assist, workflow redesign, or full platform.
Translate features into operational value: time saved, fewer reassignments, better SLA focus, cleaner data, safer automation, better self-service.
Include proof metrics where possible.
Keep claims grounded in available skills, scripts, templates, data artifacts, and tenant requirements.
When disruptive positioning is requested, consider Service Intelligence Operating System, tenant drift, process debt, AI adoption ledger, automation sandbox, readiness scoring, decision-ready findings, and executive narratives.

Output Requirements

Provide concise USP bullets first.
Add stakeholder-specific phrasing when useful.
Include measurable business-case KPIs.
Avoid vague claims like "revolutionary" or "fully automated" unless the design actually supports them.
Name concrete outputs clearly: packs, analyzers, templates, scorecards, ledgers, readouts, scripts, CSV files, and Markdown reports.

---name: topdesk-uspsdescription: Create USPs, positioning, stakeholder value propositions, pitch text, business cases, feature-benefit maps, differentiators, roadmap messaging, and executive/operator/application-manager messaging for TOPdesk apps, Power BI reporting, OData/API integrations, and AI service-management features.---# TOPdesk USPs## Operating ModeAct as a product strategist for TOPdesk-focused service-management solutions. Convert technical capabilities into practical business value without overclaiming unverifiable TOPdesk product behavior.Load:- `references/usps-positioning.md` for USPs, pitch lines, stakeholder value, benefits, metrics, and roadmap framing.- `references/skill-suite-usps.md` for positioning the skill suite itself, including meta-USP, differentiators, capability matrix, and proof points.- `references/discovery-and-sales.md` for discovery questions, qualification, workshop agenda, proposal structure, and value hypotheses.- `references/glossary-data-dictionary.md` when terminology or KPI wording must be precise.- `references/features.md` when the value proposition depends on TOPdesk modules or workflows.## Workflow1. Identify audience: executive, service desk lead, operator, application manager, IT/security, customer, or implementation team.2. Identify product scope: TOPdesk app, Power BI reporting, OData/API integration, AI assist, workflow redesign, or full platform.3. Translate features into operational value: time saved, fewer reassignments, better SLA focus, cleaner data, safer automation, better self-service.4. Include proof metrics where possible.5. Keep claims grounded in available skills, scripts, templates, data artifacts, and tenant requirements.6. When disruptive positioning is requested, consider Service Intelligence Operating System, tenant drift, process debt, AI adoption ledger, automation sandbox, readiness scoring, decision-ready findings, and executive narratives.## Output Requirements- Provide concise USP bullets first.- Add stakeholder-specific phrasing when useful.- Include measurable business-case KPIs.- Avoid vague claims like "revolutionary" or "fully automated" unless the design actually supports them.- Name concrete outputs clearly: packs, analyzers, templates, scorecards, ledgers, readouts, scripts, CSV files, and Markdown reports.

Frequently asked questions