agentleFS
garroshubgarroshub/MixCut-Skill/SKILL.md

mixcut

Skill7 starsChanged 10 months agoApache-2.0View on GitHub

Create short mixed-cut videos from YouTube clips with automated analysis, clipping, and professional subtitle processing.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 9 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check if the user has provided ALL of the following:

    line 22
  2. Very specific:

    If ANY of these are missing, you MUST use the AskUserQuestion tool to obtain them.

    line 31
  3. Distinctive:

    DO NOT assume defaults. DO NOT start downloading until configuration is complete.

    line 32
  4. Distinctive:

    DO NOT start downloading until configuration is complete.

    line 33
  5. Distinctive:

    Gather Sources: Ask for YouTube URLs from the user.

    line 40
  6. Very specific:

    Ensure the directory ./work exists in the project root.

    line 42
  7. Very specific:

    Configuration: Create ./work/mixcut_config.json with global settings and source clip metadata (start, end, title).

    line 56
  8. Distinctive:

    Deduplication: Remove repeated words, stutters, and verbal fillers ("uh", "um", "you know").

    line 68
  9. Very specific:

    Synchronize: Run python skills/mixcut/scripts/process_mixcut.py "./work/mixcut_config.json" --action generate_srt to sync changes to …

    line 72
  10. Very specific:

    Use the remotion skill to render the project located in skills/mixcut/remotion.

    line 76
  11. Very specific:

    Verify ./work/outputs/final_mixcut.mp4 exists and has a file size > 0.

    line 84
  12. Distinctive:

    Troubleshooting: If files are missing or empty, identify the failure point in previous phases and re-run the necessary steps.

    line 86
  13. Very specific:

    Retention Policy: Do NOT delete the ./work directory until the user explicitly confirms the results or you have verified the outputs …

    line 90
  14. Distinctive:

    Path Management: Always use absolute paths when delegating tasks to external skills.

    line 95
  15. Distinctive:

    Cross-Platform: Avoid hardcoding drive letters.

    line 96
  16. Distinctive:

    Performance: Use parallel tool calls for independent download/analysis tasks where supported.

    line 97

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MixCut Skill

CRITICAL INSTRUCTION: MANDATORY CONFIGURATION

You MUST NOT proceed to downloading or processing until the Project Configuration is fully defined.

Step 1: The Configuration Gate Check if the user has provided ALL of the following:

  • Video Title: Main title for intro and segment cards.
  • Caption Language: Target language for subtitles (e.g., English, etc.). Crucial: No bilingual output.
  • Aspect Ratio: 16:9 (Desktop), 9:16 (Shorts/TikTok), or 1:1.
  • Target Duration: 30s, 60s, 120s, or 180s.
  • Pace: Fast, Medium, or Slow.
  • Style: Highlight Montage or Beat-cut.
  • Transitions: none, fade, slide, flash, or glitch.

If ANY of these are missing, you MUST use the AskUserQuestion tool to obtain them. DO NOT assume defaults. DO NOT start downloading until configuration is complete.


Workflow

Phase 1: Sources & Workspace Setup

  1. Gather Sources: Ask for YouTube URLs from the user.
  2. Setup Workspace:
    • Ensure the directory ./work exists in the project root.
    • Prepare ./work/assets and ./work/outputs subdirectories.

Phase 2: Content Analysis

For each YouTube URL provided:

  1. Download:
    • Run python skills/Youtube-clipper-skill/scripts/download_video.py <url> "./work/assets/youtube"
  2. Analyze:
    • Run python skills/Youtube-clipper-skill/scripts/analyze_subtitles.py <subtitle_path>
  3. Selection:
    • Present analyzed chapters/highlights to the user.
    • Confirm which segments to include in the final cut.

Phase 3: Assembly & Processing

  1. Configuration: Create ./work/mixcut_config.json with global settings and source clip metadata (start, end, title).
  2. Processing:
    • Run python skills/mixcut/scripts/process_mixcut.py "./work/mixcut_config.json"
    • This script automates clipping, media normalization (ffmpeg), and generates the initial timeline.json and final.srt.

Phase 4: Professional Subtitle Cleaning (Agent-Driven)

This phase ensures high-quality, professional subtitles.

  1. Read Timeline: Access ./work/timeline.json.
  2. Subtitle Optimization: Iterate through all subtitle entries and apply the following cleaning logic:
    • Remove Noise: Strip speaker markers (e.g., >>, >>>) and sound cues (e.g., [Music], [Applause]).
    • Deduplication: Remove repeated words, stutters, and verbal fillers ("uh", "um", "you know").
    • Flow Improvement: Merge fragmented phrases into natural, readable sentences.
    • Professional Polish: Refine text into the target language using appropriate technical terminology.
  3. Update: Save the optimized content back to ./work/timeline.json.
  4. Synchronize: Run python skills/mixcut/scripts/process_mixcut.py "./work/mixcut_config.json" --action generate_srt to sync changes to final.srt.

Phase 5: Rendering

  1. Delegate to Remotion:
    • Use the remotion skill to render the project located in skills/mixcut/remotion.
    • Provide the absolute path to ./work/timeline.json as input props.
    • Set output to ./work/outputs/final_mixcut.mp4.

Phase 6: Delivery Guard & Verification

Mandatory verification before completion.

  1. Integrity Check:
    • Verify ./work/outputs/final_mixcut.mp4 exists and has a file size > 0.
    • Verify ./work/outputs/final.srt exists and has a file size > 0.
  2. Troubleshooting: If files are missing or empty, identify the failure point in previous phases and re-run the necessary steps.

Phase 7: Completion & Cleanup

  1. Report: Provide the paths to the final video and subtitle files.
  2. Retention Policy: Do NOT delete the ./work directory until the user explicitly confirms the results or you have verified the outputs physically.

Technical Guidelines

  • Path Management: Always use absolute paths when delegating tasks to external skills.
  • Cross-Platform: Avoid hardcoding drive letters; use system-agnostic path resolution.
  • Performance: Use parallel tool calls for independent download/analysis tasks where supported.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.