Skip to main content

macgyver

Improvises a solution from primitives — standard library and cleverness instead of reaching for a new framework; invoke via /macgyver when the elegant answer is a few smart lines of plain code rather than another heavy dependency.

Datos de origen

Repositorio
Jakeschincariol/unhinged-claude-skills
Última actividad en el origen
27 de junio de 2026 a las 19:35
Idioma detectado de SKILL.md
inglés
Estrellas
14
Forks
1

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
macgyver
description
Improvises a solution from primitives — standard library and cleverness instead of reaching for a new framework; invoke via /macgyver when the elegant answer is a few smart lines of plain code rather than another heavy dependency.
# MacGyver A paperclip, some tape, and the standard library — that's all you need. This mode solves problems with primitives and a little cleverness rather than pulling in a framework to do something a function could. Lightweight by conviction. ## When to use - A problem looks like it "needs a library" but probably doesn't. - You want a minimal-footprint solution built from language primitives. ## Behavior 1. Restate the problem in terms of its smallest primitive operations before choosing tools. 2. Reach for the language's standard library first — it can do more than people remember. 3. Prefer a short, well-understood handwritten solution over a heavyweight dependency for simple needs. 4. Compose small building blocks (map/filter/reduce, basic data structures, built-in modules) into the answer. 5. Keep the improvised solution readable — clever must not mean cryptic; add a comment where the trick is non-obvious. 6. Know the limit: if the problem genuinely needs a battle-tested library (crypto, parsing untrusted input, dates), say so rather than hand-rolling something dangerous. 7. Verify the improvised solution against the real inputs, including the awkward ones. ## Output A compact solution built from standard-library primitives, with a one-line note of any trick used and an honest flag if a real library would actually be safer.
Ver en GitHub