agentleFS
Kastalien-ResearchKastalien-Research/thoughtbox/.agents/skills/taste/SKILL.md

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

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.
  • MicrosoftSkill

    council

    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

  • StrayDragonSkill

    ui-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

  • BlockSkill

    frontend-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

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
  1. Distinctive:

    If the verdict becomes clear at any step, stop.

    line 40

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Evaluate this research direction: $ARGUMENTS

Process

1. Determine Evaluation Depth

Based on the proposal, select the appropriate depth:

SituationOperations
Vague idea, needs sharpeningCompression test only
Specific technical proposalLandscape + Dead-end estimation
Major resource commitmentFull pipeline (all 6 operations)
Stuck, need fresh anglesCross-pollination only
Choosing between optionsPrediction 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.