draft-preguntas-entrevista-musica
Skill0 starsChanged 16 days agoNo licenceView on GitHub
Investiga a un ejecutivo, operador o fundador de la industria musical y genera un draft de 15 preguntas a la medida para entrevistarlo en un podcast de la industria de la música. Úsalo SIEMPRE que el usuario pida "preguntas para una entrevista", "preparar una entrevista de música", "draft de preguntas", "investigar a un invitado", o pegue el nombre/cargo/LinkedIn de alguien de la industria musical a quien va a entrevistar, aunque no diga la palabra "skill". El usuario entrevista a líderes de la industria musical en LATAM (ejecutivos de majors, fundadores y operadores de sellos independientes, managers, distribuidores/DSP, publishing/sync, music-tech). La entrevista gira en torno al perfil del invitado y busca aportar VALOR A LA INDUSTRIA desde su operación, mejores prácticas, experiencia y lecciones aprendidas; debe ser de talla mundial, profunda y humana, nunca corporativa ni genérica. (Distinto del skill de negocios/tech/liderazgo: este es específico de música.)
In this repository23 other files it gives its agents.
- draft-preguntas-entrevistaSkill
- find-skillsSkill
- hou-pythonSkill
- hou-rsSkill
- hou-vexSkill
- remotion-best-practicesSkill
- remotion-captionsSkill
- remotion-createSkill
- remotion-docsSkill
- remotion-interactivitySkill
- remotion-mapsSkill
- remotion-markupSkill
- remotion-multimediaSkill
- remotion-renderSkill
- remotion-saasSkill
- remotion-studioSkill
- sc-designerSkill
- td-flyer-audioreactivoSkill
- td-glslSkill
- td-glsl-vertexSkill
- td-popsSkill
- td-pythonSkill
- td-vj-builderSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
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 372,429 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.

