ecom-video-workflow
Skill4 starsChanged 37 days agoMITView on GitHub
Use when analyzing local ecommerce videos, extracting shot and subtitle
In this repository29 other files it gives its agents.
- analysis-report-orchestratorSkill
- chatlab-analyzerSkill
- document-to-markdownSkill
- ecom-image-reverse-sop-shareSkill
- ecom-main-image-diagnosisSkill
- ecom-market-insight-tableSkill
- ecommerce-competitor-analyzerSkill
- ecommerce-data-analysis-workflowSkill
- ecommerce-review-analysisSkill
- ecom-one-photo-pageSkill
- ecom-page-plannerSkill
- ecom-product-assets-collectorSkill
- ecom-ranking-main-image-collectorSkill
- external-skill-adapterSkill
- feishu-project-weekly-reportSkill
- frontend-design-systemSkill
- full-spectrum-distillerSkill
- github-repo-dissectorSkill
- kolsprite-tiktok-opsSkill
- manim-hyperframes-videoSkill
- rpa-flow-architectSkill
- sellersprite-amazon-opsSkill
- top10stats-data-videoSkill
- video-producer-coreSkill
- webbridge-archive-publisherSkill
- web-collection-orchestratorSkill
- wechat-account-data-reviewSkill
- wechat-article-knowledge-packSkill
- wechat-group-insight-reportsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Never invent product efficacy, certifications, sales, reviews, or performance uplift.
- Distinctive: line 19
Use FFmpeg/FFprobe only when available.
≈ “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.
Files
Ecommerce Video Workflow
Route the task to analysis, single-video planning, or campaign-level planning.
- For an existing local video, extract duration, shots, visible claims, subtitles, pacing, and risks. Read
references/ecom-video-evidence-analysis.md. - For one deliverable, create storyboard, voiceover, subtitles, prop list, and acceptance checks. Read
references/ecom-video-planner.md. - For a content matrix, map audience, pain point, benefit, proof, format, and shooting priority. Read
references/ecom-marketing-video-planner.md. - Never invent product efficacy, certifications, sales, reviews, or performance uplift.
- Store assets and outputs under
./outputs/ecommerce\video.
Use FFmpeg/FFprobe only when available. If missing, report the dependency before attempting deterministic media extraction. Resolve the current Python runtime for bundled scripts.
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
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.