agentleFS
q2522879285-sourceq2522879285-source/red-monkey-reasoning-kit/skills/longitudinal-horizontal-analysis/SKILL.md

longitudinal-horizontal-analysis

Skill2 starsChanged 2 months agoMITView on GitHub

Research an object through both longitudinal evolution and horizontal comparison, then produce conditional future paths. Use for strategy, competitors, technologies, companies, industries, or events when the user asks how it evolved, how it differs, and what may happen next. Skip one-point lookups, summaries, purely current spec tables, and history-only timelines.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the request combines how an object reached its current state, how it differs from meaningful comparators, and what paths may …

    line 12
  2. Very specific:

    Use $fact-claim-audit for disputed, current, or decision-critical claims.

    line 27
  3. Very specific:

    Use $bidirectional-steelman when the research supports a contestable strategic choice.

    line 28

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Longitudinal-Horizontal Analysis

Own the structure “historical path × comparable differences → conditional outlook.” Current facts and claims must still pass evidence checks.

Route

Use when the request combines how an object reached its current state, how it differs from meaningful comparators, and what paths may follow. Typical domains include strategy, products, companies, technologies, and industries.

Skip single facts, mechanical calculations, summaries, history-only chronologies, and current comparison tables that do not require path dependence. Use $industry-briefing for recurring latest-news briefing ownership.

Procedure

  1. Fix the object, cutoff date, research question, comparison boundary, and evidence standard.
  2. Build the longitudinal axis: origin and demand, key drivers, turning points, successes and failures, and early choices that created current capabilities or constraints.
  3. Choose a small set of genuinely comparable objects, justify the set, and use common definitions, time windows, and metrics.
  4. Compare strengths, limits, uniqueness, and observed user or market choice without treating difference as causality.
  5. Combine both axes into two or three future paths, each with prerequisites, leading signals, and disconfirming or exit signals.
  6. Separate facts, inference, and viewpoint; place sources and dates near important claims and show conflicts rather than smoothing them away.

Handoffs and Boundaries

  • Use $fact-claim-audit for disputed, current, or decision-critical claims.
  • Use $bidirectional-steelman when the research supports a contestable strategic choice.
  • Report length follows the question; never inherit the source card’s fixed 10,000–30,000-character template.

Completion Gate

Core conclusions trace to longitudinal evidence and/or a same-basis comparison. Forecasts are conditional, comparators are justified, definitions match, and uncertainty is visible.

Source Status

Distilled from the user-supplied “纵横分析法” method card. Its process and fixed length are proposals, not validated evidence of research quality.

<!-- integration-watermark: 红猴子整合 -->

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.