Rick Rubin — Taste as an Operating System
Judge decisions and artifacts by taste, not spec — reduction, the lean-in test, serve the work
- What
- Judge decisions and artifacts by taste, not spec — reduction, the lean-in test, serve the work
- Cost
- Free
- Needs
- none — no account, no API keys. You make decisions about creative or technical work and want a taste-led judgment framework.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the legendary producer's judgment, ported as an operating mentality rather than a persona: judge by taste, not by spec. The framework: strip the label and react to the artifact itself; the lean-in test (does it pull you in, or is it merely correct?); reduction (the least that makes the point — remove until one more cut would break it); recognition over origination (let the work tell you what it wants to become); serve the work, not your ego; discipline over waiting. Three non-negotiable gates: strip the label, the lean-in test, a reduction pass before shipping. Explicitly not cosplay — never quote him, impersonate him, or invoke his name as authority; the judgment runs silently in your normal voice. Discovered via skills.sh, listed here with credit to its creator by @vinny380. Honest caveats: a judgment framework, not a how-to — it changes how you decide, not what you make; subjective by design, no checklists or scores; pairs naturally with minimalist/YAGNI instincts but won't replace domain rigor. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Version:
Install
Prerequisites: none — no account, no API keys. You make decisions about creative or technical work and want a taste-led judgment framework. Install "Rick Rubin — Taste as an Operating System" for me. A judgment framework for decisions and artifacts: strip the label, the lean-in test, reduction to the least that makes the point, serve the work not the ego — running silently as a mentality, never as a persona. Repository: https://github.com/vinny380/rick-ruibin-skill/blob/main/skills/rick-rubin/SKILL.md 1. Fetch the SKILL.md file for the rick-rubin skill (and its reference files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "rick-rubin". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point it at a decision or artifact to judge, or say "rubin off" to stand it down). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.