landing-report

Displays a read-only dashboard of gship workspace/version/ship-queue statuses from open PRs across Conductor workspaces.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill landing-report-xotong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/gstack/skills/landing-report
Command: npx skills add https://github.com/xotong/claude-marketplace --skill landing-report-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only dashboard that surfaces workspace-aware queue state for gstack, showing which VERSION slots are claimed by open PRs, which Conductor workspaces have WIP work likely to ship, and what would be next to ship. It provides a snapshot without mutating any state, enabling teams to understand backlog and plan releases.

Core Features & Use Cases

  • Read-only version and ship queue snapshot across workspaces.
  • Visualize claimed slots, in-flight work, and upcoming ship candidates to avoid conflicts.
  • Use when asked for current queue status, open PR visibility, or next-version recommendations.

Quick Start

Ask for the landing report to display the current workspace/version queue snapshot.

Frequently Asked Questions about landing-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I visualize which version slots are claimed by open pull requests?

You can visualize claimed version slots by generating a read-only landing report that surfaces workspace-aware queue state, showing which open PRs hold specific VERSION slots and what work is in-flight across Conductor workspaces.

What is a read-only version queue dashboard for gstack workspaces?

A read-only version queue dashboard is a snapshot of workspace state that highlights WIP work likely to ship soon, indicates which slot or ship would be chosen next, and operates with no mutations to the existing state.

How do I check the next version to ship across multiple Conductor workspaces?

To check the next version to ship, request a landing report to display the current workspace version queue snapshot, which identifies upcoming ship candidates and indicates which slot or ship would be chosen next.

Can I see open PR versions and ship queue status without mutating any workspace state?

Yes, you can see open PR versions and ship queue status without mutations. The landing report operates as a read-only dashboard that loads context when activated by triggers like landing report or show open PR versions.

Does the landing report dashboard work across all Conductor workspaces?

Yes, the landing report dashboard applies across all Conductor workspaces, providing a unified read-only snapshot of the version queue and highlighting WIP work likely to ship soon to help avoid release conflicts.

When should I use a read-only landing report instead of directly querying the ship queue?

Use a read-only landing report when you need to understand backlog and plan releases without altering state. It provides a conflict-free snapshot of claimed slots, in-flight work, and upcoming ship candidates.