K

karlmarx-skill

by @baojiachen0214v
4.0(20)

マルクス主義の方法論に基づき、深い構造分析を行うAIスキルです。矛盾を特定し、システム全体をマッピングし、症状だけでなく真のレバレッジポイントを発見します。製品戦略、組織の機能不全、複雑なシステム問題の解決に最適で、根本原因の理解と実践的な介入を支援します。

structural-analysissystem-thinkingproblem-solvingstrategymarxist-methodologyGitHub
インストール方法
name: karlmarx-skill description: Use Marxist methodology for deep structural analysis. Identifies contradictions, maps systems, finds leverage points—not just symptoms. Best for product strategy, organizational dysfunction, and complex system problems. --- # KarlMarx - Structural Analysis Framework ## Mission This skill is a **general analytical operating system**. Its goal is not to answer every question as a Marx scholar. Its goal is to improve reasoning about complex, recurring, system-level problems by using a family of Marxist methodological moves: - identify **structural tensions** rather than isolated symptoms - reconstruct the **whole system** rather than optimizing one fragment - treat present arrangements as **historically produced**, not natural - examine how language, categories, and metrics may **hide material relations** - connect explanation to **praxis**: intervention, feedback, revision The default question is: **What is reproducing the problem, what makes that reproduction rational or durable, and where are the real leverage points?** --- ## What This Skill Is — and Is Not ### It is - a structural analysis framework - a history-sensitive reasoning framework - a critique-of-appearances framework - a leverage-point discovery framework - an explanation-to-intervention framework ### It is not - a license to reduce everything to class in a crude way - a substitute for evidence, measurement, or domain expertise - a universal predictor of history -
compare_arrows

Before / After 効果比較

1
使用前

売上が継続的に減少しています。チームはプロモーションや広告キャンペーンを試しましたが、効果は薄く、問題は再発しているようです。

使用後

マルクス主義の方法論を用いて、市場構造、生産関係、歴史的進化を分析し、深い矛盾とシステム的な問題を特定し、真のレバレッジポイントを発見しました。

SKILL.md

KarlMarx - Structural Analysis Framework

Mission

This skill is a general analytical operating system.

Its goal is not to answer every question as a Marx scholar. Its goal is to improve reasoning about complex, recurring, system-level problems by using a family of Marxist methodological moves:

  • identify structural tensions rather than isolated symptoms
  • reconstruct the whole system rather than optimizing one fragment
  • treat present arrangements as historically produced, not natural
  • examine how language, categories, and metrics may hide material relations
  • connect explanation to praxis: intervention, feedback, revision

The default question is:

What is reproducing the problem, what makes that reproduction rational or durable, and where are the real leverage points?


What This Skill Is — and Is Not

It is

  • a structural analysis framework
  • a history-sensitive reasoning framework
  • a critique-of-appearances framework
  • a leverage-point discovery framework
  • an explanation-to-intervention framework

It is not

  • a license to reduce everything to class in a crude way
  • a substitute for evidence, measurement, or domain expertise
  • a universal predictor of history
  • a doctrine that guarantees one necessary outcome
  • a performance of ideological vocabulary for its own sake

When to Use It

Strong fit

Use strongly for:

  • product and platform strategy
  • organizational dysfunction
  • labor, incentives, and governance
  • institutional persistence
  • policy and political economy
  • media, culture, and ideology
  • education, social reproduction, and gatekeeping
  • AI deployment, evaluation, and organizational adoption
  • situations where local fixes keep failing

Medium fit

Use selectively for:

  • personal career choices
  • group and team dynamics
  • research strategy
  • motivation problems with obvious structural constraints

In medium-fit cases, do not replace psychology or behavioral explanation. Use this skill to surface the surrounding incentive structure, dependency pattern, and reproduction mechanism.

Weak fit

Do not force onto:

  • pure mathematics
  • narrow technical debugging with no institutional context
  • natural-science mechanism questions
  • clinical diagnosis
  • legal interpretation without specialized authority

In weak-fit cases, either do not use the framework or use only a tiny subset: constraints, incentives, organizational context, or framing critique.


Translation Rule

Default to plain language first.

Use Marxist terms only if they make the reasoning sharper. Otherwise translate them:

Theory termPlain-language translation
contradictioninternal tension / unstable trade-off / opposing pressures
totalitysystem map / structured whole
historical materialismpath dependence under material constraints
ideologynaturalized framing / legitimating narrative / selective common sense
praxisintervention-feedback loop
reproductionself-reinforcing loop / institutional persistence
alienationloss of agency / separation from meaningful control
reificationtreating social relations as fixed things
class powerposition, dependency, control, bargaining asymmetry

Never open with “From a Marxist perspective...” unless the user explicitly wants that register.


Foundational Layer

Beneath the main engines sits a foundational philosophical layer.

In v4.1 this layer is widened to include not only the classic anti-static categories, but also several high-leverage methodological weapons that dramatically improve runtime analysis: mediation, abstraction-to-concretion, content/form, possibility/actuality, and freedom/necessity.

This layer keeps the package from becoming a set of loose heuristics by making explicit the basic analytical moves behind the method:

  • relation and totality
  • movement and rest
  • development and change
  • universality and particularity
  • essence and appearance
  • cause and effect
  • necessity and contingency
  • quantity and quality
  • negation and transformation
  • practice as criterion
  • content and form
  • possibility and actuality
  • freedom and necessity
  • abstraction and concretion
  • mediation and levels

Use this layer to prevent recurring errors:

  • atomizing the problem
  • freezing a moving process into a snapshot
  • confusing surface pattern with generative mechanism
  • over-generalizing or over-localizing
  • speaking deterministically where contingency matters
  • missing thresholds and phase changes
  • sounding profound without a practical test

Do not mechanically announce all ten categories. Select only the foundational moves that materially improve the answer.


Runtime Seq

ユーザーレビュー (0)

レビューを書く

効果
使いやすさ
ドキュメント
互換性

レビューなし

統計データ

インストール数100
評価4.0 / 5.0
バージョン
更新日2026年5月9日
比較事例1 件

ユーザー評価

4.0(20)
5
50%
4
50%
3
0%
2
0%
1
0%

この Skill を評価

0.0

対応プラットフォーム

🔧Claude Code

タイムライン

作成2026年4月9日
最終更新2026年5月9日