finding-agent-runs

Locate GitHub Actions runs triggered by fullsend agents using issue or pull request numbers.

Updated May 31, 2026
One-click install
npx skills add https://github.com/ascerra-fullsend-rehearsal/fullsend --skill finding-agent-runs-ascerra-fullsend-rehearsal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finding-agent-runs
Source: https://github.com/ascerra-fullsend-rehearsal/fullsend/tree/main/internal/scaffold/fullsend-repo/skills/finding-agent-runs
Command: npx skills add https://github.com/ascerra-fullsend-rehearsal/fullsend --skill finding-agent-runs-ascerra-fullsend-rehearsal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you identify and trace GitHub Actions runs for fullsend triage, code, or review agents when results are missing or you need to review a specific workflow run.

Core Features & Use Cases

  • Trace Workflow Runs: Find the exact workflow runs for GitHub Actions triggered by fullsend agents.
  • Event-Based Dispatches: Identify runs triggered by specific events like issue_comment, issues, and pull_request_target.
  • Search and Match: Search through runs by timestamp to match with specific events or comments.
  • Logs and Artifacts: Access logs and download artifacts from the workflow runs.
  • Use Case: If you've received a report that an agent workflow didn't complete successfully, use this Skill to locate the specific run and review its logs.

Quick Start

Run the finding-agent-runs skill with the issue number or PR number to find the corresponding GitHub Actions runs.

Frequently Asked Questions about finding-agent-runs

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

FAQPage Schema
How do I find GitHub Actions runs triggered by fullsend agents for a specific issue?

You can trace GitHub Actions runs triggered by fullsend agents by providing the specific issue or pull request number to retrieve the corresponding workflow run details and logs for troubleshooting.

What types of GitHub events can I trace for agent workflow runs?

You can trace GitHub Actions runs triggered by events like issue_comment, issues, and pull_request_target to identify specific workflow dispatches initiated by fullsend triage, code, or review agents.

How do I access logs and artifacts from a GitHub Actions run triggered by an agent?

After locating the specific GitHub Actions run using the issue or PR number, this Skill enables you to access the workflow run logs and download artifacts for post-mortem analysis.

Can I search GitHub Actions runs by timestamp to match a specific agent event?

Yes, you can search through GitHub Actions runs by timestamp to match workflow executions with specific events or comments triggered by fullsend agents for accurate run tracing.

Do I need the GitHub API and CLI to trace missing agent workflow runs?

Yes, this Skill operates within the GitHub API and CLI ecosystem to locate and retrieve specific GitHub Actions runs triggered by fullsend agents when results are missing or incomplete.

Why did my fullsend agent workflow fail to complete successfully on GitHub Actions?

If an agent workflow did not complete successfully, use this Skill to locate the specific GitHub Actions run by issue or PR number and review its logs to diagnose the failure.