skills
CLAUDE.md1 starsChanged 3 months agoMITView on GitHub
This repo is a collection of agent skills, one per subfolder containing a SKILL.md. When a session starts inside this repo, or when a user pastes an install prompt pointing at it, run this onboarding immediately: This copies only that skill into ~/.claude/skills/ so it is available in every future chat (use --codex for Codex). Re-running it later updates that skill only. If this is a sparse checkout without install-skills.mjs, copy the skill folder into ~/.claude/skills/<skill-name>/ directly — that is…
In this repository24 other files it gives its agents.
- ai-automation-contractsSkill
- brand-mascotSkill
- business-ai-auditSkill
- content-diarioSkill
- fable-5-protocolSkill
- hook-generatorSkill
- kieai-minimax-h3Skill
- lead-finderSkill
- mercadolibre-publisherSkill
- motion-reel-ingestSkill
- motion-reel-pipelineSkill
- motion-reelSkill
- pdf-markitdownSkill
- post-for-meSkill
- reel-pipelineSkill
- reels-referentesSkill
- replykaro-automation-communitySkill
- replykaro-automationSkill
- resource-pageSkill
- social-carousel-generatorSkill
- social-video-producerSkill
- soloduenos-leadsSkill
- video-animation-workflowSkill
- web-builderSkill
The file
Files
Skills collection — agent onboarding
This repo is a collection of agent skills, one per subfolder containing a SKILL.md. When a session starts inside this repo, or when a user pastes an install prompt pointing at it, run this onboarding immediately:
- Identify the skill the user wants. If they already named one (the install prompts in each skill's README do), use it. Otherwise list the available skills (folders with a
SKILL.md, or the table inREADME.md) and ask. Never install skills the user did not choose, and never touch skills they already have installed. Install it permanently with the bundled installer:
node install-skills.mjs <skill-name>This copies only that skill into
~/.claude/skills/so it is available in every future chat (use--codexfor Codex). Re-running it later updates that skill only. If this is a sparse checkout withoutinstall-skills.mjs, copy the skill folder into~/.claude/skills/<skill-name>/directly — that is all the installer does.To update an already-installed skill,
git pulland re-run the same installer command: it preserves the skill's installednode_modules, records the installed commit in.installed-from.json, and prints the old and new commits so you can summarize the changes for the user.node install-skills.mjs <skill-name> --checkreports whether the installed copy is behind this checkout (exit 3 = update available) without installing anything.node install-skills.mjs <skill-name> --removeuninstalls: it deletes only that skill's installed copy (never the repo folder, other skills, or the user's project folders) — only run it when the user explicitly asks to remove the skill.- Confirm the skill loads, then briefly explain — in the user's language — what it does and how it is used, based on the skill's own README.
- Offer to start the first job right away. For
social-video-producer, ask whether they want a full script-to-video production or an assembly from existing clips/audio. For assembly, offer to fillsocial-video-producer/PROMPT-template.mdtogether: ask for each placeholder value conversationally, show the filled prompt, and ask "Do I apply this prompt and start?" before proceeding. - Check requirements for the chosen skill (Node, ffmpeg, Playwright, API keys per its README) and help set up anything missing.
Once a job starts, always respect the skill's own approval gates and hard rules.
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.

