work-jiang-ingest-fallback

Recovers blocked lecture ingestion workflows by switching failed transcript retrieval to targeted fallback ingest processing.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/rbtkhn/grace-mar --skill work-jiang-ingest-fallback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-jiang-ingest-fallback
Source: https://github.com/rbtkhn/grace-mar/tree/main/.cursor/skills/work-jiang-ingest-fallback
Command: npx skills add https://github.com/rbtkhn/grace-mar --skill work-jiang-ingest-fallback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves blocked lecture ingestion workflows when full transcript retrieval fails due to rate limits while preserving auditability and validation.

Core Features & Use Cases

  • Fallback Ingest Workflow: Switches from unreliable channel-wide transcript fetching to a targeted local index approach for individual lectures.
  • Validation Support: Guides operators through ingest execution, metadata checks, argument validation, and comparative validation steps.
  • Use Case: When a new lecture cannot be ingested because transcript fetching returns repeated rate limits, use this Skill to perform a bounded recovery ingest with explicit provenance.

Quick Start

Use the work-jiang-ingest-fallback skill to recover a blocked lecture ingest using a targeted local index and validate the resulting artifacts.

Frequently Asked Questions about work-jiang-ingest-fallback

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

FAQPage Schema
How do I recover a blocked lecture ingest when transcript fetching fails?

Recover a blocked lecture ingest by switching from channel-wide transcript fetching to a targeted local index approach for individual lectures. This fallback workflow executes a bounded recovery ingest while preserving auditability and validation.

What is a fallback workflow for lecture transcript imports?

A fallback workflow for lecture transcript imports is a bounded recovery process that replaces failed channel-wide retrieval with a targeted local index. It requires explicit transcript provenance, local index overrides, ingest execution, and post-ingest validation checks.

Why does lecture metadata validation fail after a transcript rate limit?

Lecture metadata validation fails after a transcript rate limit because the primary retrieval path is blocked, leaving incomplete data. Applying a fallback ingest workflow restores the missing artifacts and enables post-ingest validation checks to verify metadata integrity.

How do I validate lecture transcripts after a fallback ingest?

Validate lecture transcripts after a fallback ingest by following the guided post-ingest validation steps, which include metadata checks, argument validation, and comparative validation to ensure the recovered artifacts meet provenance and auditability requirements.

When should I use a targeted local index instead of channel-wide transcript retrieval?

Use a targeted local index instead of channel-wide transcript retrieval when a new lecture cannot be ingested due to repeated rate limits. This approach provides explicit provenance and bounded operational recovery for individual lecture pipelines.

Does the lecture ingest fallback workflow require explicit transcript provenance?

Yes, the lecture ingest fallback workflow requires explicit transcript provenance. It also requires local index overrides, ingest execution, and post-ingest validation checks to ensure a reliable and auditable recovery process.