preview
Skill0 starsChanged 42 days agoMITView on GitHub
Show before choosing: caption style comparisons rendered on the user's own footage, candidate-moment preview sheets, Luxury graphics snapshots, draft renders and contact/cut sheets — so choices are made from real frames, not style names.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- botifyex/previewtheir own version, first seen Nov 8, 2026
- jisuzzzz/haechitheir own version, first seen Nov 8, 2026
- Kangentic/kangentictheir own version, first seen Nov 7, 2026
- lodev09/react-native-true-sheettheir own version, first seen Nov 1, 2026
- gr219/OpenBA-Kittheir own version, first seen Oct 25, 2026
- spmtitsolution/OpenBA-Kittheir own version, first seen Oct 20, 2026
Used with
Projects with it also use ml-training-recipe, replication and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
getcompanion-aiSkillml-training-recipe
Find implementable ML training recipes from papers, datasets, docs, and code. Use when the user wants to fine-tune, train, reproduce, or choose a practical ML method, dataset, hyperparameter setup, or benchmark recipe.
Also in 3 projects that use this
getcompanion-aiSkillreplication
Plan a replication of a paper, claim, or benchmark, and execute only after an explicit environment choice. Use when the user asks to replicate results, reproduce an experiment, verify a claim empirically, or build a replication package.
Also in 3 projects that use this
brainbytes-devSkillalpha-research
Also in 3 projects that use this
JaimeParkerSkillpaper-code-audit
Perform three-way cross-validation of a research paper by comparing the original paper text (via Zotero), official code implementation (via Git), and personal Obsidian notes. Use this skill whenever the user wants to "audit a paper", "verify paper claims against code", "cross-check notes with implementation", "triangulate paper + code + notes", "find discrepancies between paper and code", or mentions wanting a deep, structured comparison of a paper's claims against its implementation and their own notes. Also trigger when the user asks to "analyze this paper thoroughly" with code available, or when they want to systematically reconcile what the paper says, what the code does, and what their notes claim.
Also in 3 projects that use this
JimLiuSkillpdf-explore
Use this skill when the user has attached a PDF, paper, report, or other document and the answer needs content from more than one place in it: summarize the methods or any other section, compare sections, find where a topic is discussed, read a value or label off a figure or chart, or find/list/extract every instance of something across the whole document (datasets, benchmarks, citations, figures, table rows, accession numbers — including appendices). Skip it only for a single lookup of 1–4 pages quoted in your very next response — `read_file(pages=[...])` attaches pages as images that are dropped from context after one turn, so multi-section answers end up re-reading the same ranges repeatedly. Parses the PDF once in the Python kernel: `pdf_pages` (pages as persistent text), `pdf_outline` (TOC), `pdf_scan` (rank pages by relevance), `pdf_map`/`pdf_extract` (per-page summary / structured fields via parallel haiku calls). For PDF creation/manipulation, use reportlab/pypdf directly.
Also in 3 projects that use this
KISHOR403Skillsession-search
This skill should be used when searching Claude Code session transcripts with semantic understanding. Triggers on queries like "find sessions about X", "when did I work on Y", "search previous conversations". Supports natural language queries with synonym matching.
Also in 3 projects that use this
- +1 more from getcompanion-ai
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- advaitpaliwal/feynman★ 10ksame name
- companion-inc/feynman★ 10ksame name
- getcompanion-ai/feynman★ 10ksame name
- lodev09/react-native-true-sheet★ 2.1ksame name
- nextflow-io/training★ 277same name
- typv/nest-turbo-starter★ 224same name
- Kangentic/kangentic★ 140same name
- kv0906/pm-kit★ 138same name
- spmtitsolution/OpenBA-Kit★ 38same name
- sanghun0724/cmux-claude-skills★ 33same name
8 more not listed
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 repository19 other files it gives its agents.
- analyzeSkill
- audioSkill
- captionsSkill
- clipSkill
- creator-editSkill
- designSkill
- directorSkill
- doctorSkill
- editSkill
- exportSkill
- graphicsSkill
- ingestSkill
- luxury-techSkill
- quality-checkSkill
- reframeSkill
- reviseSkill
- studioSkill
- style-learningSkill
- transcribeSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
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 40
Always read the produced images before describing or asking about them.
“Common” is measured: kept by at least 6 in 10 of the 10 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
Preview
Rules: ${CLAUDE_PLUGIN_ROOT}/references/rules.md · CLI: ${CLAUDE_PLUGIN_ROOT}/references/cli.md.
ss = "${CLAUDE_PLUGIN_ROOT}/bin/shorts-studio". Input: $ARGUMENTS
0. Engine check
The commands below run the Shorts Studio engine. Installed as the Claude Code plugin it is already
present and shorts-studio is on the Bash PATH. If shorts-studio doctor is not found (for example,
this skill was added with npx skills add), ask the user before installing anything, then:
- Claude Code:
/plugin marketplace add bloxy-studios/shorts-studio→/plugin install shorts-studio@shorts-studio. - Other agents:
git clone --depth 1 https://github.com/bloxy-studios/shorts-studio ~/.shorts-studio/engineand read every${CLAUDE_PLUGIN_ROOT}path below as~/.shorts-studio/engine.
Then run shorts-studio doctor --setup once (project-local runtime; never sudo or global installs).
Steps
| Need | Command | Then |
| Caption styles | ss preview captions <project> --range 0:23.3-0:30.2 [--styles a,b,…] | Read caption-styles.jpg; ask with AskUserQuestion (≤ 4 options, recommended first) |
| Candidate moments | ss candidates preview <project> --top N | Read each sheet; correct titles/boundaries (candidates note) |
| Luxury graphics | ss luxury preview <project> --clip <id> | Read each run's contact sheet |
| Draft edit | ss render <project> --clip <id> --draft | Read qa/contact.jpg and qa/cuts.jpg |
Always read the produced images before describing or asking about them. Pick a short, representative range for caption previews (≥ 2 chunks, includes a highlighted word).
Completion check
The user (or, in autonomous mode, the log) has a choice grounded in images you actually inspected.
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.

