Taste Report

What it does

When your agent uses it

• The user wants to see how they design — whats my taste
• Show me my taste report
• How do I decide
• What are my patterns

Example prompts

• “s my taste”
• “show me my taste report”
• “how do I decide”
• “/taste-report”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1Synthesise, don't transcribe. The value is in patterns across entries — "you always subtract," "you decide colour last" — not in…
2. 2Every claim cites evidence. Tie each observation to specific projects, overrides, or repeated decisions in the profile. No evidence, no…
3. 3Describe decision-making, not just preference. "Prefers muted palettes" is a lookup. "Decides colour last, after structure is settled" is…
4. 4Be honest about confidence and thinness. Distinguish strong, well-evidenced patterns from thin ones. Don't manufacture a richer picture…
5. 5Blind spots are a gift, not a verdict. Surface ruts and gaps gently, as questions. The goal is self-awareness, never a grade.
6. 6Stay in the personal layer. If a "preference" is really one client's brand requirement, it does not belong here.

What it can do on your machine

Read from SKILL.md and the folder at commit cb00757. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Taste Report loads about 1.4k tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 481 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~122

When it runs · the whole SKILL.md, loaded when a task matches

~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Owl-Listener/designpowers at commit cb00757, republished under its MIT licence (© Owl-Listener). 481 words, ~1,397 tokens.

name

taste-report

description

Use when the user wants to see how they design — "what's my taste", "show me my taste report", "how do I decide", "what are my patterns", or periodically as the personal profile matures. Generates a longitudinal, reflective report from the PERSONAL taste profile (design-memory) — recurring moves, tells, evolution, blind spots — that helps a designer understand their own instincts. Personal layer only: it never reports client-specific signals from any project's DESIGN.md

# How You Design — Taste Report
_Generated [date] · based on [N] projects · [X] strong opinions, [Y] soft patterns_

## In one line
[The single sharpest characterisation of their taste. e.g. "You're a restraint-first
designer who earns every accent and trusts whitespace to do the work."]

## How you decide
[3-5 observations about their decision-making, each with evidence from the profile.
Not what they like — HOW they choose. e.g.:
- "You subtract before you add — your overrides almost always remove an element
   rather than restyle it (4 of 5 recorded overrides)."
- "You decide colour last. Type and spacing are settled before accent appears."]

## What you reach for
[Recurring moves — the defaults they return to across projects. The strong opinions
and confirmed soft patterns, framed as instincts not rules.]

## What you reject
[The anti-patterns, synthesised into a point of view. e.g. "You reject anything that
performs friendliness — confetti, mascots, exclamation marks, skeleton 'delight'."]

## How your taste is evolving
[Movement over time from the project history. What's hardened from soft to strong,
what you've changed your mind about, what's newly appearing. e.g. "Your tolerance
for density has risen — early projects favoured sparse layouts, recent ones trust
the user with more on screen."]

## Possible blind spots
[Gentle, honest. Tendencies that could become ruts, or places the profile is thin.
e.g. "Every project leans editorial-serif for personality — worth testing whether
that's taste or habit." Frame as questions, not judgements.]

## Where the signal is thin
[What the profile doesn't yet know — areas with little evidence, so the designer
knows what's well-established vs. a guess. Honesty about confidence.]

© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/taste-report of Owl-Listener/designpowers.

Open the folder on GitHubat commit cb00757