fsx-pipeline-report

Generate FSX pipeline operation reports from Bits run data.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/eatbreads/.agents --skill fsx-pipeline-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fsx-pipeline-report
Source: https://github.com/eatbreads/.agents/tree/main/skills/fsx-pipeline-report
Command: npx skills add https://github.com/eatbreads/.agents --skill fsx-pipeline-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Help on-call and operations teams quickly transform Bits pipeline run data for a fixed set of FSX watched pipelines into a concise, operator-friendly report and group notification so incidents and failed steps are visible immediately without manual aggregation.

Core Features & Use Cases

  • Focused monitoring: Fetch the latest runs for FSX duty-owned pipelines, map run and job statuses, and surface only pipelines that need attention.
  • Two-layer reporting: Produce a short summary for fast scanning and a detailed failed-step list for operator follow-up, plus Markdown and JSON artifacts for archival.
  • Feishu integration: Optionally sync summary and detail tables to Feishu Base and send a group message or interactive card, with user→bot fallback for send scope issues.

Quick Start

Use the fsx-pipeline-report skill to fetch the watched FSX pipelines from Bits, generate summary and detail artifacts under /tmp/fsx-pipeline-report, and send a concise Feishu group summary.

Frequently Asked Questions about fsx-pipeline-report

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

FAQPage Schema
How do I generate Feishu pipeline reports from Bits run data?▼

To generate Feishu pipeline reports from Bits run data, you fetch the latest runs for FSX duty-owned watched pipelines, map run and job statuses, and produce concise summaries with failed-step lists. The process outputs Markdown and JSON artifacts for archival.

What is the best way to send a failed pipeline summary to a Feishu group?▼

The best way to send a failed pipeline summary to a Feishu group is using lark-cli based IM operations. The mechanism sends a group message or interactive card detailing failed steps, utilizing a user-to-bot fallback for send scope issues.

Do I need a service-account secret to fetch FSX pipeline runs from Bits?▼

Yes, you need a service-account secret to fetch FSX pipeline runs from Bits. The pipeline report generation requires service-account secret resolution and a cloud JWT exchange to authenticate Bits API calls with specific headers.

Can I sync pipeline operation reports to a Feishu Base automatically?▼

Yes, you can sync pipeline operation reports to a Feishu Base automatically. The process uses lark-cli based Base operations to sync both the short summary and the detailed failed-step list directly into Feishu Base tables.

Where are the Markdown and JSON artifacts stored during pipeline report generation?▼

During pipeline report generation, the Markdown and JSON artifacts are stored under the /tmp/fsx-pipeline-report directory. These artifacts contain the short summary and detailed failed-step list for operator follow-up and archival.