studio-setup
Skill1 starsChanged 42 days agoMITView on GitHub
AI Handout Studio をこの環境に入れる。更新のあとに流し直してもよい(SETUP のゲームブックを doctor に沿って進め、最初に進み具合のチェックリストを見せる)
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Melvynx/video-agent-skillstheir own version, first seen Oct 15, 2026
- scrollmark/social-skillstheir own version, first seen Oct 14, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Melvynx/video-agent-skills★ 126same name
- scrollmark/social-skills★ 19same 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- pull-requestSkill
- studio-uninstallSkill
- ai-handout-studioSkill
- question-sheetSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
If ok is true: if you finished any section in this run, show the checklist again (step 1).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Set up AI Handout Studio in this environment by following the setup game book. Speak the user's language throughout. Running it again later (for example after git pull) is safe: doctor stops only at what is missing or not decided yet.
- In the repository root, run
node scripts/doctor.mjs --checklistand show its output to the user as it is (a Markdown checklist: one line per section, what is done and which section comes next). Do this first, before anything else. - Run
node scripts/doctor.mjs --json. - If
okistrue: if you finished any section in this run, show the checklist again (step 1). Tell the user the setup is complete, mention eachwarncheck with its detail, and stop. - Otherwise, read the section numbered
next.sectioninSETUP.md(inSETUP.ja.mdif the user speaks Japanese) and do what it says.next.reasonsays what is missing. - At the end of the section, go back to step 2.
Keep the promises in section 1 of SETUP.md: ask only about the choices that doctor reports as missing or outdated, get the user's consent before editing their agent instructions or shell configuration, and never use sudo. SETUP.md is the only source of what each section does, so read it instead of guessing.
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.

