landing-report

Display a read-only VERSION queue dashboard from repository context and gstack data.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/nhattran998/personal-athlete-agent --skill landing-report-nhattran998
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/nhattran998/personal-athlete-agent/tree/main/.agents/skills/gstack-landing-report
Command: npx skills add https://github.com/nhattran998/personal-athlete-agent --skill landing-report-nhattran998

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a read-only snapshot of the workspace VERSION queue, showing which slots are claimed by open PRs and which Conductor workspaces have work in progress so you can plan shipping without making changes.

Core Features & Use Cases

  • Read-only dashboard that lists current VERSION slot assignments and pending work across sibling Conductor workspaces.
  • Quick visibility into which version would be claimed next, enabling informed planning and risk assessment.
  • Safe planning aid: no mutations to the repository; data is sourced from the current workspace context and gstack tooling.

Quick Start

Ask for the landing report to display the current VERSION queue snapshot without mutating the repository.

Frequently Asked Questions about landing-report

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

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

To check which version slots are claimed by open pull requests, you can view a read-only VERSION queue dashboard that displays current slot assignments and pending work across sibling Conductor workspaces.

What is a read-only version queue snapshot for ship planning?

A read-only version queue snapshot is a safe planning aid that shows current VERSION slot assignments and pending Conductor workspace work, enabling informed planning and risk assessment without mutating the repository.

How do I see which workspace will ship next without modifying the repository?

You can see which workspace will ship next without modifying the repository by requesting a landing report, which renders a read-only snapshot of the current VERSION queue state sourced from repository context and gstack data.

Can I use this to claim the next available version slot for my pull request?

You cannot claim the next available version slot for your pull request using this tool, because it is strictly a read-only dashboard that displays queue status and does not perform any mutations to the repository.

Does the landing report require gstack tooling to display the queue status?

The landing report relies on repository context and gstack data sources to render the current VERSION queue state, so gstack tooling is required to display the queue status accurately.

Why does my landing report show no pending work in the version queue?

Your landing report shows no pending work in the version queue because it renders a read-only snapshot of the current state, meaning there are currently no open pull requests claiming version slots or active Conductor workspaces with work in progress.