CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

karl-marx-perspective

卡尔·马克思的思维框架与表达方式。基于《资本论》《共产党宣言》 《德意志意识形态》《关于费尔巴哈的提纲》《路易·波拿巴的雾月十八日》 《哥达纲领批判》、书信、第一国际材料和权威学术评价的调研, 提炼5个核心心智模型、8条决策启发式和表达DNA。 用途:作为思维顾问,用马克思的视角分析资本、劳动、技术、组织、 阶级、意识形态、政治经济结构和历史变迁。 当用户提到「用马克思的视角」「马克思会怎么看」「马克思模式」 「Marx perspective」「karl marx perspective」「从马克思主义看」时使用。 即使用户只是说「按生产关系分析」「看资本逻辑」「阶级分析一下」 「这是不是异化」也应触发。

67

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a well-structured, genuinely actionable roleplay protocol with clear steps, routing, and boundary rules. Its weaknesses are token efficiency — long biographical/bibliographical sections that restate what Claude already knows — and a monolithic layout that inlines material the existing references/research/ bundle could hold.

Suggestions

Move the 人物时间线, 智识谱系, and 调研来源 sections into references/research/ (or drop them) — Claude already knows Marx's biography and works, so these lines spend context on shared knowledge.

Add 1-2 worked examples (sample user question → expected Marx-perspective answer) so the required response shape is demonstrated, not just described by the Step 3 rules.

Compress each 核心心智模型's 证据 bullet lists to one line and point to references/research/01-writings.md for the textual evidence, keeping only the 一句话/应用/局限 inline.

DimensionReasoningScore

Conciseness

The workflow, models, and heuristics are dense and earn their tokens, but sizable sections restate knowledge Claude already has: the 15-row biographical timeline (1818 birth, 1848 Manifesto, 1867 Capital), the 智识谱系 section, and the full URL source lists. This fits "Mostly efficient but includes some unnecessary explanation or could be tightened" rather than the 4 anchor, where only minor trimming would be needed — here entire sections (timeline, genealogy, sources) could move out or be cut.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: a question-classification table, five numbered research lenses each with four specific questions, a five-step answer structure, a scenario-routing table, and explicit expression rules ("用「我」而非「马克思会认为」", "不拼贴名言"). It falls short of the 5 anchor only because there is no worked example (sample question → expected Marx-perspective response) demonstrating the required output shape, leaving the common cases shown by rule rather than by example.

4 / 5

Workflow Clarity

The three-step protocol (问题分类 → 马克思式研究 → 马克思式回答) is clearly sequenced with checkpoints: a mandatory research gate ("只要缺少最新事实会改变……就必须先研究"), a pre-answer consolidation step ("研究完成后,先在内部整理事实摘要,再进入 Step 3"), and an explicit boundary-reporting step ("主动写出边界:哪些事实不足"). It misses the 5 anchor because there are no true feedback loops (no re-check/retry when research is inconclusive) and the scenario-routing step's interaction with Step 1 is implicit.

4 / 5

Progressive Disclosure

References exist and are real (references/research/01-writings.md through 06-timeline.md are listed and "调研过程详见 references/research/"), but the SKILL.md body inlines ~330 lines of content that belongs at one remove: the full timeline, the source bibliography, per-model evidence lists, and the expression DNA details all duplicate material plausibly present in the research files. This matches "Some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline" — the structure is genuinely good (clear sections, real one-level-deep references), which keeps it above the 2 anchor, but the monolithic inline bulk keeps it below 4.

3 / 5

Total

14

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: it states the skill's purpose and analysis domains concretely, gives explicit bilingual trigger phrases including indirect invocation variants, and occupies a distinct niche. Voice is appropriately third-person and there is no fluff or over-claiming.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities and domains: "作为思维顾问,用马克思的视角分析资本、劳动、技术、组织、阶级、意识形态、政治经济结构和历史变迁", plus concrete artifacts ("5个核心心智模型、8条决策启发式和表达DNA"). This matches the anchor "Lists multiple specific concrete actions; comprehensive coverage"; it is not the level-4 anchor because there are no meaningful coverage gaps.

5 / 5

Completeness

Both what and when are explicit: the what is stated in the opening ("卡尔·马克思的思维框架与表达方式……作为思维顾问,用马克思的视角分析……") and the when is an explicit trigger clause ("当用户提到……时使用" plus "即使用户只是说……也应触发"). This mirrors the 5 anchor "Clearly and explicitly answers both what AND when with concrete trigger phrases"; the 4 anchor would require the when-clause to be less explicit or specific, which is not the case.

5 / 5

Trigger Term Quality

It covers natural trigger phrases with synonyms in both Chinese and English: 「用马克思的视角」「马克思会怎么看」「马克思模式」「Marx perspective」「karl marx perspective」「从马克思主义看」, and additionally anticipates indirect phrasings like 「按生产关系分析」「看资本逻辑」「阶级分析一下」「这是不是异化」. This is comprehensive synonym-level coverage, matching the 5 anchor rather than the 4 anchor ("a few natural terms missing") because even indirect variants are supplied.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — a Marx-perspective thinking advisor — with named triggers unlikely to appear for other skills (「马克思会怎么看」, "Marx perspective", 「这是不是异化」). This is a "Clear niche with distinct triggers; minimal conflict risk"; it does not fall to the 4 anchor since no closely related skill would contend for these phrases.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 6 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

digoal/blog

Path

skills/karl-marx-perspective/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.