Skip to content

yanliudesign/offer-toolkit-skill / bq-skill

bq-skill

Verified

行为面试 skill。帮求职者挖掘真实经历、用 STAR/CAR 结构化、映射能力标签、构建可复用的中英双语故事库(Story Bank);并能接入 JD + 简历,针对具体岗位生成 Top 20 BQ 选题 + 基于真实经历的 STAR 准备模板(HTML 报告)。不是背答案,而是建立可复用的职业叙事体系,让任何行为面试题都能自然作答。关键词:behavioral question, BQ, 行为面试, STAR, 故事库, Amazon LP, 职业故事, tell me about a time, 面试准备, JD 面试题预测, top 20 题。

frameworks/star-car.md

View on GitHub
# 框架选择 — STAR / CAR / SOAR + 一稿多用

## 三个框架,何时用哪个

| 框架 | 结构 | 最适合 |
|---|---|---|
| **STAR** | Situation · Task · Action · Result | 默认主力。绝大多数 BQ 都用它。 |
| **CAR / PAR** | Challenge(Problem) · Action · Result | 答案要更短、更快入题时;口述、电话轮。省掉冗长背景。 |
| **SOAR** | Situation · Obstacle · Action · Result | 想突出"障碍/逆境"的题:最大挑战、克服困难、抗压。 |

经验法则:**库里按 STAR 存全料,临场按题型裁剪成 CAR/SOAR。** 存的是全集,讲的是子集。

## 黄金配比(口述 60–90 秒)

```
S  ▓             ~15%   一两句,听懂即可
T  ▓▓            ~15%   锁定"我"的责任
A  ▓▓▓▓▓▓        ~50%   引擎,讲判断和取舍
R  ▓▓▓           ~20%   量化 + 一句反思
```

最常见错误:S 占 50%,A 只剩一句。**时间预算永远向 A 倾斜。**

## 一稿多用 —— 同一个故事打多道题

一个挖透的故事能打 5–8 道题,靠的是**换开场句 + 换落点**,主体 A 不动。

例:一个"说服团队放弃已投入方案"的故事——

| 被问到 | 开场往哪带 | 落点强调 |
|---|---|---|
| Tell me about a conflict | 强调判断分歧 | 如何达成一致 |
| A time you influenced without authority | 强调没有职权 | 怎么靠数据/信任说服 |
| A time you took ownership | 强调主动发起 | 扛下结果 |
| A data-driven decision | 强调用数据 | 数据如何改变结论 |
| Your biggest failure(若有教训) | 强调早期误判 | 复盘与改变 |

**所以打标层一定要告诉用户"这个故事还能打哪些题"——这是故事库复用价值的直观证明。**

## 双语产出格式

- **EN**:面试可直接说的口语版本,60–90 秒长度,第一人称,动词驱动。
- **中文要点**:bullet 形式,供用户自查与记忆,不是逐句翻译。
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall