Showing 34621–34650 of 77205 skills
Near-term Atlassian Marketplace cash view for the ZenUML apps — what vendor income to expect over the next few days (client subscriptions renewing) and which paying clients missed a payment in the past few days (renewal lapsed / in grace / dead payment method). Use when the user asks "what income am I expecting", "what's landing this week", "any renewals coming up", "did anyone miss a payment", "who's late", "income projection for the next few days", or wants a daily payments radar. Built on the marketplace engine (licenses + transactions joined on cloudId), payers only, all revenue apps. For lifetime revenue / top payers / a full renewals-in-a-window audit use `marketplace`; for a single tenant's paid status use `tenant`.
ZenUml/conf-app
Enable, launch, monitor, troubleshoot, and stop the local joint-debug environment across conf-app, its Cloudflare Worker, ngrok, Forge tunnel, and diagramly.ai. Use for requests mentioning joint-debug, join-debug, combined local AI Repair testing, starting or monitoring the five-service stack, or closing that stack.
ZenUml/conf-app
Create a branch, run local validation, create a PR and **merge** on main with staging deployed and draft releases created. Use when the user says "land", "land it", "land this branch", "merge this", or wants to go from local branch to merged in one command. Fixes actionable local validation failures in a bounded loop, then stops at the first unrecoverable failure. Does NOT deploy to production — use /release-app after shipping.
ZenUml/conf-app
Merge a green PR to main and verify CI succeeds (staging deploy + draft releases). Use when the user says "merge", "land", "land PR", "merge this", or when a PR has passed CI and is ready to merge. This does NOT deploy to production — use /release-app for that.
ZenUml/conf-app
Start a local development server for the Connect app and install it on a Confluence site via UPM. Use when setting up local dev, tunneling to Confluence, or installing the Connect app on a test site.
ZenUml/conf-app
Investigate per-space macro inventory for one Confluence site, comparing reported Metrics KV inventory with distinct viewed macros and optional D1 coverage. Use for macro counts, space limits and reconciling inventory/usage. Distinguishes actual stock from activity and historical sync rows.
ZenUml/conf-app
Query live Atlassian Marketplace pricing, licenses, transactions and revenue cohorts for the ZenUML apps. Use for seat-based prices, monthly/annual quotes, vendor share, renewal windows, overdue candidates, top customers and portfolio rollups. Separates recorded purchases from source-reported payment and vendor payout; Open orders are not absent purchases. Use mp_pricing.py for prices and take rates, and mp_report.py for bulk exports, scoped license/transaction joins and local snapshots. For one tenant's status, profile or trial expiry use tenant, which reuses this engine; one tenant's price still belongs here.
ZenUml/conf-app
Change the public Atlassian Marketplace listing of a ZenUML app - name, tagline, summary, highlight texts, highlight images, More details - in the vendor console, then read the result back. Use for "change the listing", "rename the app on Marketplace", "replace the highlight images", "update the tagline", "上架页", "改名", "换配图", and for reading a search rank before and after. For prices, licenses and revenue use marketplace.
ZenUml/conf-app
Use when you need a Mixpanel fact or query path for the conf-app / ZenUML Confluence add-on — which project, which event name (and the 2026-04 rename), the internal-domain exclude filter, whether isForge/isLite/product_type is usable, MCP-vs-JQL, or how to authenticate. Canonical reference for Mixpanel project 3373228. Triggers on mixpanel, session replay, macro_viewed, view_macro, create_macro, edit_macro, JQL, is_internal_client_domain, product_type, isForge, "which mixpanel project", "how to query mixpanel". For churn/retention/growth/D1 analysis use the conf-app skill instead.
ZenUml/conf-app
Query recent Confluence customer/license/trial candidates through live licenses-only Marketplace API reads. Handles 查 Confluence app 过去 N 天的新客户, defaulting to one approximate day and seven products. License starts do not prove first installation; investigate prior history only for candidates.
ZenUml/conf-app
Inspect and manage the Confluence page-content capture pipeline (forge-page-capture, R2 page-snapshots, the PAGE_CAPTURE_ENABLED kill switch, and the PAGE_CAPTURE_ALLOWED_DOMAINS allowlist) for the ZenUML Confluence app variants. Use when asked about page capture, content capture, page snapshots, the page-capture kill switch, PAGE_CAPTURE_ALLOWED_DOMAINS, or whether a tenant's page content is actually being captured.
ZenUml/conf-app
Manage the ZenUML Lite paywall rollout (Lite variant only — Full and Diagramly have no restrictions). Decide which domains to enroll in CUSTOMER_SUCCESS_SERVICE (CSS), monitor daily paywall activity, and generate the exact KV commands to execute. Use this skill whenever the user asks about paywall rollout, which clients to enable, the CSS flag, tenant enrollment state, space licensing, or "who should be on the paywall list". Also use when the user asks to check a specific domain's paywall state, wants to understand why a tenant is or isn't seeing the paywall, or wants to A/B compare paywall impact (treatment vs. control tenants).
ZenUml/conf-app
Decide and publish the E2E test scope when creating or updating a conf-app PR. Queue full-suite or unresolved decisions for manual test triage.
ZenUml/conf-app
Prepare or refresh the reviewer-facing evidence at the top of a PR. Use when creating/updating a PR, reporting validation, marking it ready, or when the user asks for PR Review Support Material, before/after evidence, or review screenshots. Complements validate-branch; does not replace its checks or authorize merging.
ZenUml/conf-app
Focused production validation for the AI Repair flow in diagram editors: syntax error banner, AI Repair modal, asynchronous fix-diagram job polling, editable diff, Apply Code, and save/render after applying the repair. Invoked by release-app Step 2.6 when AI repair, SyntaxErrorBox, GenerateService, diagramly fix-diagram, or validation/error-surface commits are detected. Triggers on "pvt-ai-repair", "test ai repair", "validate ai repair", "repair broken diagram".
ZenUml/conf-app
Focused production validation for the Graph (DrawIO) macro: nested Forge + DrawIO iframes, title field, at least one shape on the canvas (required — avoids false PASS on empty diagrams), Publish from inner editor, and verified rendered geometry on the Confluence page. Invoked by release-app Step 2.6 when graph/drawio-related commits are detected. Triggers on "pvt-drawio", "test drawio", "validate graph macro".
ZenUml/conf-app
Focused production validation for the macro edit path (Forge custom UI modal, editor mount, Publish). Confirms opening Edit from the viewer loads the editor iframe and can publish or cancel without blank states. Invoked by release-app Step 2.6 when editor-related commits are detected. Triggers on "pvt-edit", "test macro edit", "validate editor", "pvt-editor".
ZenUml/conf-app
Focused production validation for macro fullscreen / expanded viewer (Forge fullscreen modal bridge). Opens fullscreen from the viewer toolbar, verifies the diagram remains usable, then exits cleanly. Invoked by release-app Step 2.6 when fullscreen-related commits are detected. Triggers on "pvt-fullscreen", "test fullscreen", "validate fullscreen viewer".
ZenUml/conf-app
Focused production validation for the paywall modal across both trigger paths: Edit (existing) and Fullscreen viewer (added 2026-05-17). Tests every interactive element, every dismissal path, post-dismiss state per trigger, and Mixpanel events (upgrade_modal_shown, paywall_triggered with action_type={page_editor,fullscreen_viewer}, advocacy_message_copied with ui_component=modal, paywall_continued_editing). Invoked automatically by release-app Step 2.6 when paywall-related commits are detected. Triggers on "pvt-paywall", "test paywall", "validate paywall".
ZenUml/conf-app
Focused production validation for the OpenAPI / Swagger macro: insert or open editor, set title, publish, and verify rendered spec viewer in the Forge iframe. Invoked by release-app Step 2.6 when swagger/openapi-related commits are detected. Triggers on "pvt-swagger", "test openapi", "validate swagger macro".
ZenUml/conf-app
Focused production validation for manual syntax-error repair in code-based diagram editors: syntax error detection, SyntaxErrorBox visibility, direct human correction in the editor, error clearing, preview render, save, and published render. Use this when parser validation, SyntaxErrorBox, editor validation, error-surface, Mermaid/ZenUML/PlantUML/OpenAPI syntax handling, or non-AI repair commits ship. Triggers on "pvt-syntax-repair", "test syntax repair", "validate syntax error repair", "manual syntax repair", or "repair syntax error without AI".
ZenUml/conf-app
Guard-rails for deriving aggregate claims ("X% of diagrams are abandoned", "cross-space duplication is rare") from stored product data — D1 CustomContent bodies, Mixpanel events, any bulk store. Use when analyzing diagram content at scale, counting defaults/templates/unused content, measuring duplication or reuse, joining content to tenants, or whenever a percentage derived from a LIKE/GROUP BY query is about to drive a roadmap decision. Triggers on "analyze the data", "how many diagrams", "what fraction", "abandoned", "unedited defaults", "cross-space", "duplicate content", "query CustomContent".
ZenUml/conf-app
Mark a conf-app PR Ready for Review after validating its current E2E decision, or run its approved E2E scope while keeping it Draft.
ZenUml/conf-app
Release one named ZenUML Forge variant (lite, full, diagramly/dia, asyncapi/async/api) to production. The script selects the draft, enforces the canary gate, publishes, and waits for production smoke. Use when the user asks to release, deploy, ship, or promote a named variant, or asks for `release-app preflight`.
ZenUml/conf-app
Rendering performance analysis for ZenUML macros. Queries Mixpanel macro_viewed duration_ms percentiles by macro type, compares against baseline, and guides investigation of regressions or improvements. Usage: /rendering-perf Triggers on "rendering performance", "how fast do macros render", "p50 p90 p99", "duration_ms baseline", "render time regression".
ZenUml/conf-app
Reproduce a bug in the conf-app. Extract the bug from the current conversation or user prompt, then try to reproduce it in the simplest available environment. Use when the user says "repro", "reproduce", "can you repro this", "reproduce the bug", "verify this bug", or describes a bug they want confirmed. Try environments in strict order: local dev server first, then conf-stg-lite.zenuml.com, then conf-lite.zenuml.com, then real Confluence as last resort.
ZenUml/conf-app
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.
ZenUml/conf-app
Ad hoc, AI-driven verification of a specific behavior — not a checked-in E2E test. Use after developing a feature, fixing a bug, validating a branch, or post-release. Drives agent-browser for Forge iframe UI, or CLI for backend/analytics signals. Triggers on "spot check", "run a spot check on X", "spot check this fix", "spot check on staging", "spot check zenuml-lite@stg", "verify on staging".
ZenUml/conf-app
Push the current branch and create or reuse a PR on ZenUml/conf-app. Use when the user says "submit", "create PR", "push and PR", "open a pull request", "submit branch", or wants to publish their work as a PR without merging. Classify its E2E scope with pr-labeling, then babysit executable CI; unresolved scope enters manual test triage. Does not merge — use land-pr for that.
ZenUml/conf-app
Read and triage the ZEN service-desk queue on zenuml.atlassian.net — what tickets are open, who is waiting on a reply, which granted extensions are about to expire. Use for any QUEUE-shaped question: "any new tickets", "who is waiting on me", "did this tenant ever file a ticket", "what came in since a given date", "工单", "谁在等回复", "有没有新工单", or when a paywall/churn analysis needs the support-ticket signal. Read-only. To FULFIL a specific request (write the KV licence, draft the reply) use `extend-space-license` instead. Discriminator, one rule: the question names a specific ticket or hands over a request to fulfil uses `extend-space-license`; the question is about the queue, a time window, "anything new", or who is waiting uses this skill.
ZenUml/conf-app