landing-report

Read version queue data across Conductor workspaces without mutations.

1|Updated Apr 26, 2026

Search Tags:#pull-request #landing-report #version-queue #queue-dashboard #workspace-aware #pr-versions #ship-next

Ready to run

npx skills add https://github.com/tblakex01/conductor-playground --skill landing-report-tblakex01

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/tblakex01/conductor-playground/tree/main/.claude/skills/gstack/landing-report
Command: npx skills add https://github.com/tblakex01/conductor-playground --skill landing-report-tblakex01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only visibility into the version slot and ship readiness landscape for workspace-aware Conductor setups, enabling quick understanding without mutating state.

Core Features & Use Cases

Read the current version queue across multiple workspaces and PRs to identify what is claimed and what is available.
See which sibling Conductor workspaces have WIP work likely to ship soon, and what slot/ship would be picked next.
Use when asked for "landing report", "what's in the queue", or "which version do I claim next" to get a snapshot.

Quick Start

Invoke the landing-report skill to display the current version queue for your workspace.

Frequently Asked Questions about landing-report

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

FAQPage Schema

How do I view which version slots are claimed by open pull requests?▼

To view which version slots are claimed by open pull requests, you need a read-only version queue dashboard. This Skill surfaces a snapshot of claimed slots, ships, and PRs across multiple workspaces to guide your next steps without mutating state.

What is a landing report in a workspace-aware environment?▼

A landing report is a read-only snapshot of version queue data in workspace-aware environments. It shows which version slots are claimed by open PRs and identifies which workspaces are likely to ship next.

How do I determine which version to claim next across multiple workspaces?▼

You determine which version to claim next by reading the current version queue across multiple workspaces and PRs. The snapshot identifies what slots are claimed and what is available to pick next.

Can I see which sibling workspaces have work in progress that will ship soon?▼

Yes, you can see which sibling Conductor workspaces have work in progress that is likely to ship soon. The version queue displays the slot and ship readiness status to indicate what would be picked next.

Does generating a queue dashboard modify my repository state?▼

Generating a queue dashboard does not modify your repository state. The Skill operates without mutations and provides a strictly read-only snapshot of slots, ships, and PRs.