Field Notes

Community

Dragoon0x

field-notes

Structured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.

Overview

Publisher	Dragoon0x
Repository	`taste-skills`
Skill name	`field-notes`
Stars	6
Forks	3
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Dragoon0x on GitHub. Read the source before you install it.

Installation

Install the Field Notes AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Dragoon0x/taste-skills/tree/main/skills/evaluation/field-notes
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Dragoon0x/taste-skills.git /tmp/taste-skills
mkdir -p .claude/skills
cp -r /tmp/taste-skills/skills/evaluation/field-notes .claude/skills/field-notes

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Field Notes in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Field Notes on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Field Notes is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Field Notes

The format for making taste observations legible.

How to use

/field-notes Write a structured taste breakdown of a product in this conversation.
/field-notes <product> Analyze the specified product using the field notes format.

Constraints

Field Note Structure

Product name, URL, date, category
What it's trying to be (2-3 sentences. Not what it does. What experience it's trying to create.)
Three things that work (specific decisions with principles behind them)
One thing that doesn't (specific decision with reasoning and impact)
The taste principle (one sentence: "This product demonstrates that...")
Tags (principle-based tags for the reference library)

Writing Rules

MUST be specific. Reference actual elements, sizes, and interactions.
MUST connect every observation to a principle.
MUST include at least one thing that doesn't work. No product is perfect.
SHOULD be under 500 words. Concise analysis is harder and more useful than exhaustive analysis.
NEVER write a field note about a product you haven't actually used.

Anti-Patterns

Writing only about famous products everyone has already analyzed
Describing what the product does instead of how it feels to use
Listing features instead of evaluating decisions
Being uniformly positive (honest analysis includes what falls short)

Frequently asked questions

What does the Field Notes AI skill do?

Why use Field Notes on TypingMind?

Because you install it once and use it with any model. Field Notes is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Field Notes in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Dragoon0x/taste-skills/tree/main/skills/evaluation/field-notes. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Field Notes?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Field Notes?

As many as you like. As long as a model supports skills, you can use Field Notes with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Field Notes AI skill free?

Yes. It is published on GitHub by Dragoon0x under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Skill Host Compat

affaan-m

CommunityPopular

Lint ECC skills for Codex/Cursor-safe frontmatter and Claude-only substitutions before a skill PR.

Brand Voice

Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants…

Competitive Platform Analysis

affaan-m

CommunityPopular

Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong…

Content Engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Field Notes

How to use

Constraints

Field Note Structure

Writing Rules

Anti-Patterns

Frequently asked questions

Related AI Skills

Set up your own AI workspace now