Claude Skill Marketplace

Begleitet Änderungen bei TeleClinic: erkennt, was sich geändert hat, findet veraltete Stellen in Confluence und Jira, nennt die zu informierenden Teams und liefert eine Checkliste mit fertigen Vorschlägen, die er nach Freigabe selbst ausführt.

Drafts and files Jira tickets in TeleClinic's format — Strategic Initiative to Sub-task — with the right parent, title level and acceptance criteria that define what gets built, not how. Not for status transitions, multi-ticket audits or board cleanups.

Drafts a legal request for TeleClinic's LDR Jira board (Legal and Data Protection) and files it after the user approves.

Creates or improves Jira Story tickets in the PO (Platform Operations Tech) project, written purely from the business point of view. Technical Specifications and Testing are always left blank for engineering/QA.

Writes and rewrites patient-facing TeleClinic copy for a specific channel (app screen, push, email, content card, IAM, LP headline, Meta ad script) and returns at least two channel-appropriate variants plus a recommendation with the psychological lever, the target funnel event and an HWG/UWG check. Pulls real patient language from Metabase for indication-specific copy.

Shapes Claude's output to be direct and immediately actionable: action first, numbered steps, no preamble or recap. A TeleClinic-renamed, de-pathologized version of the popular open-source "i-have-adhd" skill, per the Inclusive Language Guide (a diagnosis should not be used as a metaphor/brand for a communication style).

Guides you through the full bug-reporting process for doctor-related issues at TeleClinic: gathers information via a form, checks the Jira BUB board for duplicates, creates the ticket, and notifies the responsible team via Slack. Only activate when someone actively wants to report a bug or create a Jira ticket — not for general questions or troubleshooting.

Erstellt den woechentlichen Doc Growth Kurier fuer das Doctor-Growth-Team: liest Slack-Channels (#mission-doctor-growth, #team-dg-customer-success, #team-doctor), zeigt Mission-KPIs aus Metabase, sammelt Releases, gleicht Wissen mit Confluence ab und postet die gestaltete Zeitungsseite.

Pulls the weekly Doctor Support KPIs (CSAT, survey participation, ticket density, treatment volume, and comment highlights) from Metabase and writes a bilingual (German + English) analysis text ready to paste into the company-wide Weekly report.

Runs TeleClinic's automated experiment learning loop: searches Won/Lost experiments, synthesizes cross-cutting learnings, and generates HBPS hypothesis and PG iteration tickets with a single approval gate before anything is written.

Explains how code the user works with actually works — a codebase, a framework, a merge request, a single file — for people who are not experts in that language or stack, grounded line-by-line in the repo's real code instead of generic textbook examples.

Writes the Monday performance post for #tc-performance — a headline plus 2–3 driver bullets on why last week's treatments moved and what will move next week (holidays, RKI, segments, channels, slugs, integrations, releases), plus an evidence block, always checked with the requester before posting. Trigger on "tc-performance update", "Wochen-Performance erklären", "warum sind wir letzte Woche gefallen/gestiegen", "what's driving treatments this week", "Performance-Recap für den Channel", "was erwartet uns nächste Woche", or when someone in #tc-performance asks why traction changed. NOT for the Core Weekly leadership doc (core-weekly-update), not for aTM deep dives (atm-roundtable-brief), not for the 2027 budget/forecast model itself.

Creates a TeleClinic HBPS growth hypothesis from experiment keys or a problem statement, through to a short Jira ticket that leads with a testable hypothesis and its value, linked to its CMDB Signal, with a single approval gate before anything is written.

Creates formal ISO 27001 risk register entries for Teleclinic's ISMS, formatted for Vanta.

Scores a TeleClinic Prompt Battle session (chat history + artifact) with a weighted, evidence-cited verdict and a battle report for neutral side-by-side ranking.

Diagnose and fix KIM problems across the TeleClinic chain: IBM KIM Clientmodul (cm), Praxisverbindung onboarding/registration, DC Device Server POP3/SMTP bridge, inSuite KIM account and the teleclinic_core backend (TIKIMServiceConfiguration, IBM conmgr2).

Scan the market to find new potential integration partners for TeleClinic and return a scored, prioritised shortlist ready for outreach and HubSpot upload.

Checks finished patient-facing TeleClinic marketing copy (ads, landing pages, CRM, SEO) against HWG/UWG, the KV Nordrhein cease-and-desist settlement and documented Legal precedents, and returns a traffic-light verdict per line with a compliant alternative that keeps the punch, plus the exact mandatory disclaimer where one is required.

Measures the incremental impact of a TeleClinic feature launch that had no A/B test, as extra treatments, via load-adjusted difference-in-differences with a placebo check.

Posts user feedback on a Metabase MCP answer (helpful, wrong, unclear) with a privacy-safe summary of the session to the Slack channel #bi-metabase-feedback, so BI can investigate later. Runs only when the user explicitly asks.

Sizes up an opportunity or decision and returns a two-tab spreadsheet (the case, one arithmetic step per row, plus an evidence tab) and a short written verdict naming what the answer hinges on.

OpenEvidence clone for clinical evidence lookup — designed for TeleClinic's employed doctors, usable by anyone at TeleClinic.

Research a company, app, or product for TeleClinic partner outreach, then write a ready-to-send email and a co-branded landing page HTML mockup.

Creates a TeleClinic partnership hypothesis for a partner integration, scored on Partnership RICE, and on approval files it as an Idea on the PPD discovery board.

Wochen-Check Patient Support: CSAT (L7D) und Top-3-Gründe aus den CSAT-Kommentaren je Abschnitt (5/5, 4/5, <4/5) direkt aus Metabase.

Erstellt formale TeleClinic-Angebote (Angebots-DOCX) für Pharma-Partner in OTC, eRX und pRX – einzeln oder kombiniert. IMMER nutzen, wenn ein Angebot/Offer für einen Pharma-Partner erstellt, aktualisiert oder kalkuliert werden soll: "erstell ein Offer für Bionorica", "Angebot für Klosterfrau über Placement + Newsletter", "prepare offer für den Deal in HubSpot". Auch bei Preisfragen zu Placements/HCP Education, wenn daraus ein Angebot entsteht, bei "passt der Preis zur Reichweite", "TKP / Preis pro Kontakt fürs Placement", "lohnt sich der neue Pfad für 8k", und wenn zum Angebot ein Konzept, Pilot-Vorschlag oder Versorgungskonzept gehört ("Konzept wie bei Oviva/Galderma"). Erzeugt auch Placement-Mockups im Karten-Design. Nicht für Verträge, NDAs oder Pitch-Decks.

Legt einen Pharma-Sales-Outreach an, der versandbereit für HubSpot ist: Pipeline mit Deals, Kontakten und Personalisierung plus versandfertige Mailtexte.

Creates and validates tickets (Idea, Requirement, Bug, Tech Debt) on the PLOPS Jira Product Discovery board PLOPSHE, following the board's current templates and fields, and only writes to Jira after explicit approval.

Personal prompting-craft feedback on any chat session, scored on TeleClinic's shared craft anchors, with concrete coaching and rewritten prompts.

Reviews a Claude skill (SKILL.md + bundled resources) for craftsmanship quality against TeleClinic's 15 skill design principles. Returns a traffic-light rating (red / yellow / green), a per-principle scorecard, and the highest-leverage fixes.

Walks a non-engineer step by step from a ready idea to a live A/B test in TeleClinic's Patient Web App with Iris and AB Tasty Flagship.

Compiles the 'Effect on Platform Balance' profile (a 12-row table) for a Supporting Initiative under STRATEGY-600 together with its owner and posts it as a Jira comment that mentions Julius.

For marketplace maintainers: run a structured quality review of a submitted skill and grant/revoke the quality badge (★ rating).

Autonomously monitor a Slack thread with an open action item, checking every 2 minutes and driving the conversation to completion until the goal is achieved or the other party opts out.

Checks internal work content for AI slop before or after publishing. Gives a blunt publish / fix-first / don't-publish call and a traffic-light read across five dimensions: readability, slop phrases, language clarity, author comprehension, and context sufficiency.

Erstellt das TeleClinic Software Change Assessment (C1–C5, Sonderprüfungen, Information/Zustimmung) nach der aktuellen Confluence-Policy „Software Changes & Releases“ und fragt danach, ob ein Legal-Ticket (LDR) angelegt werden soll.

Submit a Claude skill to the TeleClinic Skill Marketplace without a GitHub account or a terminal: packages it into the plugin structure, validates it, checks for secrets and patient data, and opens the pull request through the submission connector.

Runs a white-box OWASP Top 10 2021 static security audit of the TeleClinic Video platform (video-backend, app.teleclinic.video, teleclinic-video) and renders a TÜVIT-style penetration test report as a PDF.

Self-review and sign off your own spike / technical-investigation / proof-of-concept BEFORE you share it with stakeholders, so the usual gaps never make it into the doc. Enforces mandatory checks on success metrics, technical performance and authentication/integration mechanics, with extra attention to regulated/healthcare contexts (GDPR, patient data, ISO 27001, EU AI Act, MDR). Reports on the draft; it does not edit it.

Drafts screens in Figma from a completed design brief using TeleClinic's connected design system, and documents them in an in-file spec. Enforces a validated brief, screen naming convention, product palette, CTA hierarchy and no-overlap placement.

Working handbook for the patient-app-ios codebase: house code-style conventions distilled from review feedback, build/test workflows (snapshot tests, SwiftUI previews, running on device, Maestro E2E), localization via Lokalise + SwiftGen, RemoteConfig A/B experiments, Mixpanel/Braze tracking, and task playbooks for the app's core flows. Use it whenever doing iOS development in that repo.

Picks the right user-research method and writes a bilingual (EN/DE) research plan: discovery interviews, validation interviews, usability test, A/B test brief or survey with sample-size check.

Durchsucht taeglich die Demodesk-Transkripte der Doctor-Growth-Arztgespraeche nach Wissensluecken, Widerspruechen und undokumentiertem Einzelwissen, meldet Befunde strukturiert in #neues-wissen und dokumentiert freigegebenes Wissen in Confluence.