library
Skill6 starsChanged 28 days agoMITView on GitHub
Grow and look after the BashCut library: make a missing preset, effect, transition, look, sticker or sound, harvest what to keep after an edit, fix, copy or prune items. Triggers: "thiếu hiệu ứng", "không có cái nào hợp", "tạo preset", "lưu lại", "dùng lại lần sau", "để dành", "xong rồi".
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Edge-City/agentvillage-skillstheir own version, first seen Nov 1, 2026
- shipshitshow/skillstheir own version, first seen Oct 15, 2026
- atopile/atopiletheir own version, first seen Oct 8, 2026
- enkerewpo/zoresearchtheir own version, first seen Apr 30, 2026
- CodeWithBehnam/cc-docstheir own version, first seen Mar 15, 2026
- disler/the-librarytheir own version, first seen Mar 15, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- atopile/atopile★ 4ksame name
- disler/the-library★ 421same name
- CodeWithBehnam/cc-docs★ 2same name
- Edge-City/agentvillage-skills★ 1same name
- enkerewpo/zoresearch★ 1same name
- shipshitshow/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- audio-mixSkill
- beat-cutSkill
- captions-textSkill
- color-gradeSkill
- edit-workflowSkill
- effectsSkill
- footage-surveySkill
- motion-graphicsSkill
- reviewSkill
- rough-cutSkill
- self-learnSkill
- setupSkill
- stock-imagesSkill
- style-studySkill
- visual-planSkill
- voiceoverSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Write it with
library add: when it is a recipe you can describe in numbers (below), or from a file you were given or made (a .cube LUT, a … - Very specific: line 92
Every item: a clear English --name (the ID comes from it), --tags for mood and use, --pack for a set (the user's channel).
- Distinctive: line 97
When the edit is done (after review, before or after export), look for work worth keeping.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Library: make, harvest, look after
Eight kinds: text-preset, sticker, effect-preset, transition-preset, look, audio, voice, clip
(footage), plus a brand kit. Four scopes, searched in this order: the project (.bashcut/library), this Mac
(user), plugin packs, built-ins (read-only).
- Save to the project by default; no approval needed.
--scope user(every project on this Mac) waits for the user's click in the app. Offer it for things the user will clearly want again (their channel's grade, their outro sound), and say it needs their click.
1. Something is missing: make it
- Check first:
library list --kind K --query "shake". A close item with other numbers is not missing: apply it with--set, or copy it withlibrary update ID --as NEW_IDand change the copy. - Ask a plugin:
library searchorlibrary generate(jobs; a paid provider:--dry-runfirst). Show the candidates, check the licence, thenlibrary add --from-result JOB:N. No provider (capabilities get library.generate --kind stickersays why): say so; installing or turning one on is the user's job. - Build it on the timeline, then save it (most reliable): make it with
bc:effects,bc:color-grade,bc:audio-mixorbc:captions-text, let the user approve, thenlibrary save-selection. - Write it with
library addwhen it is a recipe you can describe in numbers (below), or from a file you were given or made (a.cubeLUT, a PNG, an audio file). - Try it before calling it done:
library applyorlibrary placeit on a real clip, readui frame F(several frames for motion), ask the user to listen for sound, thentimeline undounless they keep it. A wrong value:library update ID --params '{...}'(a new version).
Writing each kind
library get ID on a built-in shows a working example of every kind; library add --help has every field.
Frames are timeline frames.
effect-preset: up to 32 steps run in order on the clip, up to 16 named parameters set on apply (--set
name=value); a step value "$name" takes the parameter. Positions are t (0–1, so the effect scales with the
clip) or frame (negative counts from the end).
bashcut library add --kind effect-preset --name "Shake hit" --tags punch,impact --params '{"parameters": {"zoom": {"default": 1.25, "min": 1.05, "max": 2}}, "steps": [{"op": "keyframes", "keys": {"zoom": [{"frame": 0, "value": "$zoom", "ease": "out"}, {"frame": 6, "value": 1}], "pan": [{"frame": 0, "value": -20}, {"frame": 2, "value": 20}, {"frame": 4, "value": -10}, {"frame": 6, "value": 0}]}}, {"op": "sfx", "sfx": "AUDIO_ITEM_ID", "frame": 0}]}'
bashcut library apply shake-hit --item CLIP --set zoom=1.4 --from 120 --to 150 --base-rev N| op | fields |
motion | preset (as clip motion --preset), or focus [x, y, w, h] (fractions) with focusTo, ease |
keyframes | keys {property: [{t or frame, value, ease}]}: zoom, pan, tilt, rotation, opacity |
speed / speedCurve | speed, keepDuration; preset or points |
reverse, freeze | freeze holds the frame at t or frame |
patch | item properties set as they are (transform, opacity, crop…) |
sfx | sfx (an audio item ID, or the preset's own --file), t or frame, volumeDb |
text | text, textPreset, t or frame, duration |
Speed steps break lip sync: tag such presets b-roll.
transition-preset: kind (any of the kinds in bc:effects "Transition kinds"), duration in frames (1–600),
easing, sfx (an audio item ID) or its own sound as --file.
bashcut library add --kind transition-preset --name "Snap whip" --params '{"kind": "whip", "duration": 6, "easing": "in", "sfx": "AUDIO_ITEM_ID"}'look: {"color": {...}} with an optional .cube as --file (make one with grade.py in bc:color-grade;
look at its preview first).
audio: needs --file; library add measures length and picks music or sfx, library analyze ID (job) fills
BPM and loudness. Tag mood and use (calm, whoosh, outro) after the user listened (library preview ID).
{"loopable": true} only for a bed that loops without a click.
sticker: an emoji ({"emoji": "🎉", "textPreset": "bold-outline"}), or a PNG/WebP with transparency or a
.mov with alpha (HEVC alpha or ProRes 4444). GIFs place as their first frame for now; Lottie is not supported.
Pictures from the web: bc:stock-images.
clip: a B-roll shot or still kept for reuse (--file); other params (a generator's model, prompt) are
kept. library place ID --track OVERLAY --at-frame F --duration N copies it into clips/. Generated ones:
library generate "<shot>" --kind clip when a provider serves it (bc:stock-images).
text-preset: textPreset, text, optional textStyle and animation (a clip motion preset).
save-selection keeps size, position, outline, font, colours and the motion preset (hand-made keys are dropped).
A font from a project's fonts/ folder is not copied with the preset: fonts import it in the next project
(bc:captions-text).
brand: palette, fonts, logo and mascot (sticker items: add the user's own images as stickers first),
voice, disclosure, every field optional. Only from what the user gave or approved; never invent a mascot and
present it as theirs. library apply ID (no --item) puts it on the whole project.
bashcut library add --kind brand --name "Acme" --params '{"palette": {"accent": "#F2B544", "text": "#2B1B0E", "background": "#EADBC4"}, "fonts": {"heading": "BeVietnamPro-Black"}, "logo": "acme-logo"}'Every item: a clear English --name (the ID comes from it), --tags for mood and use, --pack for a set (the
user's channel).
2. After an edit: harvest
When the edit is done (after review, before or after export), look for work worth keeping. Never save silently.
- From
timeline get, list candidates:- a grade the user approved (adjustment or clip colour, with its LUT) →
look; - a keyframed move, speed ramp or freeze you built by hand →
effect-preset; - the same transition kind and length at 3+ cuts, or one In/Out used on many items →
transition-preset; - an SFX or music bed that fit and is not already a library item →
audio; - an image or alpha overlay used as a sticker →
sticker.
- a grade the user approved (adjustment or clip colour, with its LUT) →
- Skip what came from the library already, one-off fixes (a crop for one bad shot) and anything the user complained about.
library list --kind Kandlibrary stats --kind K: skip a duplicate of a saved item; when it improves one, proposelibrary update IDinstead.- Propose at most five, each with name, kind, scope and why it is reusable. Save only what they say yes to, with
library save-selection --kind K --name N --item ID(--scope userfor their channel's items).
Nothing worth keeping: say so in one line.
3. Look after it
- Correction. The user changed an item's result by hand, or undid it right after
library apply/library place: proposelibrary update ID --params '{...}'(a new version; the old stays in its history). Built-in or plugin:library update ID --as NEW_ID, and record a preference to use the copy. - Wrong place.
library move ID --to user(approval) or--to project. - Prune.
library statslists saved items nobody used and duplicates. At the end of a session offer to remove or merge them; never remove without a yes (library remove ID; user scope waits for approval). Removing keeps files the timeline still uses. - Share.
library export-pack --output DIR --pack NAME; the other side runslibrary import-pack DIR --scope user.
Report
What was made or saved (name, kind, scope), what was tried and undone, what waits for the user's approval.
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.

