evidence-video-kit
Skill1 starsChanged 39 days agoNo licenceView on GitHub
Turn real business evidence - Excel/spreadsheet exports, Power BI/PDF reports, real email or Outlook screenshots, real internal HTML tools/dashboards, and live public APIs (GitHub/npm stats) - into board-deck-ready or launch-ready HyperFrames video assets. Four patterns it knows: (1) animated data/stat visuals with count-up numbers and chart reveals sourced from actual spreadsheet or dashboard data, (2) mockup "typing" animations of real email/document correspondence with narration-friendly pacing and highlighter-marker emphasis on key figures, (3) continuous-scroll "product tour" walkthroughs of real internal tools/dashboards (actual HTML platforms, not slide decks) using one virtual-camera pass instead of scene-cuts, (4) quick-hit cards - one-sentence stat cards with live-fetched date-stamped numbers, staggered list cards, and reusable parameterized series/intro cards - as full-frame MP4 or transparent alpha overlays for placing on footage. Use this whenever Evyatar needs to turn client or business proof - ROI numbers, adoption stats, real tool screenshots, real correspondence - into presentation video evidence for board decks, investor updates, client case studies, ROI reports, workshop deliverables, or sales enablement. Trigger on Hebrew: "תעשה מזה אנימציה", "תהפוך את הדאטה לוידאו", "אנימציה לדשבורד", "וידאו הוכחה", "תדגים את הפלטפורמה", "סיור וידאו בכלי", "אנימציית מייל", "תנפיש את האקסל הזה"; English: "animate this spreadsheet", "turn this dashboard into a video", "product tour of our tool", "email typing animation", "data video from this report", "board deck animations", "proof video from real data". Skip when the ask is a generic branded launch teaser/opener with no real data or tool to recreate (use hyperframes-launch-video instead), raw recorded footage needs trimming or captioning (use agent-video-editor), or the deliverable is a slide deck file rather than a video (use presentation-from-content or slideshow-from-photos).
In this repository16 other files it gives its agents.
- my-video/AGENTS.mdAGENTS.md
- my-video/CLAUDE.mdCLAUDE.md
- analyse-problemSkill
- caption-from-videoSkill
- cause-and-effectSkill
- content-strategySkill
- copywritingSkill
- emailsSkill
- eventsSkill
- frontend-designSkill
- hebrew-captions-hyperframesSkill
- lead-magnetsSkill
- remotion-best-practicesSkill
- socialSkill
- stop-slopSkill
- whySkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.