fehr-clarity-taste-strategy
Skill5 starsChanged 13 days agoApache-2.0View on GitHub
Turn brand and creative strategy discussions into clear positioning, distinctive creative choices, and consistent delivery using Sophia Marie Fehr's public principles and three meeting questions. Use for brand reviews, positioning, creative briefs, product concepts, and leadership sparring.
In this repository168 other files it gives its agents.
- abel-sell-the-alphaSkill
- agent-governance-gap-analysisSkill
- agent-infra-fixerSkill
- agent-receiptSkill
- agent-skills-gapSkill
- ai-dnaSkill
- ai-festival-posterSkill
- ai-teamSkill
- albro-founder-brandSkill
- anatomySkill
- andy-raskin-strategic-narrativeSkill
- ar-aging-and-cash-applicationSkill
- asshauer-performance-contentSkill
- autonomous-researchSkill
- awwwards-sitesSkill
- better-typographySkill
- bourgoin-why-we-buySkill
- brain-scanSkill
- brath-b2b-demand-frameworkSkill
- braun-poke-the-bearSkill
- broll-pickerSkill
- claritySkill
- client-commsSkill
- cli-ux-reviewSkill
- clone-my-voiceSkill
- clone-yourselfSkill
- costa-negotiation-dynamicsSkill
- crawler-access-auditSkill
- cv-job-matchSkill
- data-globeSkill
- decision-ledgerSkill
- denney-persona-angle-formatSkill
- dicks-homework-five-secondSkill
- domain-uptime-monitorSkill
- dreyer-funnel-diagnosisSkill
- dry-three-copy-testsSkill
- dunford-obviously-awesomeSkill
- edge-find-skillsSkill
- fede-cloneSkill
- fede-voiceSkill
- fitzpatrick-mom-testSkill
- flores-founder-content-machineSkill
- founders-handbookSkill
- foxwell-meta-creativeSkill
- frankus-geo-auditsSkill
- gahan-b2b-creator-blueprintSkill
- galloway-youtube-outlier-packagingSkill
- generate-imageSkill
- geo-dominationSkill
- gerhardt-founder-brandSkill
- german-taxes-elsterSkill
- goetz-challenger-marketingSkill
- greger-creator-squadSkill
- handley-everybody-writesSkill
- harness-firstSkill
- hire-founding-engineerSkill
- hott-ugly-adsSkill
- http-error-triageSkill
- hubspot-crm-cleanupSkill
- humanizerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
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 20
Frame the decision: Read method: Intake and evidence.
- Distinctive: line 28
Find the lived core: Follow method: Core before expression.
- Distinctive: line 30
Make positioning a choice: Use method: Position and exclusions.
- Distinctive: line 32
Define taste in context: Use method: Taste as selection.
- Distinctive: line 36
Compare and edit: Use method: Decision rules and edge cases and worked examples.
- Distinctive: line 40
Review before handoff: Run checklists/review-checklist.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
FEHR: Clarity, Taste, Strategy
Based on Sophia Marie Fehr's public method. Not affiliated with or endorsed by Sophia Marie Fehr.
When to use
Use this skill when a team has attractive creative work but an unclear brand promise, a positioning statement that staff cannot explain, competing audience assumptions, or a strategy meeting that produces discussion without decisions. It also supports product development, hospitality concepts, channel briefs, and leadership sparring where brand choices must translate into everyday behavior.
The deliverable is a concise decision brief: the decision and its authority, three diagnostic answers, a supported brand core, chosen audience, one-sentence position, creative criteria, delivery requirements, and next actions. Adapt its length to the assignment. For a narrow creative review, evaluate the supplied positioning and recommend changes within the requested scope. For a full strategy assignment, complete the whole brief.
Read references/method.md first. Its evidence labels distinguish Fehr's public principles, a third-party account of her work, and this package's practical adaptations. The recurring questions are paraphrased from the supplied LinkedIn post's three publicly accessible images. They are one verified installment of a recurring format, not a claim that every installment uses the same questions. Consult references/sources.md for provenance before attributing a claim.
Procedure
- Frame the decision. Read method: Intake and evidence. Identify the requested output, business tension, available evidence, constraints, and decision deadline. Separate observations from assumptions. Ask only for missing inputs that affect the recommendation; use clearly marked hypotheses when useful work can proceed.
- Establish decision authority. Apply the first diagnostic in method: Three meeting questions. Identify who can approve the specific choice today and the limits of that mandate. If authority is absent, produce a recommendation and identify the unresolved decision rather than recording fictional agreement.
- Test internal clarity. Apply the second diagnostic in method: Three meeting questions. Ask whether a new employee could explain the brand's position in one sentence. Diagnose ambiguity in the position before polishing communications. Mark an unperformed employee test as pending.
- Choose the customer horizon. Apply the third diagnostic in method: Three meeting questions. Distinguish the customer served today from the customer the organization wants to attract. State which one guides this decision and what a transition would require.
- Find the lived core. Follow method: Core before expression. Extract repeatable strengths, customer benefits, and credible behaviors from the supplied material. Identify what matters and what can be omitted. Avoid turning a desired future attribute into a present fact.
- Make positioning a choice. Use method: Position and exclusions. Write one plain sentence connecting audience, promise, and credible distinction. State the alternative audience, offer, or behavior being deprioritized. If no distinctive evidence exists, recommend discovery or product improvement.
- Define taste in context. Use method: Taste as selection. Translate the position into concrete creative criteria for imagery, language, collaborations, materials, or space. Explain each choice's relationship to the audience and promise. Identify familiar category codes that would make the work interchangeable.
- Connect promise to delivery. Apply method: Strategy as continuity. Specify what the product, service, team, and channels must do to support the position. Identify fragile promises that depend on one leader's presence and repair those dependencies before claiming consistency.
- Compare and edit. Use method: Decision rules and edge cases and worked examples. Compare plausible options against clarity, distinctiveness, and deliverability. Remove additions that weaken the promise. Keep commercial or ethical tensions visible when relevant to the brief.
- Write the decision brief. Fill templates/output-template.md. Lead with the recommendation and status, explain the supporting choices, and assign proportionate actions with owners and review points. Include uncertainties and what evidence would change the recommendation.
- Review before handoff. Run checklists/review-checklist.md. Repair failed checks and report any unresolved dependency. Do not imply Fehr reviewed the work, invent business results, or treat a strategy recommendation as permission to publish or contact people.
Files in this skill
- SLUG.txt: Package identifier for naming and discovery.
- SKILL.md: Entry point, use cases, and eleven-step workflow.
- references/method.md: Principles, paraphrased meeting questions, decision rules, and attribution boundaries.
- references/sources.md: Nine fetched public sources, contributions, and research limitations.
- examples/worked-examples.md: Two invented illustrations showing weak drafts, improved briefs, and applied rules.
- templates/output-template.md: Deliverable structure with field-by-field instructions.
- checklists/review-checklist.md: Pass/fail quality gates and common failures with fixes.
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.

