Skill Live Processing logo

Skill Live Processing

Organization
IAPro-Community
skill-live-processing

Use for live stream and VOD ingestion pipelines, including YouTube, Twitch, uploads, capture jobs, queues, transcription, clip generation, media storage, retries, idempotent workers, consent, validation, observability, and safe server-side provider credentials.

Overview

PublisherIAPro-Community
RepositoryOrquestrador-Maestro
Skill nameskill-live-processing
Stars
63
Forks
11
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by IAPro-Community on GitHub. Read the source before you install it.

Installation

Install the Skill Live Processing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/IAPro-Community/Orquestrador-Maestro/tree/v1/codex/skills/skill-live-processing
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/IAPro-Community/Orquestrador-Maestro.git /tmp/Orquestrador-Maestro
mkdir -p .claude/skills
cp -r /tmp/Orquestrador-Maestro/codex/skills/skill-live-processing .claude/skills/skill-live-processing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Skill Live Processing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Skill Live Processing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Skill Live Processing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Live Processing

Use this skill for live streams, long VODs, and media pipelines that produce transcripts, summaries, clips, thumbnails, captions, or publishable assets.

Pipeline Contract

  1. Separate ingestion, processing, enrichment, review, and publishing into explicit stages.
  2. Keep platform OAuth tokens, webhook secrets, storage credentials, AI provider keys, and signing keys server-side.
  3. Validate source ownership, platform terms, tenant quota, duration, codec, file size, language, and processing options before enqueueing.
  4. Create a durable media_jobs record before downloading or running expensive work.
  5. Run long work in queues or workers. Do not download, transcode, transcribe, or render inside request handlers.
  6. Make every stage idempotent and resumable from stored artifacts, checksums, stage status, and provider job IDs.
  7. Store source media and generated assets in private storage. Use signed URLs with short TTLs for preview and download.
  8. Batch and chunk AI work. Reuse transcript segments, embeddings, shot boundaries, and thumbnails instead of resending full media context.
  9. Require review before publishing clips or generated metadata unless the product has explicit auto-publish consent.
  10. Emit structured progress, queue age, stage duration, retry count, artifact checksums, and sanitized failure reasons.

Stage States

Use stable states such as:

queued, validating, downloading, extracting_audio, transcribing, detecting_clips, rendering, review_ready, publishing, published, failed, cancelled.

Data Model Hints

  • media_jobs: tenant ID, owner ID, source type, source URL or asset ID, status, current stage, progress, idempotency key, retry count, error class.
  • media_assets: job ID, kind, storage path, duration, size, checksum, codec, metadata, retention deadline.
  • clip_candidates: job ID, timestamps, score, reason, transcript excerpt hash, review status.
  • processing_events: job ID, stage, status, duration, worker ID, details.

Verification

  • Test webhook ingestion, duplicate webhook, cancelled job, worker crash and resume, provider timeout, quota exceeded, invalid media, signed URL expiry, and publishing gate behavior.
  • Confirm platform and provider secrets are not exposed in clients or logs.

Related Skills

  • skill-smart-clip-detection
  • skill-manual-video-processing
  • skill-ai-orchestration
  • skill-unified-analytics

Frequently asked questions

What does the Skill Live Processing AI skill do?

Use for live stream and VOD ingestion pipelines, including YouTube, Twitch, uploads, capture jobs, queues, transcription, clip generation, media storage, retries, idempotent workers, consent, validation, observability, and safe server-side provider credentials.

Why use Skill Live Processing on TypingMind?

Because you install it once and use it with any model. Skill Live Processing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Skill Live Processing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/IAPro-Community/Orquestrador-Maestro/tree/v1/codex/skills/skill-live-processing. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Skill Live Processing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Skill Live Processing?

As many as you like. As long as a model supports skills, you can use Skill Live Processing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Skill Live Processing AI skill free?

Yes. It is published on GitHub by IAPro-Community under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇