landing-report

Display landing queue and version slots claimed by open PRs across Conductor workspaces.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill landing-report-alejandrofigini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/AlejandroFigini/artist-portfolio/tree/main/.agent/skills/landing-report
Command: npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill landing-report-alejandrofigini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The landing-report skill provides a read-only dashboard to summarize the current version queue and which workspace-aware ship slots are claimed by open PRs. It helps teams quickly assess what is in flight and what would ship next without making changes.

Core Features & Use Cases

  • Display a live snapshot of version slots and PR allocations across Conductor workspaces.
  • Identify which slots are claimed, which are open, and what the next candidate ship is.
  • Use in planning meetings to communicate release readiness and bottlenecks without mutating code or config.

Quick Start

Invoke the landing-report skill to display the current landing/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 in my landing queue are claimed by open PRs?

You can view version slots claimed by open PRs by generating a read-only landing queue report. The dashboard surfaces workspace-aware ship slots, branch states, and the next candidate ship across Conductor workspaces for quick release planning.

What is a read-only landing queue dashboard used for in release planning?

A read-only landing queue dashboard is used to assess release readiness without mutating code or configuration. It displays a live snapshot of PR allocations and version slots, helping teams identify bottlenecks and communicate ship status during planning meetings.

Can I check release readiness across Conductor workspaces without modifying code?

Yes, you can check release readiness without modifying code by invoking a read-only landing report. It reads existing configuration and PR metadata to present current workspace contexts, branch states, and upcoming ship candidates safely.

How do I find the next ship candidate from my current workspace version queue?

To find the next ship candidate, generate a landing report for your workspace context. The dashboard identifies which version slots are open, which are claimed by open PRs, and surfaces the next upcoming ship candidate.

Does the landing report dashboard support mutating branch states during planning meetings?

No, the landing report dashboard does not support mutating branch states. It is strictly a read-only view designed to surface version queue status, PR metadata, and workspace contexts for decision-making without applying changes.