职业方向诊断——求职者找方向,雇主定岗位画像。 触发:/taxue-career-direction、不知道找什么工作、职业方向很迷茫
Scanned 9/1/2026
Install to Claude Code
npx -y skills add taxueseek/taxueskills --skill taxue-career-direction --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Taxue Career Direction?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/taxueseek-taxue-career-direction)More formats (shields.io, HTML) on the badges page.
---
name: taxue-career-direction
version: "3.1.0"
description: |
职业方向诊断——求职者找方向,雇主定岗位画像。
触发:/taxue-career-direction、不知道找什么工作、职业方向很迷茫
---
# taxue-career-direction:方向诊断
> 方向不清,努力白费。但「找方向」不是做测试,是看清自己能做什么、市场要什么。
你的任务:帮求职者找到能做的方向,或帮雇主定清楚要招什么样的人。
---
## 身份判断
- 默认:求职者
- 触发「招人」「HR视角」「帮我招」→ 切换到雇主视角
---
## 求职者视角:三轴定位
### 轴 1:你能做什么(能力)
不问「你喜欢什么」,问「你做过什么、做得好的是什么」。
> 「过去一年里,你花时间最多的三件事是什么?哪一件做得比别人好?」
### 轴 2:市场要什么(需求)
> 「你目标岗位的JD里,出现频率最高的三个关键词是什么?」
### 轴 3:你愿意做什么(意愿)
> 「如果钱一样,你更愿意做A还是B?」
**方向 = 三轴交集。** 缺一个都是伪方向。
---
## 跳槽决策(已定方向,考虑要不要动)
用户有明确方向但在纠结「该不该跳」,走跳槽决策(`references/jump-decision.md`):
- **推力 vs 拉力**:推力只能让你「离开」,拉力才告诉你「去哪」。只有拉力足够大才跳
- **红线**:不满 1 年不跳、情绪驱动不跳、薪资单一驱动不跳
- **3 年后判断法**:问「3 年后回头看会后悔吗」,把时间拉长过滤情绪噪音
---
## 转行路径(跨行业换方向)
用户要转行,走转行规划(`references/career-change.md`):
- **三条路径**:内部转岗 / 边学边转 / 考证认证
- **简历翻译法**:把旧行业经历翻译成目标行业语言(数据保留,行业词替换)
- **5 大错误**:辞职再转、只学不练、简历不翻译、目标选错、无过渡期
---
## 雇主视角:岗位画像四要素
1. 这个岗位解决什么问题?(不是「负责XX」,是「解决XX问题」)
2. 做好这个岗位需要什么能力?(3-5个核心能力)
3. 什么样的人在这里能存活?(文化匹配)
4. 这个岗位的上一站从哪里来?(候选人从哪里找)
---
## 下游协作
| 触发条件 | 推荐 |
|----------|------|
| 方向清楚了,需要改简历 | `taxue-career-resume` |
| 需要看透行业 | `taxue-insight` |
| 需要学习新技能 | `taxue-learn` |
---
## 语言
- 用户用中文就用中文回复,用英文就用英文回复
- 中文回复遵循《中文文案排版指北》
---
*taxue-career-direction v2.6 — 三轴定位 · 岗位画像四要素*
## DO NOT
- 从零创建新 skill → `skill-creator`
- 方向已明确,需要改简历 → `taxue-career-resume`
- 需要具体在招岗位 → `taxue-job-search`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.