agentleFS
Sign inStart free
Dragoon0xDragoon0x/taste-skills/skills/evaluation/self-assessment/SKILL.md

self-assessment

Skill5 starsChanged 8 months agoMITView on GitHub

Diagnose your taste gaps across six skill areas. Know what to practice. Use when starting a taste development program, checking progress, or identifying specific areas to improve.

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    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:

    Collecting: Do you have an organized, principle-tagged reference library you can search in 60 seconds?

    line 21
  2. Distinctive:

    MUST retake every 3 months.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 8 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

Self-Assessment

Know your gaps. Practice the right thing.

How to use

  • /self-assessment Generate a taste self-assessment for the user.

Constraints

Six Skill Areas

Rate 1-5 on each:

  • Seeing: Can you spot spacing inconsistencies, hierarchy issues, and craft details without being told?
  • Comparing: Can you rank solutions and explain the ranking beyond personal preference?
  • Deconstructing: Can you reverse-engineer the constraints and decisions behind a design?
  • Collecting: Do you have an organized, principle-tagged reference library you can search in 60 seconds?
  • Articulating: Can you explain design decisions without saying "it feels right"?
  • Applying: Does your first design instinct usually turn out to be correct?

Interpreting Results

  • Lowest score = where to focus. Don't improve everything at once.
  • High Seeing + Low Articulating = good instincts, can't convince anyone. Focus on vocabulary.
  • High Collecting + Low Applying = great references, own work doesn't match. Focus on deconstruction.
  • Even scores across the board (all 2s or 3s) = the plateau. Go deep in any one area.
  • MUST retake every 3 months. Taste develops too slowly to notice daily.

Anti-Patterns

  • Overrating yourself on every dimension
  • Skipping the assessment and jumping straight to exercises
  • Focusing only on strengths instead of weaknesses

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.

Check your setup, free