taste
Skill64 starsChanged 5 months agoMITView on GitHub
Run a taste evaluation on a research proposal or technical direction. Determines whether to proceed, simplify, defer, or kill before committing research effort.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- hamzzaqureshi/gravidextheir own version, first seen Nov 8, 2026
- WingedGuardian/GENesis-AGItheir own version, first seen Nov 8, 2026
- ForeignerfromJupiter/foreigners-povtheir own version, first seen Nov 1, 2026
- renepf/claude-skillstheir own version, first seen Oct 25, 2026
- hhx465453939/agent-taste-seed-systemtheir own version, first seen Oct 25, 2026
- adityareddy-dev/deskstudiotheir own version, first seen Oct 25, 2026
Used with
Projects with it also use council, ui-ux-pro-max and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcouncil
Convene the persona panel — six orthogonal review lenses — on a target. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.
Also in 3 projects that use this
StrayDragonSkillui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- TryCaspian/caspian-sdk★ 935same name
- tryproduck/produck-skills★ 511same name
- senlindesign/taste-skill★ 330same name
- WingedGuardian/GENesis-AGI★ 100same name
- gavishap/omnia-vault★ 53same name
- adityareddy-dev/deskstudio★ 43same name
- leadgenjay/claude-skills★ 22same name
- alebgl77/claude-inc★ 21same name
- gongyijie85/dsh-ecc★ 8same name
- hhx465453939/agent-taste-seed-system★ 4same name
13 more not listed
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 repository102 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- assumptionsSkill
- capture-learningSkill
- Codex-opus-4-6-promptingSkill
- Codex-promptSkill
- mcp-code-modeSkill
- deploy-team-hubSkill
- diagramSkill
- distillSkill
- effect-tsSkill
- escalateSkill
- evalSkill
- experimentSkill
- hddSkill
- hub-auditSkill
- hub-collabSkill
- implementSkill
- knowledgeSkill
- peer-notebook-delivery-guardSkill
- research-taskSkill
- session-reviewSkill
- source-command-hdd-decideSkill
- source-command-hdd-hddSkill
- source-command-hdd-researchSkill
- source-command-hdd-stage-adrSkill
- source-command-hdd-validateSkill
- statusSkill
- supabaseSkill
- synthesizeSkill
- teamSkill
- test-suiteSkill
- theseus-protocolSkill
- thoughtbox:debugSkill
- thoughtbox:decisionSkill
- thoughtbox:evolutionSkill
- thoughtbox:knowledge-querySkill
- thoughtbox:onboardSkill
- thoughtbox:refactorSkill
- thoughtbox:researchSkill
- thoughtbox:session-reviewSkill
- thoughtbox-teamSkill
- ulc-loopSkill
- ulysses-protocolSkill
- workflow-brainstormingSkill
- workflow-ideationSkill
- workflow-reflectionSkill
- workflow-revisionSkill
- workflows-compoundSkill
- workflowSkill
- workflows-planSkill
- workflows-reviewSkill
- workflows-workSkill
- workflow-tournamentSkill
- assumptionsSkill
- capture-learningSkill
- claude-opus-4-6-promptingSkill
- claude-promptSkill
- mcp-code-modeSkill
- deploy-team-hubSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
If the verdict becomes clear at any step, stop.
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Evaluate this research direction: $ARGUMENTS
Process
1. Determine Evaluation Depth
Based on the proposal, select the appropriate depth:
| Situation | Operations |
| Vague idea, needs sharpening | Compression test only |
| Specific technical proposal | Landscape + Dead-end estimation |
| Major resource commitment | Full pipeline (all 6 operations) |
| Stuck, need fresh angles | Cross-pollination only |
| Choosing between options | Prediction query only |
2. Run Operations (in order, skip per above)
Compression Test — Force into: "We believe [X] because [Y], and if we're right, [Z] follows." If it can't survive compression, verdict is defer.
Landscape Assessment — Use WebSearch and Exa (web_search_exa) to find adjacent work, abandoned approaches, new capabilities. What exists? What changed recently?
Prediction Query — Simulate success and failure worlds. Is the direction informative under both outcomes?
Dead-End Estimation — What's the most likely failure mode? What's the time-to-signal (not time-to-completion)?
Simplicity Audit — Is there an 80%-value simpler version? Apply recursively.
Cross-Pollination — Check against other domains. Structural resonance = real signal.
3. Stop Early
If the verdict becomes clear at any step, stop. Don't run more operations just to fill out the report.
4. Output
## Taste Evaluation: [Title]
**Verdict:** proceed | simplify | defer | kill
**Rationale:** [One sentence]
**Compression:** [Single-sentence formulation]
**Landscape:** [Position relative to existing work]
**Prediction:** Success -> [X] / Failure -> [Y]
**Time-to-signal:** [Estimate]
**Simplification:** [Cheaper version, if any]
**Cross-domain:** [Analogies, if checked]
**Next step:** [Concrete action]Omit unchecked sections.
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.

