temporary-id-safe-output

Resolve temporary IDs to real issue numbers in workflow runs.

4.9k|489|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/github/gh-aw --skill temporary-id-safe-output-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: temporary-id-safe-output
Source: https://github.com/github/gh-aw/tree/main/skills/temporary-id-safe-output
Command: npx skills add https://github.com/github/gh-aw --skill temporary-id-safe-output-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables reliable referencing of temporary IDs generated within a single workflow run, allowing agents to link newly created issues before actual numbers are available.

Core Features & Use Cases

  • Temporary ID mapping between create_issue and linking jobs.
  • Resolve temporary IDs to real issue numbers in subsequent steps without exposing sensitive data.
  • Safe, non-fatal handling of resolution failures with warnings and summaries.
  • Easy integration with GH_AW_TEMPORARY_ID_MAP env variable and dynamic needs.

Quick Start

Use this skill to enable temporary IDs in safe output workflows. After the create_issue job produces a temporary ID, use the map to resolve it to the actual issue number for linking or annotation tasks.

Frequently Asked Questions about temporary-id-safe-output

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

FAQPage Schema
How do I reference a GitHub issue number in a workflow before it is created?

Temporary ID mapping resolves generated placeholders to actual issue numbers within a single workflow run. It allows agents to link newly created issues before actual numbers are available using a shared map via environment variables and job outputs.

How do I pass temporary IDs between create_issue and linking jobs in GitHub Actions?

Pass temporary IDs by sharing a temporary ID map via the GH_AW_TEMPORARY_ID_MAP environment variable and dynamic needs. This propagates the map to subsequent steps to resolve placeholders to actual issue numbers for linking tasks.

What happens when temporary ID resolution fails in a safe output workflow?

Failed temporary ID resolution triggers safe, non-fatal handling. The workflow issues warnings and generates summaries instead of failing the run, ensuring safe outputs are maintained without exposing sensitive data.

Can I use dynamic needs to resolve temporary IDs in GitHub Actions?

Yes, you can use dynamic needs to resolve temporary IDs. This skill specifically satisfies the use of dynamic needs alongside controlled environment propagation to map temporary placeholders to real issue numbers.

When do I need temporary ID mapping for safe outputs?

You need temporary ID mapping for safe outputs when a workflow creates and links issues in separate jobs. It allows reliable referencing of dynamically created issues before the actual issue numbers are available.