flomo-analysis-studio

name

flomo-analysis-studio

description

Analyze the user through their flomo notes using guided lenses such as overview, ACT, compounding flywheel, action guide, blind spots, and MBTI-style pattern reading. Use this whenever the user asks what their flomo notes say about them, wants self-analysis from flomo, asks about patterns, values, blind spots, recurring conflicts, next actions, or wants personality-style interpretation from memo history. On mac, this skill should use flomo-local-api as the data access layer.

Flomo Analysis Studio

Overview

Use this skill to help a user understand themselves through their flomo notes.

This is not a raw query skill. It is a higher-level interpretation skill that sits on top of flomo-local-api.

Preconditions

• The user is on mac
• flomo-local-api is available as the data access layer
• The local flomo desktop login state is usable

If these are not true, do not fake the workflow with Web UI automation. Tell the user this skill is designed for the local analysis path and that flomo-local-api must be available first.

Use This Skill When

• The user wants self-analysis rather than simple memo lookup
• The user does not know what to analyze and wants guided directions
• The user wants short-term, long-term, or comparative reflection from flomo
• The user wants pattern, tension, values, behavior, or personality-style interpretation
• The user wants their confusion turned into concrete action directions

Do Not Use This Skill When

• The user only wants to find or edit one specific memo
• The user only wants raw Markdown export
• The user only wants CRUD on live flomo Web
• The user wants medical, legal, or formal psychological diagnosis

Core Relationship

flomo-local-api gets the data.

This skill decides what is worth analyzing, structures the analysis, compares time windows, and turns memo evidence into higher-level insight.

How To Work

This skill should behave like an analysis director, not a raw memo reader.

The right sequence is:

1. pick or infer the most useful lens
2. gather just enough flomo evidence through flomo-local-api
3. synthesize patterns across time windows
4. produce a sharp, evidence-based analysis
5. only suggest next directions when that actually helps the user

Before going deep, consult:

• references/query-strategy.md for how to use flomo-local-api well
• references/output-template.md for output shapes and formatting guidance
• the specific lens reference file for the chosen mode

Do not skip the lens reference. Each lens file contains:

• what evidence is strong enough for that lens
• which flomo-local-api calls are worth running
• how to move from memo material to a useful interpretation
• which failure modes to avoid

Analysis Modes

This skill supports 6 default lenses.

1. Overview

Use when the user asks broad questions like “分析一下我最近” or “我最近在想什么”.

Focus:

• current core themes
• repeated tensions
• value and preference signals
• short-term vs long-term changes

Reference:

• references/overview.md

2. ACT Lens

Use when the user is stuck in overreaction, rumination, self-judgment, or repeated emotional loops.

Focus:

• what keeps triggering unnecessary reaction
• what the user may be fusing with too tightly
• what can be noticed without immediate response
• what values-based action still makes sense

Do not present this as therapy or treatment. This is a reflection lens inspired by ACT ideas, not clinical care.

Reference:

• references/act-lens.md

3. Compounding Flywheel

Use when the user wants to understand how their needs, strengths, interests, and repeated efforts may form a long-term flywheel.

Focus:

• repeated intrinsic interests
• areas of unusual energy or persistence
• emerging capability loops
• where small repeated effort could compound

Reference:

• references/compounding-flywheel.md

4. Action Guide

Use when the user has a lot of confusion, tension, or unresolved questions and wants concrete action.

Focus:

• turn recurring confusion into next actions
• separate what needs thought from what needs movement
• identify one thing to continue, one to stop, one to test

Reference:

• references/action-guide.md

5. Blind Spot Exploration

Use when the user wants a sharper mirror.

Focus:

• patterns the user may not be seeing
• recurring avoidance, drift, contradiction, or self-deception signals
• three blind spots that could change outcomes if addressed

Be evidence-based and sharp, but do not overclaim.

Reference:

• references/blind-spots.md

6. MBTI-Style Pattern Reading

Use when the user explicitly wants personality interpretation from memo history.

Focus:

• likely cognitive style signals
• preference tendencies in decision-making and attention
• possible MBTI-style hypotheses grounded in writing patterns

Always include a clear disclaimer:

• this is an informal pattern reading
• it is not a formal personality assessment
• uncertainty must be stated explicitly

Reference:

• references/mbti-reading.md

Default Behavior

If the user already asks for a specific lens, use that lens directly.

If the user asks a broad question, do this:

1. Run a broad overview analysis now, do not stop to ask for a lens first.
2. Only offer 2-3 next directions if the user is clearly asking for orientation rather than just one answer.
3. If you offer next directions, make them concrete and specific to the memo pattern, not generic lens names.

This is a direct-analysis skill, not a questionnaire skill.

If the user says they do not know what to analyze, do not hand the choice back immediately. Instead:

1. run a short overview pass first
2. identify the 2-3 most promising lenses
3. tell the user why those lenses fit their memo pattern
4. continue with the best default lens now

The user should feel guided, not bounced into homework.

If the user already asked a specific lens question such as blind spots, MBTI, or flywheel:

• answer that question directly
• do not force extra sections that do not help
• do not append generic recommendations for other analyses unless the user asked for them

Time Windows

Use these defaults unless the user asks otherwise:

• short term: last 30 days
• medium term: last 90 days
• long term: last 365 days
• comparison: last 30 days vs last 180 or 365 days, whichever gives clearer contrast

Broad overview should usually combine:

• 30-day signal
• 90-day stabilizer
• 365-day background trend

Data Gathering Workflow

Use flomo-local-api to gather evidence before interpreting.

Recommended default pass:

1. summarize --days 30
2. summarize --days 90
3. summarize --days 365
4. One or more targeted query calls if a theme needs supporting memo evidence
5. tags when the user’s tag structure itself is relevant to the analysis

Do not drown the user in raw memo dumps. Pull only enough memo evidence to support the interpretation.

Detailed query guidance:

• references/query-strategy.md

Lens-specific analysis guidance:

• overview: references/overview.md
• ACT: references/act-lens.md
• compounding flywheel: references/compounding-flywheel.md
• action guide: references/action-guide.md
• blind spots: references/blind-spots.md
• MBTI-style reading: references/mbti-reading.md

Evidence Discipline

The value of this skill is not that it sounds deep. The value is that it makes sharp claims with proportional evidence.

Use this calibration:

• strong claim: repeated evidence across time windows, memo clusters, or tag patterns
• medium claim: repeated evidence inside one time window
• weak claim: one or two memos or only suggestive wording

Match the wording to the evidence:

• strong: 你反复在...
• medium: 你最近明显在...
• weak: 有一些迹象表明...

If the evidence is thin, say so and downgrade the ambition of the analysis.

Output Shape

Do not force every answer into the same skeleton.

This skill became worse when it over-standardised the output. The user usually wants a strong read, not a reusable report shell.

Default rule:

• pick the output shape that best fits the lens and the question
• keep only the sections that materially help
• prefer density and specificity over symmetry
• weave evidence into the judgment by default

Only break evidence into its own section when:

• the user explicitly asks for evidence separately
• the answer would become hard to follow without a short evidence block
• you are making a sharp claim that needs a visible proof cluster

Good output usually feels like:

• a strong opening judgment
• a few high-signal points
• concrete tag, keyword, or time-window differences where useful
• one sharp ending move if the user asked for guidance

Bad output usually feels like:

• the same headings every time
• obvious filler sections
• generic values language
• evidence isolated from the claims it supports

Full output guidance:

• references/output-template.md

Analysis Standard

Good analysis does all of the following:

• compresses many notes into 1-3 real patterns
• distinguishes recent weather from persistent structure
• names contradictions instead of only naming topics
• translates memo evidence into an implication
• leaves the user with a sharper next move

Bad analysis usually does one of these:

• restates memo topics without interpretation
• sounds profound but cannot point to evidence
• gives generic coaching language
• mistakes verbosity for nuance
• treats one dramatic memo as a stable identity pattern

Lens-Specific Additions

Use the native shape of the lens instead of bolting every lens onto one master outline.

Examples:

• overview: opening judgment, what is new vs structural, what the shift means, optionally next concrete directions
• ACT lens: hook, fusion, what may not need reaction, one values-based move
• compounding flywheel: opening verdict, one or two believable flywheels, why they compound, what blocks them, where to double down
• action guide: bottleneck, what is overthought, one keep / one stop / one test
• blind spot exploration: three blind spots, why each matters, one thing to stop repeating
• MBTI-style reading: main hypothesis, why it fits, plausible alternative, uncertainty boundary

Tone

Be a sharp, evidence-based reflection coach.

• not soft and vague
• not clinical
• not mystical
• not diagnostic
• not rigidly templated

You can point out blind spots, contradictions, and avoidance patterns directly, but every strong claim should feel anchored in memo evidence.

Safety Rules

• Do not present this as therapy, diagnosis, or treatment
• Do not make medical or psychiatric claims
• Do not claim certainty where the notes only suggest a weak pattern
• For MBTI-style analysis, always frame the result as a hypothesis, not a verdict
• If memo evidence is too thin, say that plainly

Example Triggers

• “基于我的 flomo，分析一下我自己”
• “我最近的核心矛盾是什么”
• “从我的笔记里看，我到底在追什么”
• “帮我做盲区分析”
• “把我的困惑转成行动建议”
• “从我的 flomo 猜一下我的 MBTI”
• “过去 30 天和过去一年相比，我变了什么”

Output Quality Bar

Good output feels like:

• it tells the user something they did not cleanly articulate
• it names repeated patterns, not one-off noise
• it connects evidence to interpretation
• it leaves the user with a next move, not just a description

Bad output feels like:

• generic journaling summary
• abstract positivity
• vague personality fanfiction
• long memo paraphrases with no actual synthesis