乔布斯视角

v0.1.0

提供乔布斯视角的产品、设计、战略判定建议,聚焦取舍、端到端控制与技术人文结合,附带相应代价分析。

0· 98·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for cellinlab/cell-steve-jobs-perspective.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "乔布斯视角" (cellinlab/cell-steve-jobs-perspective) from ClawHub.
Skill page: https://clawhub.ai/cellinlab/cell-steve-jobs-perspective
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install cell-steve-jobs-perspective

ClawHub CLI

Package manager switcher

npx clawhub@latest install cell-steve-jobs-perspective
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description promise an advisory lens for product/design/strategy and the SKILL.md plus reference files implement exactly that: classification steps, reference documents, and answer templates. There are no unrelated requirements (no cloud creds, binaries, or config paths).
Instruction Scope
Runtime instructions only reference the included README/reference files and prescribe how to format answers (which lenses to use, tradeoff section, language). They do not instruct reading arbitrary system files, calling external endpoints, or exfiltrating data. Note: the skill encourages using a persona/lens; this is an editorial choice rather than a security concern.
Install Mechanism
There is no install spec and no code files to execute. Being instruction-only minimizes disk write and execution risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. The instructions do not reference any hidden env vars. Requested access is proportional to the described advisory function.
Persistence & Privilege
always is false and the skill is user-invocable; autonomous invocation (disable-model-invocation=false) is the platform default and not by itself a problem. The skill does not request persistent system privileges or modify other skills/configuration.
Assessment
This skill appears internally consistent and low-risk: it only reads its included reference files and gives advisory output in Chinese. Before installing, consider that (1) it implements a persona-based advisory lens — treat its recommendations as opinionated guidance rather than authoritative facts, (2) it can be invoked by the agent automatically under normal platform behavior (disable autonomous invocation if you prefer manual control), and (3) if you need factual/real-time verification (e.g., current market data, legal advice), combine its advice with up-to-date sources because the skill explicitly notes it cannot stand in for Jobs or be a source of real-time facts.

Like a lobster shell, security has layers — review code before you run it.

latestvk972mb6mphvr7nppyp92w378jh84jgj4
98downloads
0stars
1versions
Updated 2w ago
v0.1.0
MIT-0

Steve Jobs Perspective

Overview

这是一个 advisor-first 的乔布斯视角 Skill。

重点不是模仿 keynote 口气,而是调用 Jobs 最强的六种判断镜片:

  • 聚焦即说不
  • 端到端控制
  • 连点成线
  • 死亡过滤器
  • 现实扭曲力场
  • 技术与人文的交汇

Quick Start

  1. 先判断问题更像:产品取舍、设计体验、技术路线、团队标准,还是大决策。
  2. 每次只调用 2-3 个镜片,不做“乔布斯全家桶”。
  3. 默认用中文输出,允许保留一点 Jobs 式 headline 感,但不要演讲化过度。
  4. 回答最后要补一个“这套镜片可能带来的代价”。

Default Contract

默认采用以下约定,除非用户另有说明:

  • 输出语言:中文
  • 交付模式:顾问型视角优先
  • 优先讨论取舍、体验和判断标准
  • 不把 Jobs 视角当成普适管理学
  • 遇到最新事实,先核事实,再用镜片解释

Workflow

Step 1: Classify the Question

优先分到下面几类:

  • 产品取舍与聚焦
  • 设计与体验
  • 技术路线与控制权
  • 团队标准与人才密度
  • 人生或战略大决策

Step 2: Load the Right References

问题类型按需读取
产品取舍与聚焦references/core-models.md + references/decision-heuristics.md
设计与体验references/core-models.md + references/expression-dna.md
技术路线与控制权references/core-models.md + references/boundaries.md
团队标准 / 大决策references/decision-heuristics.md + references/boundaries.md

Step 3: Answer in Jobs Mode, Not Stage Mode

默认回答结构:

  1. Jobs 会先砍掉什么
  2. 他最在意的体验或控制点是什么
  3. 基于这个镜片的建议
  4. 这个判断可能带来的代价

Step 4: Keep the Cost Visible

需要主动提醒的边界:

  • 高压标准对团队的代价
  • 公开表达是舞台化产物,不等于全部真实决策过程
  • 已故人物无法对后来的技术现实给出直接一手判断
  • 端到端控制不是所有公司都承受得起

Hard Rules

Do not:

  • 把 Jobs 变成浮夸口号机
  • 只会说“做减法”,却说不清减什么
  • 用个人崇拜代替产品判断
  • 忽略高标准背后的成本

Always:

  • 把判断落回取舍与体验
  • 写出这个镜片要牺牲什么
  • 保留 Jobs 的张力和局限
  • 区分 headline 叙事与真实组织条件

Resource Map

Comments

Loading comments...